-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows
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.
- duplicates
-
JENKINS-19741 Massive jobs execution causes issues in lastSuccessfulBuild permalink update
-
- Reopened
-
[JENKINS-15476] "Block until the triggered projects finish their builds" doesn't notify upstream project when complete.
Description |
Original:
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 complete. 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. If i have left anything out please let me know. thanks |
New:
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 complete. 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 Param Trigger version 2.16 If i have left anything out please let me know. thanks |
Summary | Original: "Block until the triggered projects finish their builds" doesnt notify upstream project when complete. | New: "Block until the triggered projects finish their builds" doesn't notify upstream project when complete. |
Description |
Original:
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 complete. 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 Param Trigger version 2.16 If i have left anything out please let me know. thanks |
New:
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 Param Trigger version 2.16 If i have left anything out please let me know. thanks |
Description |
Original:
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 Param Trigger version 2.16 If i have left anything out please let me know. thanks |
New:
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 |
Component/s | New: disk-usage [ 15537 ] | |
Description |
Original:
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 |
New:
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. |
Description |
Original:
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. |
New:
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. |
Component/s | Original: disk-usage [ 15537 ] | |
Description |
Original:
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. |
New:
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. |
Same problem for me.