Finished Build trigger always in Pending state

We have two build configurations set up for a project -- one runs the debug build and tests (call it A), another runs asset builds and produces a deployable package (call it B). We have a Build Finished trigger on configuration B, pointing at configuration A. We also have a snapshot dependency from B to A, as recommended in the docs.

However, when A finishes a build successfully, the corresponding build on B never starts. It shows up as pending changes on B, but an actual build never starts.

Do we need to configure another trigger to actually kick off the pending changes, or is there some way to debug why the build isn't starting?

3 comments
Comment actions Permalink

Hmm, so it seems like it only triggers an actual build for master branch builds, even though the branch filter is cleared. Is there a way to change this?

0
Comment actions Permalink

Hello,

Please try to use the following branch filter: +:*
Empty branch filter is equivalent to +:<default> branch filter.
How do you trigger builds in build configuration A? If you trigger them on commits to VCS, then the recommended setup is to configure one VCS trigger for build configuration B with option "Trigger a build on changes in snapshot dependencies" enabled.

0
Comment actions Permalink

Thanks -- I ended up realizing the same thing about the branch filter after posting the question and forgot to go back and update it.

0

Please sign in to leave a comment.