Ytukyg

The simplest way

You can use EnvInject plugin to injects environment variables at build startup. For example:

How you know it's working

In my case, I needed to add the JMETER_HOME environment variable to be available via my Ant build scripts across all projects on my Jenkins server (Linux), in a way that would not interfere with my local build environment (Windows and Mac) in the build.xml script. Setting the environment variable via Manage Jenkins - Configure System - Global properties was the easiest and least intrusive way to accomplish this. No plug-ins are necessary.

The environment variable is then available in Ant via:

<property environment="env" />

<property name="jmeter.home" value="${env.JMETER_HOME}" />

This can be verified to works by adding:

<echo message="JMeter Home: ${jmeter.home}"/>

Which produces:

JMeter Home: ~/.jmeter

EnvInject Plugin aka (Environment Injector Plugin) gives you several options to set environment variables from Jenkins configuration.

By selecting Inject environment variables to the build process you will get:

• Properties File Path


• Properties Content



• Script File Path




• Script Content




• and finally Evaluated Groovy script.

Evaluated Groovy script gives you possibility to set environment variable based on result of executed command:

• with execute method:

    return [HOSTNAME_SHELL: 'hostname'.execute().text, 

        DATE_SHELL: 'date'.execute().text,

        ECHO_SHELL: 'echo hello world!'.execute().text

    ]

• or with explicit Groovy code:

    return [HOSTNAME_GROOVY: java.net.InetAddress.getLocalHost().getHostName(),

        DATE_GROOVY: new Date()

    ] 

(More details about each method could be found in build-in help (?))

Unfortunately you can't do the same from Script Content as it states:

Execute a script file aimed at setting an environment such as creating
folders, copying files, and so on. Give the script file content. You
can use the above properties variables. However, adding or overriding
environment variables in the script doesn't have any impacts in the
build job.

There is Build Env Propagator Plugin which lets you add new build environment variables, e.g.

Any successive Propagate build environment variables step will override previously defined environment variable values.

You can try something like this

stages {

        stage('Build') {

            environment { 

                    AOEU= sh (returnStdout: true, script: 'echo aoeu').trim()

                }

            steps {

                sh 'env'

                sh 'echo $AOEU'

            }

        }

    }

You can use Environment Injector Plugin to set environment variables in Jenkins at job and node levels. Below I will show how to do it at job level.

1. From the Jenkins web interface, go to Manage Jenkins > Manage Plugins and install the plugin.

2. Go to your job Configure screen


3. Find Add build step in Build section and select Inject environment variables
   


4. Set the desired environment variable as VARIABLE_NAME=VALUE pattern. In my case, I changed value of USERPROFILE variable

If you need to define a new environment variable depending on some conditions (e.g. job parameters) you can refer to this answer.

Normally you can configure Environment variables in Global properties in Configure System.

However for dynamic variables with shell substitution, you may want to create a script file in Jenkins HOME dir and execute it during the build. The SSH access is required. For example.

1. Log-in as Jenkins: sudo su - jenkins or sudo su - jenkins -s /bin/bash
   


2. 
   

   Create a shell script, e.g.:

   
   
   

   echo 'export VM_NAME="$JOB_NAME"' > ~/load_env.sh
   
   echo "export AOEU=$(echo aoeu)" >> ~/load_env.sh
   
   chmod 750 ~/load_env.sh
   
   

   
   


3. 
   

   In Jenkins Build (Execute shell), invoke the script and its variables before anything else, e.g.

   
   
   

   source ~/load_env.sh
   
   

   
   

Try Environment Script Plugin (GitHub) which is very similar to EnvInject. It allows you to run a script before the build (after SCM checkout) that generates environment variables for it. E.g.

and in your script, you can print e.g. FOO=bar to the standard output to set that variable.

Example to append to an existing PATH-style variable:

echo PATH+unique_identifier=/usr/local/bin

So you're free to do whatever you need in the script - either cat a file, or run a script in some other language from your project's source tree, etc.

For some reason sudo su - jenkins does not log me to jenkins user, I ended up using different approach.

I was successful setting the global env variables using using jenkins config.xml at /var/lib/jenkins/config.xml (installed in Linux/ RHEL) - without using external plugins.

I simply had to stop jenkins add then add globalNodeProperties, and then restart.

Example, I'm defining variables APPLICATION_ENVIRONMENT and SPRING_PROFILES_ACTIVE to continious_integration below,

<?xml version='1.0' encoding='UTF-8'?>

<hudson>



  <globalNodeProperties>

    <hudson.slaves.EnvironmentVariablesNodeProperty>

      <envVars serialization="custom">

        <unserializable-parents/>

        <tree-map>

          <default>

            <comparator class="hudson.util.CaseInsensitiveComparator"/>

          </default>

          <int>2</int>

          <string>APPLICATION_ENVIRONMENT</string>

          <string>continious_integration</string>

          <string>SPRING_PROFILES_ACTIVE</string>

          <string>continious_integration</string>

        </tree-map>

      </envVars>

    </hudson.slaves.EnvironmentVariablesNodeProperty>

  </globalNodeProperties>

</hudson>

We use groovy job file:

description('')

steps {

    environmentVariables {

        envs(PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: true)

    }

}

Jenkin is having inbuilt support for this, using which your can access value of local variables as global environment variables. You can achieve this in following 4 simple steps.

Step-1

............................

rm -f <some_name>.properties

touch <Some_name>.properties

............................

#pass the variable name you want to access as an env variable

echo variable_name1=$some_value1 >> <some_name>.properties

echo variable_name2=$some_value2 >> <some_name>.properties

............................

echo variable_name3=$some_value3 >> <some_name>.properties

Step-2

Under "Add Build Step" drop-down, select "Inject environment variable"

Step:3

Enter the fully qualified file name that you created previously(<some_name>.properties) in Properties File Path field.

Step-4

Now it's available as a Jenkins environment variable and you can use as needed in Post-build-Action . $variable_name1 like any other environment variable.

Here is a nice post regarding this