We have a build chain set up to trigger off of pull requests into the master branch. Right now there is 1 initial build configuration that does the actual building, then two more configurations that have to wait until the Build is finished, but those two have never triggered automatically. For simplicity I'll refer to these simply as Build 1, Build 2, and Build 3.
- VCS: a default branch of master and additional branch specification of +|-:*
- Trigger: VCS trigger, filter is +:* and -:refs/heads/master
- Build Features: Pull Requests, by target branch master
So far this has been firing every time that a pull request going into master is created/updated. It does not report back the status to the group as success/failure, but that's because that's how TeamCity works. It would be nice to have it, but not a deal-breaker.
Builds 2 and 3
- VCS: identical to Build 1
- Trigger: Finish Build Trigger, targeting Build 1
- Build Features: identical to Build 1
- Snapshot: Depends on Build 1, enforces revisions synchronization
- Artifact: Depends on Build 1, when trying to use the browser I don't get the builds except for the one time Build 1 ran off of master
So I can manually start Builds 2 and 3 in the chain and they work just fine, but they will never fire automatically. From what I've found online, because they aren't the default branch then the status of the build isn't reported to the group as a success or failure. I believe that Builds 2 and 3 have to wait until they get a completed build, and since the default branch is never being built then they don't get triggered. Should I change my default branch to target * instead of master? Or is there some other configuration that I don't have/messed up that can accomplish this?