Custom build with git branch creates a "hidden" build

I have TeamCity 7.0 set up and it builds my master branch from GIT just find. Occationally I need to build a branch so I configured my VCS root to use a configuration parameter called %branch%. It works really well, except that the build shows up in the build history in italic and gray and it doesn't show up as latest build. It seems like it's a personal build, but I have not checked that when I trigger the build. I trigger the build with just the custom build popup (under Run button) and enter my branch name that I want to build (default is master). Did I set this up wrong or why aren't these builds treated as any other builds? I've searched on "out of sequence" buidls and remote trigger personal builds, but that doesn't seem to match what I'm doing. See build #5257 in the image below.

Thanks,
/Hakan

Screen Shot 2012-02-23 at 10.20.56 PM.png

6 comments
Comment actions Permalink

This is actually expected behavior. If your custom build VCS settings differ from build configuration VCS settings, TeamCity will show this build the same way as it shows personal builds. I.e. changes in this build won't affect regular builds (builds on master branch in your case). For the same reason we do not show such builds on overview page, because this may confuse other users who may think this is a regular build made from the master.

0
Comment actions Permalink

Thanks, that makes sense, but is there a setting so I can control how that works, let's say I want to create a build-job with the purpose of only building non-master builds (all custom), I would like those to show up on the overview/history.

0
Comment actions Permalink

Is it possible to change this behavior back?

0
Comment actions Permalink

Currently this is not possible. If you need some other behavior please submit issue to our tracker. We would appreciate if you describe what builds you want to see on overview page and why.

0
Comment actions Permalink

A setting on the build to determine if custom builds (git branch != vcs-config) should be treated as personal builds (hidden) or just as normal builds.

0

Please sign in to leave a comment.