Issue Type: Bug Bug
Affects Versions: current
Assignee: huybrechts
Components: parameterized-trigger
Created: 27/Dec/13 10:52 PM
Description:

In section Usage as a Build step in https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin its mentioned that, When using the Trigger/Call builds on another project item. If the trigger is configured with the Block until the triggered projects finish their builds enabled, the following Environment variables are made available for further build steps Env variables for future build steps

  • LAST_TRIGGERED_JOB_NAME="Last project started"
  • TRIGGERED_BUILD_NUMBER_<project name>="Last build number triggered"

version 2.17 onwards

  • TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects"
  • TRIGGERED_BUILD_NUMBERS_<project name>="Comma separated list of build numbers triggered"
  • TRIGGERED_BUILD_RESULT_<project name>="Last triggered build result of project"
  • TRIGGERED_BUILD_RESULT_<project name>RUN<build number>="Result of triggered build for build number"
  • TRIGGERED_BUILD_RUN_COUNT_project name>="Number of builds triggered for the project"

I tried configuring one upstream and downstream job. But I don’t see these ENV variables being passed to downstream jobs?

PS: I am checking for these ENV variables in Build step of downstream job like 'env|grep TRIGGERED'

Environment: Parameterized Trigger Plugin: 2.20
Jenkins: 1.509.4
Project: Jenkins
Labels: plugin parameterized-trigger
Priority: Major Major
Reporter: Dilip M
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to