A new update for the TeamCity 7.1 with more then 150 fixes and improvements worth of one month team work is waiting for your downloads.
This 7.1.1 release comes with several performance and other improvements throughout the system as well as bug fixes. For the full list see issues in our issue tracker.
The release uses the same data format as TeamCity 7.1, so you can upgrade without data conversions and you can downgrade to 7.1 from 7.1.1 if necessary.
We will gradually switch our efforts to out trunk codebase and the next major TeamCity release but continue to fix issues in 7.1.x branch if they are uncovered.
For the two next weeks the TeamCity team will be experimenting with new ideas in the scope of an internal "ideas contest". I hope to share the most prominent results after that. Stay tuned!
Friday, September 21, 2012
Tuesday, August 7, 2012
TeamCity 7.1 Released: Feature Branches and More
The download page has just got an update to the official 7.1 release build (#23907).
If you were not following our EAP builds or want to get a round up, please review What's New documentation page.
Thank you all who tried the EAP builds and posted issues into the tracker. Hope, the release fixes some you care about.
This version uses updated data structure comparing to 7.0.x versions, so make sure you create a backup before upgrade.
For upgrading not-critical small installations, you can just install over and create a backup on the maintenance screen displayed on the first start of the upgraded version. For critical production installations, it is recommended to install a test server and only upgrade after checking important functionality in this new version.
Please also make sure to review Upgrade Notes for the list of changes which might affect your installation.
Our next plans are to release several 7.1.x updates based on your feedback and make up our minds on the next major release.
If you were not following our EAP builds or want to get a round up, please review What's New documentation page.
Thank you all who tried the EAP builds and posted issues into the tracker. Hope, the release fixes some you care about.
This version uses updated data structure comparing to 7.0.x versions, so make sure you create a backup before upgrade.
For upgrading not-critical small installations, you can just install over and create a backup on the maintenance screen displayed on the first start of the upgraded version. For critical production installations, it is recommended to install a test server and only upgrade after checking important functionality in this new version.
Please also make sure to review Upgrade Notes for the list of changes which might affect your installation.
Our next plans are to release several 7.1.x updates based on your feedback and make up our minds on the next major release.
Thursday, August 2, 2012
TeamCity EAP build #23892: 7.1 is Almost Here
We plan to release version 7.1 around next week, so this is really close: build 23892.
There are no major changes, just bug fixes and some polishing before the release. If you plan to upgrade to 7.1 when it will be released, it makes sense to try this EAP build to see how well it plays in your environment. In particular, if you plan to use the new feature branches support, make sure to try it out.
If you encounter any critical issues, please let us know the details via teamcity-feedback at jetbrains.com so that we still have chance to address it.
Please note that this build does not have EAP license key bundled already. You can get evaluation key on the official download page.
There are no major changes, just bug fixes and some polishing before the release. If you plan to upgrade to 7.1 when it will be released, it makes sense to try this EAP build to see how well it plays in your environment. In particular, if you plan to use the new feature branches support, make sure to try it out.
If you encounter any critical issues, please let us know the details via teamcity-feedback at jetbrains.com so that we still have chance to address it.
Please note that this build does not have EAP license key bundled already. You can get evaluation key on the official download page.
Monday, July 23, 2012
TeamCity EAP build #23833: Branches, Branches, Branches
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...
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...
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.
Monday, June 4, 2012
TeamCity EAP build #23373: NTLM SSO, Artifact Dependencies Changes, Always-Execute Build Steps and More
Last week we have published a new EAP build #23373 which reflects current state of our trunk, TeamCity 7.1 development. Sorry for the late announce here: Adriatic Sea around me last week was not very favorable for following the team's status closely.
As usual, you can get the list of most prominent changes in the change log or browse through the fixed issues list. While we are still in development phase we urge you to check the new features and let us know how well they suit your cases and how would you like to improve them. We still have some time to do some polishing before the release, so your feedback would be quite appropriate at this time.
A usual warning: EAP build might be unstable, so production installation upgrade is not recommended. You can try it as a test server, however. In any case, please create a backup of database and settings before upgrade to be safe if something goes wrong.
BTW, if you use JavaScript and use one of JetBrains IDEs with JavaScript support you might be interesting in a recent post in our official blog on setting up JavaScript inspections in TeamCity. Your comments are welcome!
As usual, you can get the list of most prominent changes in the change log or browse through the fixed issues list. While we are still in development phase we urge you to check the new features and let us know how well they suit your cases and how would you like to improve them. We still have some time to do some polishing before the release, so your feedback would be quite appropriate at this time.
A usual warning: EAP build might be unstable, so production installation upgrade is not recommended. You can try it as a test server, however. In any case, please create a backup of database and settings before upgrade to be safe if something goes wrong.
BTW, if you use JavaScript and use one of JetBrains IDEs with JavaScript support you might be interesting in a recent post in our official blog on setting up JavaScript inspections in TeamCity. Your comments are welcome!
Subscribe to:
Posts (Atom)
