Can you configure the Build Configuration Status to display result of any branch - not only the default?
Hi,
TeamCity displays the status of the last build on the "default"-branch as a red/green status indicator on the website. The status does not get updated when you build on a different branch.
Is it possible to configure that status icon to show the status (green/red) for any branch (just the latest build on any branch. Or have a branch configuration for that..)
Reason is: We are using TeamCity like this:
/--x---x--x (patch2)
--x----------x---x-------------x---x--x--x (master)
\----x---x (patch1)
"x" is a teamcity build
Basically, we have a master branch, and patch build branches, whose changes never get merged back into the master (instead they usually contain cherry picks from master). We also don't build the master when we have a patchX branch "running".
Now the big issue is, that while we are building patch builds, TeamCity does show the status of the last master build, so we always have to check each individual build target whether it failed or not. Since we got about 40 targets that we have to build, that is quite a chore.. (which basically means: we practically can't use TeamCity for verifying build results at all!)
If it would be possible to switch TeamCity to just show the damn last result in the status icon, that would be perfect. ;-)
Greetings, Imi
PS: we also tried to configure the default branch in the VCS connection to be "refs/heads/%default_branch%" and set this custom variable in the launch dialog, but it will still not count as building the "default" branch. (Also, it adds a / in front for no obvious reasons, making the branch name "/patch2".. when entering "patch2" for the default_branch..)
Please sign in to leave a comment.
https://youtrack.jetbrains.com/issue/TW-23414
https://youtrack.jetbrains.com/issue/TW-49360
Hi,
Are these patch branches something like release branches? Are they long lived? Do you run several builds in each patch branch and how stable they should be? For instance is it acceptable to break the settings of the entire configuration and to be unable to produce new patch builds for some time?
Usually for critical builds which are release or hotfixes it's quite important to freeze the settings and do not touch them anymore ensuring that you can always produce these builds no matter what. For such cases the traditional approach is to copy the project for the release branch and then run there the builds of this branch only. This decouples the release branch from the master branch settings allowing you complete freedom over what you can do in the master branch and keeping the release branches stable. In this case the status of the build configuration will also be relevant.
In our case, we have build configuration that deploys to our UAT server on builds of the “release” and “hotfix” branches.
We have branch filters and VCS triggers to control this.
+:releases/platform-v*
+:hotfix/platform-v*
Our master never triggers a build here and it would make most sense to see here if the last deployment was successful or not, for any branches matching these branch patterns.