As 7.0 release is only weeks away according to our plans, we will try to publish builds more often in a hope that more people will try them in order to check latest fixes.
Release notes are really small and the fixed issues list is also not long.
We have been experimenting with Subversion 1.7 working copy support for agent-side checkout and this build has the support bundled for you to try.
The build is on the usual EAP page.
Just do not forget to let us know if you find any issues with it.
Wednesday, February 1, 2012
Monday, January 23, 2012
TeamCity 7.0 EAP build 21075: Enhanced Dependencies Graph and Remote Settings Editing
As we are targeting TeamCity 7.0 release in about a month, this is the last EAP build with new features. We will focus on bug fixes and minor improvements to existing functionality until the release.
That is why it is important for us to get your feedback on this TeamCity build to be able to fix possible issues before the release.
This build further improves build dependencies visualization. To summarize, you get "Dependencies" tab for a build (listing all the build chains that include the build) and also for a build configuration (listing all the chains that include the builds of the build configuration). You can also "continue" a chain from the current state.
"Build chain" are all the builds interlinked with snapshot dependencies. This is a TeamCity notion that embraces build "pipeline". If you feel the need to get "pipelines" in TeamCity, this is the feature to try and give us your feedback.
Another long-awaited feature is to allow remote build configuration creation/modification. The functionality is now part of REST API. With it you can create new empty build configurations or copy existing ones as well as change individual settings like add a new build step / trigger / agent requirement. If you plan to use the feature you are highly welcome to try it and let us know how well it fulfills your needs. REST API is still scarcely documented, but you can get supported requests description via http://<your server>/app/rest/application.wadl request, which also has links to .xsd of the used entities.
Now it's time to browse through the release notes or full list of fixed issues, download and try it as a test installation.
You are welcome to share your feedback in the forum or by other means.
That is why it is important for us to get your feedback on this TeamCity build to be able to fix possible issues before the release.
This build further improves build dependencies visualization. To summarize, you get "Dependencies" tab for a build (listing all the build chains that include the build) and also for a build configuration (listing all the chains that include the builds of the build configuration). You can also "continue" a chain from the current state.
"Build chain" are all the builds interlinked with snapshot dependencies. This is a TeamCity notion that embraces build "pipeline". If you feel the need to get "pipelines" in TeamCity, this is the feature to try and give us your feedback.
Another long-awaited feature is to allow remote build configuration creation/modification. The functionality is now part of REST API. With it you can create new empty build configurations or copy existing ones as well as change individual settings like add a new build step / trigger / agent requirement. If you plan to use the feature you are highly welcome to try it and let us know how well it fulfills your needs. REST API is still scarcely documented, but you can get supported requests description via http://<your server>/app/rest/application.wadl request, which also has links to .xsd of the used entities.
Now it's time to browse through the release notes or full list of fixed issues, download and try it as a test installation.
You are welcome to share your feedback in the forum or by other means.
Tuesday, January 3, 2012
TeamCity 7.0 EAP build 20939: Restructured Admin Space, Changes Across Dependencies and More
With a bit of delay, here is an announcement of the recent TeamCity EAP build that the team published while I was spending last week of the year on a skiing holiday.
There are lots of new features both related to UI and logic. Please browse through the release notes to find those of interest to you. To get the details you are welcome to look through the fixed issues list.
We would appreciate if you try some of the features on a test installation of your server and let us know how well the features address your case and your opinion on UI changes.
If you use snapshot dependencies (which you really should for interdependent builds), try "Show changes from snapshot dependencies" option for the build configurations with dependencies.
If you have builds that need specifying additional parameters on every build run, typed parameters feature is to explore.
If you prefer to see TeamCity user names instead of VCS ones for the changes: the feature is already in.
I am sure you will find something new for you to explore in the build.
Our current plans are to polish features added in the recent EAP builds and prepare for the release of 7.0 which is planned for February. As we are approaching the release, your feedback on the features would be highly valuable at this time!
Friday, December 9, 2011
TeamCity 6.5.6: BugFix Update
We've updated our official download page with build 18130 which is stable TeamCity 6.5.6 release.
The version contains fixes related to IDEA and Visual Studio plugins, performance, Mercurial support improvements and more.
The same internal data storage format is used, so downgrade to any 6.5.x is possible.
BTW, we've got an IPhone app for TeamCity by one of our users. It displays last build statuses for selected projects. iOS 5 is required. You might find it useful if you often check how green is your project.
The version contains fixes related to IDEA and Visual Studio plugins, performance, Mercurial support improvements and more.
The same internal data storage format is used, so downgrade to any 6.5.x is possible.
BTW, we've got an IPhone app for TeamCity by one of our users. It displays last build statuses for selected projects. iOS 5 is required. You might find it useful if you often check how green is your project.
Thursday, November 24, 2011
TeamCity 7.0 EAP build 20702: My Investigations, Steps Disabling and Integrated NuGet Repostiory
This Thanksgiving fresh snapshot of upcoming TeamCity 7.0 is available for you to try at EAP page.
Almost no big new additions, just improvements all over the system and minor features like ability to disable build steps, displaying content of archived artifacts, My Investigations page, etc.
For .Net users, it might be interesting to try TeamCity as NuGet repository, which is first available in this release
See details in the release notes or browse through full fixed issues list.
Recently our team has got a new client-side developer and the EAP build already includes many of his changes. To name a few: search by build configuration name in a popup of Projects tab, fixed middle clicks, improvements in diff view. Welcome, Leonid!
So if you have any issues with layout/browser behavior of TeamCity web UI - they now have more chances of being fixed soon. Let us know about them!
Almost no big new additions, just improvements all over the system and minor features like ability to disable build steps, displaying content of archived artifacts, My Investigations page, etc.
For .Net users, it might be interesting to try TeamCity as NuGet repository, which is first available in this release
See details in the release notes or browse through full fixed issues list.
Recently our team has got a new client-side developer and the EAP build already includes many of his changes. To name a few: search by build configuration name in a popup of Projects tab, fixed middle clicks, improvements in diff view. Welcome, Leonid!
So if you have any issues with layout/browser behavior of TeamCity web UI - they now have more chances of being fixed soon. Let us know about them!
Thursday, October 27, 2011
TeamCity 6.5.5: BugFix Update
While we are developing TeamCity 7.0, some important fixes are being back-ported to 6.5.x branch to deliver the fixes to you earlier then in 7.0 release.
Latest branch snapshot is released as 6.5.5 today and is available from the official download page.
Update is recommended for all users as there were some performance improvements. See the full list of fixed issues.
Data format is the same as in all 6.5.x releases, so if you are already on 6.5.x, it is possible to downgrade if necessary. Anyway, creating the backup before the upgrade is highly recommended.
Latest branch snapshot is released as 6.5.5 today and is available from the official download page.
Update is recommended for all users as there were some performance improvements. See the full list of fixed issues.
Data format is the same as in all 6.5.x releases, so if you are already on 6.5.x, it is possible to downgrade if necessary. Anyway, creating the backup before the upgrade is highly recommended.
Tuesday, October 11, 2011
TeamCity 7.0 EAP build 20334: Dependencies Graph, ReSharper-Powered Inspections and More
And here we are with a new snapshot of the current TeamCity 7.0 state: EAP build 20334.
This build adds several highly voted features:
Dedicated setting for per-checkin builds in VCS trigger. If your builds are fast and you have enough agents you can now tick the option to ensure TeamCity includes no more then a single new change in a build. This could have been emulated with the quiet period setting for a long time, but now it works more reliably and is more obvious to use. BTW, we used the approach for R# builds before their release. That bit quite a bit of our agents farm but the approach gave the team more confidence in the changes and that proved very useful.
Visualization of build's snapshot dependencies graph. Build's Dependencies tab was reworked to display the entire graph of the build chain. The view allows to see the big picture if your setup is not too complex. We have thought on moving it further, but need your feedback to adjust our plans. If you use snapshot dependencies much, try installing this EAP build as a test server, share your graphs and let us know what would you like from it.
Ability to ask for certain properties on manual build run. This has been added as a part of introducing "meta-data" for build configuration properties: display label, type, required flag. So far this is configured via a tricky syntax, but is likely to be improved if the feature is well-received.
For you, Git and Mercurial users, we have added visualization of changes' parent/child relationships on Change Log tab of a build configuration.
And for you, .Net teams, we have bundled a ReSharper-powered tool that allows to run solution-wide analysis inside TeamCity and browse the results in the browser.
Read all the details in the release notes or look through the resolved issues.
While we use this EAP build on our production server, it is not recommended to use it on yours if you cannot rollback to the latest stable TeamCity (6.5.4) losing all the data collected in this EAP version. If you risk, ensure you have a good backup beforehand!
However, trying the features on a test installation and letting us know whether it covers your needs or not is highly anticipated.
This build adds several highly voted features:
Dedicated setting for per-checkin builds in VCS trigger. If your builds are fast and you have enough agents you can now tick the option to ensure TeamCity includes no more then a single new change in a build. This could have been emulated with the quiet period setting for a long time, but now it works more reliably and is more obvious to use. BTW, we used the approach for R# builds before their release. That bit quite a bit of our agents farm but the approach gave the team more confidence in the changes and that proved very useful.
Visualization of build's snapshot dependencies graph. Build's Dependencies tab was reworked to display the entire graph of the build chain. The view allows to see the big picture if your setup is not too complex. We have thought on moving it further, but need your feedback to adjust our plans. If you use snapshot dependencies much, try installing this EAP build as a test server, share your graphs and let us know what would you like from it.
Ability to ask for certain properties on manual build run. This has been added as a part of introducing "meta-data" for build configuration properties: display label, type, required flag. So far this is configured via a tricky syntax, but is likely to be improved if the feature is well-received.
For you, Git and Mercurial users, we have added visualization of changes' parent/child relationships on Change Log tab of a build configuration.
And for you, .Net teams, we have bundled a ReSharper-powered tool that allows to run solution-wide analysis inside TeamCity and browse the results in the browser.
Read all the details in the release notes or look through the resolved issues.
While we use this EAP build on our production server, it is not recommended to use it on yours if you cannot rollback to the latest stable TeamCity (6.5.4) losing all the data collected in this EAP version. If you risk, ensure you have a good backup beforehand!
However, trying the features on a test installation and letting us know whether it covers your needs or not is highly anticipated.
Subscribe to:
Posts (Atom)
