Access to build environment variables from a groovy script in a Jenkins build step Windows

Question

I m using Scriptler plugin  so I can run a groovy script as a build step  My Jenkins slaves are running on windows in service mode  With scriptler  I don t need to use windows batch scripts   But I have trouble to get the environment variables in a build step    This is working   System getenv  BASE     Where BASE is part of the env-vars on jenkins startup  However  I would like to get    JOB NAME    If I m adding an  Execute Windows batch command  build step   echo  JOB NAME    It works  If I m adding a scriptler script as a build step with the same settings   println  JOB NAME      System getenv  JOB NAME     I m getting    JOB NAME  null   So how can I reach the injected environment variables from a groovy script as a build step

User · Answer

One thing to note  if you are using a freestyle job  you won t be able to access build parameters or the Jenkins JVM s environment UNLESS you are using System Groovy Script build steps   I spent hours googling and researching before gathering enough clues to figure that out

User · Answer

Jenkins 2 x has the global variables  env is one of them from any script     println env JOB NAME   More at https   build intuit com services-config pipeline-syntax globals env

User · Answer

build and listener objects are presenting during system groovy execution  You can do this   def myVar   build getEnvironment listener  get  myVar

User · Answer

The Scriptler Groovy script doesn t seem to get all the environment variables of the build  But what you can do is force them in as parameters to the script    When you add the Scriptler build step into your job  select the option  Define script parameters  Add a parameter for each environment variable you want to pass in  For example  Name  JOB NAME    Value   JOB NAME   The value will get expanded from the Jenkins build environment using   envName  type variables  most fields in the job configuration settings support this sort of expansion from my experience  In your script  you should have a variable with the same name as the parameter  so you can access the parameters with something like   println  JOB NAME    JOB NAME    I haven t used Sciptler myself apart from some experimentation  but your question posed an interesting problem  I hope this helps

User · Answer

You might be able to get them like this   def thr   Thread currentThread   def build   thr  executable def envVarsMap   build parent builds 0  properties get  envVars

User · Answer

The only way I could get this to work  on Linux  was to follow this advice   https   wiki jenkins-ci org display JENKINS Parameterized System Groovy script  import hudson model       get current thread   Executor and current build def thr   Thread currentThread   def build   thr  executable     if you want the parameter by name     def hardcoded param    FOOBAR  def resolver   build buildVariableResolver def hardcoded param value   resolver resolve hardcoded param   println  param   hardcoded param  value     hardcoded param value     This is on Jenkins 1 624 running on CentOS 6 7

User · Answer

On jenkins 2 x  with groovy plugin 2 0  running SystemGroovyScript I managed to get to build variables  as below   def build   this getProperty  binding   getVariable  build   def listener   this getProperty  binding   getVariable  listener   def env   build getEnvironment listener  println env MY VARIABLE   If you are using goovy from file  simple System getenv  MY VARIABLE   is sufficient

[windows] Access to build environment variables from a groovy script in a Jenkins build step (Windows)

Examples related to windows

Examples related to groovy

Examples related to jenkins

Examples related to environment-variables