[ https://issues.jenkins-ci.org/browse/JENKINS-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hartling updated JENKINS-12788: --------------------------------------- Attachment: config.xml Job configuration with Git enabled. > Missing variables when executing EnvInject script > ------------------------------------------------- > > Key: JENKINS-12788 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12788 > Project: Jenkins > Issue Type: Bug > Components: envinject > Affects Versions: current > Environment: Jenkins 1.450 on Ubuntu 10.04 > EnvInject 1.20 or 1.22 > Reporter: Patrick Hartling > Assignee: gbois > Labels: git, plugin, windows > Attachments: config.xml, config.xml > > > Not all the Jenkins environment variables and build variables are being made > available to the EnvInject script. When testing with version 1.19, we had > JOB_NAME, EXECUTOR_NUMBER, and GIT_BRANCH to name a few. With 1.20 and 1.22, > we still have JOB_NAME, but EXECUTOR_NUMBER and GIT_BRANCH are not available. > I have attached a config.xml for use on a Windows slave. The same issue > exists on a Linux slave. The Git repository referenced in the config.xml > could be anything. The repository referenced is just there so that there is > some Git-related piece in the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira