why are subsequent builds started with the Finish Build Trigger not chained?

I have three build configurations: A, B, and C.

B has a snapshot dependency on A with the Do not run new build if there is a suitable one option checked.

C has a snapshot dependency on A with the Do not run new build if there is a suitable one option checked.

B has a Finish Build Trigger on A with the Trigger after successful build only option checked.

C has a Finish Build Trigger on A with the Trigger after successful build only option checked.

I run a custom build of A with an environment variable set to a non-default value.  After A completes, as expected and desired both B and C run as triggered by the custom build of A.  However, the build chain only shows either B or C, but not both of them as being linked to the custom build of A.  The other one is linked to a prior build of A.  Why is this?  This is unintuitive.  It seems like if the Finish Build Trigger causes the depending build to be chained to the build triggering build, that it should do this for all such triggered builds, not just one of them.

Thanks!

-shawn   :-)

4 comments
Comment actions Permalink

Can you provide a screenshot of the build chain page demonstrating this issue?

0
Comment actions Permalink

Pavel,

Does this give what you requested?

clip2.jpg

Here, both B #2 and C #2 builds were performed after A #2 due to Finish Build triggers contained in B and C, respecively.

The question is why C #2 was chained to an earlier A build instead of C #2 being chained to A #2.

Thanks!
-shawn  :-)

0
Comment actions Permalink

Could you please tell me start time for all these builds?

0
Comment actions Permalink

Pavel,

The start times are:

C #2 => 16 Oct 12 05:30:22

B #2 => 16 Oct 12 05:30:10

A #2 => 16 Oct 12 05:29:59

C #1 => 16 Oct 12 05:29:31

B # 1 => 16 Oct 12 05:29:19

A #1 => 16 Oct 12 05:29:09

Are you able to reproduce the issue?

Thanks!

-shawn   :-)

0

Please sign in to leave a comment.