4.1 EAP is open

Let us share the results of our last months work on TeamCity. We branched on 4.0.x and 4.1 releases about the same time 4.0.1 was released, and the main work effort is undergoing in the 4.1 branch since. We were continuously upgrading the internal TeamCity installation (and fixing emerging issues right away). As we reached a certain point in features and have quite stable build, we are ready to make the build public.

You can read through the release notes to get overview of the changes.

One of the main features we are introducing is user groups.
Groups store users and can be assigned roles, just like users. A user then gets all the directly assigned roles and all the roles assigned to the groups she belongs to. A group can contain other groups and users, it can also be included into several groups. Currently you can assign roles and add users on the group details page.

Our nearest plans are to add notifications to groups - they will work as default notifications for all the members of the group. Also under way is LDAP integration with automatic retrieval of user-groups correspondence from LDAP.

Please let us know your groups usage scenarios so that we can consider them when enhancing TeamCity groups support.

Get the build from EAP download page. And let us know what you think about the new features participating in the poll to the right.

TeamCity 4.0.2 is out

Our download page has got a new update with 4.0.2 link.

As we are working on 4.1 since about 4.0.1, so 4.0.2 is a branch which got only critical bugfixes and urgent improvements.
Generally, you will want to upgrade from 4.0.1 to 4.0.2 if:

• you are using snapshot dependencies and spot build queue growing large with automatically triggered builds of the same build configuration (now we merge them more aggressively)
• you often have builds with lots of failing tests (performance fixes)
• you are using SVN (several fixes incl. performance)
• you are using CVS (fixes in pre-tested commit from IDEA, other)
• you use TFS with large repositories and experience performance issues (we added TFS agent-side checkout, it is a bit experimental, though)
• you are using MSTest reporting (stability fixes)
• you have extra large build numbers (we increased the length from 32 to 256 symbols). In the trunk we also truncate build numbers in web UI to make them usable. This will soon be available in 4.1 EAP
• or if you experienced one of the fixed issues

Need user groups support? Want to move a build configuration from one project to another right from the web UI? These are the features already in development for upcoming TeamCity 4.1. We plan to open EAP for it in a week or so.