Saturday, August 6, 2011

TeamCity 6.5.3: BugFix Update

Here is a new update with the latest fixes for 6.5.x installations.

Data format is still the same, so you can downgrade to earlier 6.5.x versions if you need this for some reason.

We are mostly working on next major TeamCity version now, only integrating critical or easy fixes into 6.5.x branch. We will publish first 7.0 EAP in about three weeks.

BTW, if you are attending Agile 2011 in Salt Lake City next week, you are welcome to drop by JetBrains booth there for a live chat on TeamCity, YouTrack or other JetBrains products.

Friday, July 8, 2011

TeamCity 6.5.2: Fixes, Fixes, Fixes

Here is the build to upgrade your servers. Almost nothing really new, just fixes and several minor improvements mostly drived by your valuable feedback. See the report from the issue tracker for details.

The build uses the same data format as 6.5 and 6.5.1, so you can downgrade to 6.5.x if you need (but you hopefully do not).

BTW, if you have not yet checked recent update of JetBrains YouTrack to version 3.0, you might want to give it a try (free edition included). YouTrack team is also starting with YouTrack hosted offering, which definitely deserves a try if you need something lightweight yet powerful for your next project.

Like hosted YouTrack and want the same for TeamCity?
That's not something that we are already preparing while we do think about it.
We would really like to hear real-life stories why you need this and for what type of projects.

Wednesday, June 8, 2011

TeamCity 7.0 Features Discussion: Agent Pools

Apart from maintaining 6.5.x branch and addressing critical issues there, we are preparing for a jump into 7.0 features and spend quite a time elaborating general directions and specific features. We will surely start presenting them within upcoming EAP releases.

There is one of the minor features I'd like to ask your feedback for at this time. It is a so-called Agent Pools: ability to manage assignment of build configurations to agents not only on agent level, but for a set of agents. This is necessary to reduce configuration effort.
Apparently, this is only an issue for installations with many agents, but we get a continuous flow of  related requests from many customers.

Current idea that we want to start with is:

Allow creating an "agent pool" that will hold a set of agents. Each agent can belong to a single pool only. There is a default pool of agents that all agents initially belong to.

A pool has a set of associated projects. This means:
a) the agent in the pool can only run the builds belonging to the associated projects;
b) the builds from the build configurations within the projects can only be built on the agents of the associated pools (a single project can be associated with several agent pools).

We will still preserve current ability to select build configurations that can be run on a specific agent.

Now the question for you: Does this approach sound like a major help in simplifying your agent management needs? Is restricting the granularity to project level is enough for your specific case?

Feel free to vote in the poll (to the right on the main blog page) or leave your comments.

TeamCity 6.5.1 Bugfix Update

A fresh update is available on the download page for those of you who've encountered critical issues with 6.5 update.
Changes are mostly bug fixes addressing issues that we've introduced while implementing new features in 6.5.

The database structure is the same as with 6.5 which means that you can downgrade to 6.5 if something goes wrong with 6.5.1.

Thursday, May 26, 2011

TeamCity 6.5 is Here: New Features and Less Restrictive Free Edition

If you look through the What's New list of the release you are likely to see something useful for you.
We worked hard and we hope the release will make you a bit more happy with TeamCity and also with your builds.

The release both tweaks old things (like restyling web UI or renaming Responsibility into Investigation) and adds new strokes (like remote run on branches and test failures muting). These new directions are still to be fully explored and improved in the further releases based on your feedback.

Please make sure to look through the Upgrade Notes before you upgrade. It is recommended to test-drive the new version before upgrading your production TeamCity installation.

Our further plans are to start development of the next major version (TeamCity 7.0) and release updates to 6.5.x version with minor improvements and critical bug fixes if they surface.

Thursday, May 19, 2011

TeamCity 6.5 RC: Days For the Official Release

Here is a build that is one tiny step before the official 6.5 release. It has just several bug fixes over the previous one and is meant to be the last chance to try a build before the release.

If you consider upgrading to 6.5, consider trying the build and warning us on any misbehavior found.

A hint: this build still has an EAP license bundled (valid for 30 days) so this can be yet another reason to download and try it :)

In the mean time we are starting to think what could we bring in TeamCity 7.0 and you might add your thoughts as well :)

Thursday, May 12, 2011

TeamCity 6.5 Pre-Release: Less Restrictive Professional Edition and Stability Improvements

We are only  a small step away from 6.5 release and here is a build for you to try in your environment and let us know if anything goes wrong. The final 6.5 is planned to be released within a week or so.

Starting with this build we are dropping most limitations from Professional TeamCity edition except for the 20 build configurations limit. Now you can use per-project roles, any user authentication and more then 20 users in your TeamCity Professional installation.
As a professional user, you might be also interested in using more build configurations and here is a place to share your thoughts on this.


This build include a new way to install an agent onto a new machine: "agent push". Provided you have administrator credentials for a remote machine, you can now install a TeamCity agent on it right from "Agent Push" tab under Agents. The feature is in a bit "experimental" state, but we hope to improve it in further releases based on your feedback.

The build also further improves test muting and remote run on branches features as well as bundles PowerShell runner.

See more in the change log or full fixed issues list.

We ask you to try the build in your environment and let us know if anything goes wrong.

Get ready for the 6.5 release!