Missing variables when executing EnvInject script

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: current
  • Fix Version/s: None
  • Component/s: envinject
  • Labels:
  • Environment:
    Jenkins 1.450 on Ubuntu 10.04
    EnvInject 1.20 or 1.22

Description

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.

  1. XML File
    config.xml
    15/Feb/12 9:56 PM
    2 kB
    Patrick Hartling
  2. XML File
    config.xml
    15/Feb/12 9:55 PM
    1 kB
    Patrick Hartling

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Patrick Hartling added a comment -

Job configuration with Git enabled.

Show
Patrick Hartling added a comment - Job configuration with Git enabled.
Hide
Permalink
SCM/JIRA link daemon added a comment -

Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java
http://jenkins-ci.org/commit/envinject-plugin/f2b3a4921b5127718214ad0454bb55a3812dbcfb
Log:
Fix JENKINS-12788

Show
SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java http://jenkins-ci.org/commit/envinject-plugin/f2b3a4921b5127718214ad0454bb55a3812dbcfb Log: Fix JENKINS-12788

People

  • Assignee:
    Gregory Boissinot
    Reporter:
    Patrick Hartling
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: