What is classed as a "suitable" build

I will explain my configuration:

Build A has a VCS trigger with trigger rules that excludes check-ins from one particular user.
Build B has a snapshot dependency on Build A with "Do not run new build if there is a suitable one" and "Only use successful builds from suitable ones" the only options selected.

This is what happens currently:

1. The "excluded" user check-ins some code for Build A and a new build is not triggered automatically.
2. At some later point, with no other code having been committed for Build A, someone runs Build B and at that point Build A is run, followed by Build B.

This is what I would like to happen:

1. The "excluded" user check-ins some code for Build A and a new build is not triggered automatically.
2. At some later point, with no other code having been committed for Build A, someone runs Build B and Build B starts straight away without Build A being run first.

I assume this behaviour is by design but is there any way to get the snapshot dependency to ignore the excluded pending change on Build A and treat the last build of Build A as "suitable"?

I hope this makes sense!

1 comment
Comment actions Permalink

So I guess the fact that nobody has replied means there is no way of controlling this.

0

Please sign in to leave a comment.