[JIRA] (JENKINS-16201) Join plugin - join job does not run

[cameron.h...@boxtone.com (JIRA)]

Cameron Horn commented on JENKINS-16201 Join plugin - join job does not run I'm seeing this as well, suspect it relates to lazy project loading. Here's an example log (7.1patch142_platform_rails): Notifying upstream build 7.1patch142_platform #9 of job completion Project 7.1patch142_platform still waiting for [7.1patch142_platform_DataServices, 7.1patch142_platform_katrina, 7.1patch142_platform_flex-components, 7.1patch142_platform_authentication, 7.1patch142_platform_bAware, 7.1patch142_platform_cicada, 7.1patch142_platform_DPServer, 7.1patch142_platform_elibs, 7.1patch142_platform_ebins, 7.1patch142_platform_sdks, 7.1patch142_platform_HSQLDefrag, 7.1patch142_platform_service-wrapper, 7.1patch142_platform_bSecurity, 7.1patch142_platform_adforest] builds to complete Notifying upstream projects of job completion Notifying upstream of completion: 7.1patch142_platform #9 Finished: SUCCESS Note that at the time of this project's completion, all of the jobs listed as being waited for have already completed, and have similar logs. Here's 7.1patch142_platform_elibs from above: Notifying upstream build 7.1patch142_platform #9 of job completion Project 7.1patch142_platform still waiting for [7.1patch142_platform_DataServices, 7.1patch142_platform_rails, 7.1patch142_platform_bAware, 7.1patch142_platform_cicada] builds to complete Notifying upstream projects of job completion Notifying upstream of completion: 7.1patch142_platform #9 Finished: SUCCESS Clearly, in between these projects building, 7.1patch142_platform #9 forgot about projects that it already knew had been completed. The time between those projects completing is ~6 hours.

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