-
Bug
-
Resolution: Unresolved
-
Major
-
x86_64 GNU/Linux
We use the join plugin to send out build completion emails when all the downstream builds are complete. Our builds usually take longer than 12 hours and they are triggered every 12 hours, so there is a period of time when the new build is waiting for the previous build to finish.
Join pluggin is supposed to trigger when all downstream builds are complete, but it never does so.
[JENKINS-16922] Join plugin does not trigger when the downstream builds are complete
Similar issues here - join trigger often does not work. We have a "starter job" that prepares some files, some "platform jobs" that do the stuff on multiple platforms, and a "collector job" that collects artifacts from the "platform jobs" - the collector often fails to start.
Using 1.523 currently, but the same issue was with older Jenkins versions.
binary
added a comment - - edited Similar issues here - join trigger often does not work. We have a "starter job" that prepares some files, some "platform jobs" that do the stuff on multiple platforms, and a "collector job" that collects artifacts from the "platform jobs" - the collector often fails to start.
Using 1.523 currently, but the same issue was with older Jenkins versions. 
jacek wiśniewski
added a comment - Similar issue.
Join plugin sometimes triggers, sometimes don't. I've noticed other regularity - trigger doesn't go off only if one, specyfic, job (of 13 jobs) ends the queue. If any other of job is executed as last - it seems to work as expected. Although it might be just a coincidence - I had only few builds analysed.
Execution of those 13 jobs take at most 2h.
I don't see any exceptions in logs.
Version: 1.544
jacek wiśniewski
added a comment - Similar issue.
Join plugin sometimes triggers, sometimes don't. I've noticed other regularity - trigger doesn't go off only if one, specyfic, job (of 13 jobs) ends the queue. If any other of job is executed as last - it seems to work as expected. Although it might be just a coincidence - I had only few builds analysed.
Execution of those 13 jobs take at most 2h.
I don't see any exceptions in logs.
Version: 1.544 
It's a similar situation with our configuration.
There is a base-test-job which starts detailed test-jobs when finished.
When the detailed-test-jobs have finished and there are no errors, a info-job should get started ... but ... sometimes the trigger doesn't work and the info-job has to be started manually.
(We are working with Jenkins 1.499)