Project
TeamCity
Priority
Normal
Type
Feature
State
Open
Assignee
Dmitry Neverov
Subsystem
Server
Affected versions
No Affected versions
Fix versions
Medium Priority Pool
Fixed in build
No Fixed in build
Fixed in builds
no build yet
  • Created by   Yegor Yarko
    3 years ago (09 Apr 2009 22:40)
  • Updated by   Yegor Yarko
    5 months ago (28 Nov 2011 17:41)
 
TW-7869 Automatically create build configurations for every new git branch
29
Issue is visible to: All Users
  The issue is visible to the selected user group only
from http://www.jetbrains.net/devnet/message/5235473

aarnott:
I have a branch for every minor version of the project, and then a few feature branches that come and go as needed, and I'd like build configurations for all of these. So for example, I have "master" for the next big thing, and then maintenance branches for "v2.5", "v2.4", "v2.3", etc. In each of these branches I have tags for each revision, such as v2.5.4. Feel free to visit http://github.com/AArnott/dotnetopenid/ if you want to see the branches as I use them directly. So right now I have about a dozen branches I would want to build. Then I have a few other branches that don't contain source code, or whose source base is so old the build configuration would have to be adjusted for.

Do you think of automatic build configuration creation for every new branch or some other approach?



Yes. As soon as a branch is created on the repository that TeamCity pulls from, I'd like a build configuration to be automatically created based on some template configuration. After these configurations are created, I may need to customize them and/or delete them and they should stay altered/deleted, but by far the most common case would be a build for every new branch.
Comments (13)
 
History
  
Linked Issues (?)
 
James Summerton
  James Summerton
23 Nov 2009 13:22
2 years ago
Couldn't you just have TeamCity build against any tracked branch in the VCS Root when there is a change and have that flowed through all related builds?
Yegor Yarko
  Yegor Yarko
02 Dec 2009 18:31
2 years ago
Also requested in comments to post
Mark Derricutt
  Mark Derricutt
17 Sep 2010 12:51
20 months ago
Is this likely to come soon at all? We've just moved over to git and I'm thinking about the lack of CI as we move to using feature branchs. As well as automatically building each branch above, I'd love to have some form of "integration build" that automatically merges feature branches into an integration branch.

From a configuration side - I'd see configuring a glob/regex pattern for which branches to merge in - any merge failure would be an immediate build breaker.
Yegor Yarko
  Yegor Yarko
17 Sep 2010 16:06
20 months ago
Mark,

We are currently working on TW-8326. However, I am not sure the feature will be stable enough in two month and it might be not included into TeamCity 6.0.
However, it has good chances to be available in 6.1 (probably in abound 6 month).

After TW-8326 is implemented (so a commit into a branch whose name matches some pattern automatically creates a personal build in TeamCity), we will try to implement support for pushing the branch's changes into master - this looks like what you request except for the builds being personal.
Yegor Yarko
  Yegor Yarko
21 Oct 2010 21:33
19 months ago
Also requested by TW-13882 (mentions git-flow)
Related Changes
is duplicated by
TW-13882: Support VCS branches by convention
Marina Grechko
  Marina Grechko
25 Oct 2010 16:45
19 months ago
Yegor Yarko
  Yegor Yarko
24 Nov 2010 14:03
18 months ago
Michael Kuzmin
  Michael Kuzmin
04 Feb 2011 15:45
15 months ago
Michael Kuzmin
  Michael Kuzmin
30 May 2011 13:51
11 months ago
Yegor Yarko
  Yegor Yarko
30 May 2011 14:28
11 months ago
TW-16052 seems to be an alternative approach to alike need: build many branches as builds in a single build configuration, "tagging" them with branch name and allowing to review a single or several branches.
Ryan Hansen
  Ryan Hansen
07 Sep 2011 19:10
8 months ago
My company would love this feature! We'd like to just setup the build off of master and have all new branches copy and use that configuration when they get created.
Barnabas Debreczeni
  Barnabas Debreczeni
19 Oct 2011 23:34
7 months ago
we'd love to have this feature too!
Yegor Yarko
  Yegor Yarko
28 Nov 2011 17:41
5 months ago
Dear voters/watchers,

Feature to support building off different DVCS branches has at least two approaches: requested by this issue (create separate build configuration for every new branch) and TW-16052 (build different branches inside one build configuration, tag the builds appropriately).

Difference between the approaches is summarized in the comment.
We would appreciate if you can let us know which approach better suits YOUR needs.