![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
promoted-builds |
|
Created:
|
11/Jun/13 10:24 AM
|
|
Description:
|
The target job should pre-define variables containing the job name and build number of the Job that causes the build.
Example:
- Upstream #3 promotes Downstream
- Then in Downstream I have JENKINS_PROMOTING_JOB_NAME="Upstream" and JENKINS_PROMOTING_BUILD_NUMBER="3" defined
This is useful where the downstream promotion should copy artifacts from the upstream project. The upstream's job name can be manually configured for the downstream job, but this is not possible when multiple upstream jobs should be able to trigger one downstream job.
Currently I workaround this using the Jenkins CLI within a shell excecuting promotion where I trigger parameterized builds. But this is times slower than a "execute shell" promotion.
|
|
Project:
|
Jenkins
|
|
Labels:
|
downstream
variables
promotion
upstream
promoted
jobname
environment
buildnumber
inject
predefined
implicit
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Thomas Lehmann
|
|
|
|
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.
