Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: parameterized-trigger-plugin
-
Labels:None
-
Environment:Windows
-
Similar Issues:
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
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.
UPDATE 3
I ended up reverting to the LTS Release and this seems to have fixed the issue. So it looks like Jenkins has caused this rather than the other plugins.
Attachments
Issue Links
- duplicates
-
-
- Reopened
-
Activity
seems this issue no more!!!
please close this issue otherwise comment with latest stacktrace
hiteswar kumar
added a comment - seems this issue no more!!!
please close this issue otherwise comment with latest stacktrace We've got this on our Jenkins ver. 1.520. Parametrized trigger plugin 2.18, linux Ubuntu 12.04 x64.
Attached stacktraces.
Yaroslav Rybak
added a comment - - edited We've got this on our Jenkins ver. 1.520. Parametrized trigger plugin 2.18, linux Ubuntu 12.04 x64.
Attached stacktraces. Seeing this problem happen randomly.
Jenkins 1.526
java version "1.6.0_38"
Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)
Param Trigger 2.18
Daniel Aquino
added a comment - Seeing this problem happen randomly.
Jenkins 1.526
java version "1.6.0_38"
Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)
Param Trigger 2.18 I suppose that issue duplicates JENKINS-19741
BTW, referenced links is being reproduced during massive submissions only
There appears to be a number of ways this issue can be caused. I suspect that there are a number of exceptions which, when thrown, can cause the Future the Parameterized Trigger is waiting on to never complete.
The logging I've seen indicates the parameterized trigger is waiting at:
Yet, the project being waited on has completed.
What is the code that sets the result for the future? That would be where I'd check for exception paths that could skip the notification. Though, jenkins might be using Runnable as the future. In which case I wouldn't expect this at all.
Corey O'Connor
added a comment - There appears to be a number of ways this issue can be caused. I suspect that there are a number of exceptions which, when thrown, can cause the Future the Parameterized Trigger is waiting on to never complete.
The logging I've seen indicates the parameterized trigger is waiting at:
https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java#L135
Yet, the project being waited on has completed.
What is the code that sets the result for the future? That would be where I'd check for exception paths that could skip the notification. Though, jenkins might be using Runnable as the future. In which case I wouldn't expect this at all. I managed to workaround this issue by renaming the builds folder of the slave job (e.g. to old_builds). This, however, has the disadvantage that it removes the history of the job so far.
Martin Bektchiev
added a comment - I managed to workaround this issue by renaming the builds folder of the slave job (e.g. to old_builds). This, however, has the disadvantage that it removes the history of the job so far. This may be fixed in Jenkins-1.558, hudson-remoting 2.36.
https://github.com/jenkinsci/remoting/commit/6d0d5dea26c5f619164ade791a26a5c7c8dc50ea
https://github.com/jenkinsci/jenkins/commit/75447b57b655e38fdb48f1e854a4b287071342cf#diff-600376dffeb79835ede4a0b285078036
Please report if it reproduces after that version.
ikedam
added a comment - This may be fixed in Jenkins-1.558, hudson-remoting 2.36.
https://github.com/jenkinsci/remoting/commit/6d0d5dea26c5f619164ade791a26a5c7c8dc50ea
https://github.com/jenkinsci/jenkins/commit/75447b57b655e38fdb48f1e854a4b287071342cf#diff-600376dffeb79835ede4a0b285078036
Please report if it reproduces after that version. 
Same problem for me.