14 comments
Comment actions Permalink

here is a screen that shows what i'm talking about

http://screencast.com/t/Wn7lcrbl3Lq

0
Comment actions Permalink

What version of TeamCity do you use?

0
Comment actions Permalink

We just upgraded to 7.1.5 from I'm assuming 7.1.4. However it is still happening after the upgrade.

0
Comment actions Permalink

How these builds are triggered?

0
Comment actions Permalink

In this case manually, i.e the 'Run' button. We have config properties that show a dialog box, so we enter a branch (e.g. v24). We have some builds that are triggered on vcs changes but we haven't seen this problem with those.

0
Comment actions Permalink

When you trigger custom build and TeamCity determines that some of parameters will affect version control settings it must present you with warning about auto branch. Do you see this warning? It is only shown if teamcity.build.branch parameter is not specified. If this parameter is specified TeamCity must use value from this parameter.

0
Comment actions Permalink

I'm not sure what 'auto-branch' is and No, we've never seen any such warning. If we run the build and do not enter a value for branch when prompted, the build will still attempt to run. Although there is no regex to enforce a value for the branch property, the actual build script requires it and the build will fail without it.

0
Comment actions Permalink

p.s.

we're not using teamcity.build.branch parameter. we have defined a 'branch' build parameter that is a prompt so we can enter a branch name.

0
Comment actions Permalink

Ok i think I'm seeing now this warning you mentioned, however i've never seen it before. I assume this is new in 7.1.5?

0
Comment actions Permalink

It was added in version 7.1.1. It's strange you did not see it before.


0
Comment actions Permalink

It is possible we were using a version prior to 7.1.1. Can we disable that notification?

0
Comment actions Permalink

You can control branch marker in build with help of teamcity.build.branch parameter. If this parameter is specified, TeamCity won't show this warning.

0
Comment actions Permalink

We don't have build configurations for every branch which i assume is the intention with teamcity.build.branch ?

Is there some documentation on that parameter? What it is for and how it is supposed to be used?

0
Comment actions Permalink

Branch specific parameters are described here: http://confluence.jetbrains.com/display/TCD7/Predefined+Build+Parameters#PredefinedBuildParameters-BranchProperties
teamcity.build.branch actually works both ways. If it is specified in build manually - it affects branch label of the build. If it is not specified, TeamCity will generate branch label automatically and set this parameter. This behavior currently is not documented, and we're looking for a better solution.

0

Please sign in to leave a comment.