Our current plan is to release 7.1 within several weeks so this is really close to the release.
Main team efforts are focused around polishing feature branches support, but there are also other improvements that we included at the last minute.
See the release notes and get the build to try now.
We encourage you to try the build on a test server i your environment and see how it works for your settings. If you find any critical issues please file them into the issue tracker.
And we are back to fixing last minute issues now...
Monday, July 23, 2012
Thursday, July 12, 2012
TeamCity 7.0.4 BugFix Update: Performance and Fixes
While we are approaching 7.1 release, we still integrate critical bug fixes into 7.0.x branch and here is the latest update for your production servers: 7.0.4 build #21474.
Included are various performance improvements which can affect large TeamCity installations, fixes in Subversion integration and more. See the full list.
There are no data structure changes comparing to 7.0.3, so downgrade to other 7.0.x releases is possible.
Anyway, it's a good time to create backup for your server. The one from Administration > Backup with "Basic" setting is usually enough.
If you want to prepare for upgrade to TeamCity 7.1, consider checking out our last EAP build and let us know how new features work for you.
Included are various performance improvements which can affect large TeamCity installations, fixes in Subversion integration and more. See the full list.
There are no data structure changes comparing to 7.0.3, so downgrade to other 7.0.x releases is possible.
Anyway, it's a good time to create backup for your server. The one from Administration > Backup with "Basic" setting is usually enough.
If you want to prepare for upgrade to TeamCity 7.1, consider checking out our last EAP build and let us know how new features work for you.
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.
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.
Subscribe to:
Posts (Atom)
