[JIRA] (JENKINS-16330) Trigger should start two jobs, but one is never started

[rsand...@java.net (JIRA)]

rsandell commented on JENKINS-16330 Trigger should start two jobs, but one is never started Nothing in that list that I can find either. Could it be triggered builds that are on the same patch set number? The queue consolidates runs that have the same exact parameters as another scheduled task. That could be the reason the run is "lost". We fixed that in 2.6.0 by introducing a unique hash parameter for every triggered build.

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