Feature request: Easy way to add build configurations for every git branch

I want an automated build out of almost every branch in my git repo.  It's pretty manual to add build configurations (even with the configuration copy link) for each branch.  Can we get this automated?

Also, it seems like at least with the git plugin that each build configuration has to have its own git repo, which is then checked out from, making effectively two git clones for every build config . Is there a way to reduce this?   

5 comments
Comment actions Permalink

Hi!

Seems, you are using git plugin from github project. It is not affiliated with JetBrains, so we cannot address clones optimization.

Actually, we will open EAP within days for our own git support plugin and it will not have double clone issue because the checkout will be handled on the TeamCity server side.

Can you please elaborate on automation of every branch build?
How many branches do you have? What is the nature of the branches - are they per-developer or per-feature or per-client, etc?
Is branches set constant or it evolves over time?

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

--
Best regards,

Yegor Yarko
Project Manager (TeamCity)
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Wow, thanks Yegor for your response that makes me feel like you're really thinking about my request and various ways you could do it.

Seems, you are using git plugin from github project. It is not affiliated with JetBrains, so we cannot address clones optimization.




That's right, I'm using that plugin.  I understand you can't support that one.  It was more of a feature request for the built-in support for Git I heard was coming.

Actually, we will open EAP within days for our own git support plugin and it will not have double clone issue because the checkout will be handled on the TeamCity server side.




Within days?  That's freakin' awesome!

Can you please elaborate on automation of every branch build?
How many branches do you have? What is the nature of the branches - are they per-developer or per-feature or per-client, etc?
Is branches set constant or it evolves over time?




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.

Thanks a bunch.  I look forward to seeing what you can do!

0
Comment actions Permalink

Andrew,

Thank you very much for the description of your case.

I've created an issue so the feature can be trackable and vote-able.

We will consider it when planning features for TeamCity next major release (5.0).

0
Comment actions Permalink

Yegor,

What is the issue number for this? I definitely want to vote it up! I think it would be an awesome feature for TeamCity to monitor for new branches and auto-create new build configs for them. I'm actually planning to build a plugin to make this very thing happen, but of course, it'd be even better if the product supported this out of the box! :)

0

Please sign in to leave a comment.