![]() |
|
|
|
|
Change By:
|
Justin Crowe
(11/Oct/12 12:47 PM)
|
|
Description:
|
When using the parameterised trigger plugin Create 2 jobs.
Job 1 uses the "Trigger/call builds on other projects" option to call job 2 and check the "Block until the triggered projects finish their builds" option so that job 1 will only continue if Job 2 is complete and successful.
Build Job 1.
Job 1 will run and call the build on Job 2 but job 1 will never receive the notification of job 2's completion. This means that job 1 never completes and just sits in the build queue.
This is functionality that used to work with older versions of jenkins/the plugin so something has gone wring with recent releases as i have only just migrated from older versions.
java.runtime.name Java(TM) SE Runtime Environment
java.runtime.version 1.6.0_26-b03
Jenkins Version: 1.485 - a single master instance with no slaves
Param Trigger version 2.16
If i have left anything out please let me know.
thanks
UPDATE/Workaround
After looking through the logs i have removed the Disk Usage Plugin which seems to be having trouble (it looks like this issue has already been logged) and this seems to have fixed this. I have assigned the issue to that component as well now.
UPDATE 2
After looking further, disabling the disk usage plugin only seems to fix this for jobs with a single downstream job. If a downstream job contains further downstream jobs then the results are not being received.
|
|
|
|
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
|
