How can I inject environment variables into my groovy class?

[red 888]

My pipeline is using the environment directive to set an environment var and then calls a groovy class:

def call(int blah) {

    pipeline {
        agent any

        environment {
            MyVar = credentials('djsjflsjfljsf')
        }

        stages {
            stage('Stage ONE') {
                steps {
                    echo test.methodA()

            ....

But from in my groovy class I don't see those environment variables:

// vars/test.groovy

class test implements Serializable {
    static methodA (){

    def env = System.getenv()
    return env.dump()
    //return ['powershell', 'ls env:'].execute().text

}

 

env.dump() and listing envs from the shell from inside the class doesn't show those variables I added in the environment directive. Can I change the scope of the class to give it access to these environment vars?

[Victor Martinez]

Just wondering whether using the previous thread: https://groups.google.com/forum/#!topic/jenkinsci-users/XbI9WjlLmFY/discussion might help to keep a history of the previous suggestions though

[Michael Pailloncy]

Pipeline environment variables are not stored at the OS level. That's why you are not able to get them using System.getenv() (which only list OS level environment variables).

But you should be able to retrieve them like any other classical environment variables : with the "${MyVar}" syntax inside your shared lib class.

Hopefully it helps.

Michaël

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/87b6e2b0-ed9a-4ede-b22c-3b06761345e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[red 888]

So this is a problem for me because the APIs I'm using in the groovy class are looking for OS level environment variables.

Is there any way to set these variables with jenkins?

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

[Daniel Butler]

If you’re writing a groovy class that’s run from a library in the pipeline script then you’re not going to be able to use System.getEnv().

 

There’s a few approaches you can take that do work:

• You can pass in the values you need as parameters to the methods/constructors you’re using.
• In the pipeline there’s the global variable `env` which is a map of all the currently declared environment variables (JOB_NAME etc) you could pass into your class.
• Pass in `this` from the pipeline script. You can then use this object to access anything in pipeline, (Let’s assume you called the field/parameter ctx) i.e. ctx.env.JOB_NAME or ctx.powershell(“write-host ‘spooky’”)

 

I noticed also you’ve got a direct execution of a process commented out, don’t do that either. The same way System.getEnv() doesn’t work, doing that will not behave as expected either (Assuming the sandbox will let you)

 

 

Regards,

Daniel.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6e7e1b97-7b9c-404f-9597-8577eb739b96%40googlegroups.com.

[red 888]

"In the pipeline there’s the global variable `env` which is a map of all the currently declared environment variables (JOB_NAME etc) you could pass into your class."

Is there a way to do that so all those envs are imported and accessible in the class like they are system variables? For example if I do a printenv from the pipeline "MyVar" shows up like its a system variable, I want it to show up like that from in my class too. Is there an elegant way of importing all the vars in "env" into my class and making them access like shell variables?

[Daniel Butler]

If you’re dealing with a stubborn library that’s forcing you to use environment variables to pass in parameters you’re in for more pain than it’s worth trying to run it within the pipeline script environment.

 

Use it by running a groovy script externally, e.g.

 

sh “groovy MyScript.groovy”

 

and then you’ve got all the environment variables setup and you’re in a standard groovy environment without the pipeline restrictions and idiosyncrasies.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f9a07627-f0ce-4007-a4f5-54918f5d712c%40googlegroups.com.

[red 888]

I guess it took longer than it should have to realize I was barking up the wrong tree, but let me explain why I wanted this.

I'm using the AWS java sdk. The AWS sdk looks for these env vars and pulls them in for creds automatically if they are set in the current session. Of course you can pass them in manually, but this feature is quite convenient! I'm calling the AWS SDK from a groovy class like this because its super portable and behaves almost like a lightweight jenkins plugin- I really like the idea of writing reusable api wrappers in groovy classes for the pipeline like this.

The GCP SDK has similar features where it looks for env vars for config.

It just would be nice to be able to define this once in the environment{} directive before calling these api wrapper classes.