Wednesday, July 4, 2012

TeamCity EAP build #23732: Feature Branches and More

With this new EAP build we are introducing dedicated support for feature branches development practice. The only supported version controls are Git and Mercurial. Support for others might be added too, but not in TeamCity 7.1.


VCS roots has got a new "Branches" field where you can specify patterns for the branches to monitor. The changes are then processed as usual. They are displayed as pending and VCS trigger will trigger builds for them. The builds triggered for non-default branch will  display the branch name. You will be able to filter builds by branches in UI. At the same time, some of the features like notifications and build status work only for the default branch.

If you use Git or Mercurial and use feature branches we would appreciate if you can install a test server and see how this functionality plays for you. We are eagerly awaiting for your feedback for the feature.

For details and other improvements see release notes and full fixed issues list if interested.

Our plans were to release TeamCity 7.1 in about a month and we are reevaluating them now. Options are  to confirm the plans or postpone the release until September.

5 comments:

FreshCode said...

Been waiting for this. Thanks JetBrains!

Anonymous said...

Are there any plans for feature repositories?

Yegor Yarko said...

> Are there any plans for feature repositories?

Can you please detail what exactly you mean by feature repository? What kind of support do you need?

Micah Martin said...

I started using the featurebranch feature today and it's working great. Where do I leave feedback and ask questions?

Yegor Yarko said...

Micah,
Forum is a good place to start with. All the ways are listed at the page linked from TeamCity footer.