add check if any upstream project is in progress

[dirk-thomas]

In the following example Jenkins is not honoring the flag to block a build when any of its upstream packages is queued:

• Job A: http://build.ros.org/job/Ibin_uT32__object_recognition_capture__ubuntu_trusty_i386__binary/
• Job B: http://build.ros.org/job/Ibin_uT32__object_recognition_core__ubuntu_trusty_i386__binary/
• Job C: http://build.ros.org/job/Ibin_uT32__ecto_image_pipeline__ubuntu_trusty_i386__binary/
• Job D: http://build.ros.org/job/Ibin_uT32__ecto_ros__ubuntu_trusty_i386__binary/

The dependencies are as follows:

• A depends on B, C and D
• B depends on C
• C depends on D

The timeline of the events was:

• D5 got triggered (4:08)
• D5 finished which triggered A and C
• C4 starts building (4:47), A waits in the queue (nice)
• C4 finished which triggered A (already queued) and B
• A4 starts building (4:54:34) bad
  • since B was already queued and is an upstream project
  • it will fail since the Debian package of the upstream project B has been invalidated, but it can't detect it since all upstream projects are still "green"
• B3 starts building (4:54:42)
• B finished which triggered A5
• A5 starts and finished successfully

While that should be ensured by Jenkins we need to double check for it since Jenkins seems to not do that correctly, see pending tickets related to this:

• https://issues.jenkins-ci.org/browse/JENKINS-5125
• https://issues.jenkins-ci.org/browse/JENKINS-5150

This patch will ensure that A(4) does not only check the status of the last build result of all upstream project but also consideres if any of them are currently building or are currently queued.

[tfoote]

+1