To do this, navigate to the GitHub CI page. Click the
... button next to the
Run button to enter the Run Custom Build dialog. Select the branch number of your pull request under the
Changes tab and click run - TeamCity will then run your tests and report status to GitHub.
If there is a situation with TC you can't explain and for which we do not have best practices or troubleshooting guides yet, file a new issue, explain the situation, and assign it to the Dev Infrastructure team.
Be sure to include a link to the failed TC Build if there is one.
Then after you have captured a link to the failed build, for good measure try to run your build again once. Perhaps the first time was a flake and you can move on with your day after that.
Example odd, transient situations we've encountered in the past:
- Build appears to fail but really TC was unable to find an agent to run some targets.
- Build appears to fail but really an agent was preempted and TC was unable to re-start a target.
- TC configuration was changed recently and one of the CI targets was overlooked in the change.
When code is merged to
master, TeamCity's Release Build job gets triggered for that branch. This job triggers all of the tests run by GitHub CI and posts any failures as GitHub issues. If there are no failures and the updated branch is
master, it will kick off a set of binary builds and push them to Docker Hub and our binary release storage area in AWS S3.