| I have seen this happen in Jenkins 1.651.3, however, only when the Jenkins master is under heavy CPU load. Normally, everything works as it should, but on certain times when the Jenkins master CPU is running on max, we see two downstream builds of one project started, both builds pointing to the same parent build. This is done using the conditional build step + parameterized trigger and a schedule for the parent project. |