![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
jenkins-multijob-plugin |
|
Created:
|
16/Jul/14 5:33 AM
|
|
Description:
|
I modeled our release process using multijob and I am seeing some odd behavior that makes me question, why the multi job itself is upstream of all jobs that it encompasses or wraps?
So, I have a 13 phase multi job with each phase having 2 to 5 release jobs. Works great!
I added a parameterizedTrigger to each release job to fire a post-release-job upon success. The downstream post-release-job does fire, but it is blocked by the Upstream Multijob. Why? To me, it is just a wrapper and should not block. The verbiage from the pending job in the queue is "(pending—Upstream project In progress RELEASE_PROCESSOR » re_release » Multijob Release Pipeline is already building." Somehow the multijob, that wraps all the release jobs in phases has become the upstream project of the post-release-job even though each individual post-release-job lists only its release job as upstream.
I guess I can envision use cases where one would want to block until a whole multijob is done, but in my case, I don't want to block on the multi job.
Is it possible to make an enhancement to add a "do not treat the multijob as an upstream project" checkbox (or something similar).
Please let me know if you'd like further clarification and/or screenshots. Thanks.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
James Levinson
|
|
|
|
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/d/optout.
