If you do not know already, today we are announcing a pack of new features to all JetBrains products.
Please welcome TeamCity's Cash Options,
IntelliJ IDEA's Voice Control Plugin
and ReSharper's Configurator.
Wednesday, April 1, 2009
TeamCity Tracker Upgrade
About a year ago we migrated our TeamCity issue tracker from JetBrains Jira to a new tracker that is developed in-house. The dogfooding is great - the developers are several rooms away and you can always go complain in person rather then trying to write everything down :)
The tracker (its codename is Charisma) has been evolved a lot since then, but there were no changes visible for the last couple of months. Why? Because of the new completely rewritten UI and the whole new approach to replace the current one. These changes could not be done incrementally and were developed under cover for quite a while. BTW, thelanguage technology behind Charisma is MPS and that makes the development much more fun.
A week ago a new update was pushed to www.jetbrains.net/tracker and now all the users can try the new UI themselves. The old one ("workspace") will be abandoned soon.
So head to your profile ("Settings" tab) in the tracker and check "Use New UI" checkbox.
You will then be redirected to new UI URL: www.jetbrains.net/tracker/issues.
The workspace can still be reached by www.jetbrains.net/tracker/oldWorkspace, but if you ever need it - let us know why. We will need to improve new UI before we drop the old one for good.
Do you like new UI? Any difficulties using it? We need your feedback! Found a bug? Post it right into Charisma.
The tracker (its codename is Charisma) has been evolved a lot since then, but there were no changes visible for the last couple of months. Why? Because of the new completely rewritten UI and the whole new approach to replace the current one. These changes could not be done incrementally and were developed under cover for quite a while. BTW, the
A week ago a new update was pushed to www.jetbrains.net/tracker and now all the users can try the new UI themselves. The old one ("workspace") will be abandoned soon.
So head to your profile ("Settings" tab) in the tracker and check "Use New UI" checkbox.
You will then be redirected to new UI URL: www.jetbrains.net/tracker/issues.
The workspace can still be reached by www.jetbrains.net/tracker/oldWorkspace, but if you ever need it - let us know why. We will need to improve new UI before we drop the old one for good.
Do you like new UI? Any difficulties using it? We need your feedback! Found a bug? Post it right into Charisma.
Tuesday, March 31, 2009
VAN meeting: TeamCity Live Demo
Zachariah Young kindly invited someone from JetBrains to present at one of the Virtual ALT.Net online meetings about TeamCity. We accepted and will be giving a demo this Wednesday.
Virtual ALT.Net is a virtual group that meets once a week to talk about different alt.net topics. Current topic is on automated build and continuous integration.
More details in Zachariah post.
It will be early morning in Saint-Petersburg, but I will try not to fall asleep :)
Virtual ALT.Net is a virtual group that meets once a week to talk about different alt.net topics. Current topic is on automated build and continuous integration.
More details in Zachariah post.
It will be early morning in Saint-Petersburg, but I will try not to fall asleep :)
Thursday, March 19, 2009
New EAP build (8804): XML reports, support P4 in VS, more tests analyzing tools
During this week we were trying to get a build that we would consider EAP quality.
But as soon as one issue was fixed, another poped out and that delayed the EAP release at least half a day more. Our full build cycle takes about 4 hours. This includes many steps from Java and .Net code compile through unit tests on 4 platforms and and 5 different environments to assembling distribution packages. This process is split in about 20 steps (build configurations) and we share a common build factory with IDEA, ReSharper and other JetBrains products, so a full cycle make take a while.
Finally, after some battles we grabbed a build and are throwing it into EAP: build 8804.
Be sure to read through the release notes as it may expose unusual behavior in respect to user's default settings - read the yellow block in the notes for details.
One of the highlights of the build is bundled XML report plugin. The plugin was available for several months as a separate download and now it has reached the state we can bundle it into the distribution. But be sure to add tests reporting only if you do not see test in TeamCity UI already. Otherwise, you will get each test reported twice: once by automatic TeamCity listener and another from the XML report.
Have PMD or FindBugs reports generated during the build? Configure the report importer an get the results in TeamCity inspections browser empowered with "open in IDE" functionality.
Use Perforce and longing for the Remote Run functionality in Visual Studio? Now you get it.
Need a bird-eye view on a test in the scope of the entire project? Test details are now project-wide.
Badly want another feature? Go vote for it in our tracker (or submit a new one).
As usual, your feedback is highly appreciated.
But as soon as one issue was fixed, another poped out and that delayed the EAP release at least half a day more. Our full build cycle takes about 4 hours. This includes many steps from Java and .Net code compile through unit tests on 4 platforms and and 5 different environments to assembling distribution packages. This process is split in about 20 steps (build configurations) and we share a common build factory with IDEA, ReSharper and other JetBrains products, so a full cycle make take a while.
Finally, after some battles we grabbed a build and are throwing it into EAP: build 8804.
Be sure to read through the release notes as it may expose unusual behavior in respect to user's default settings - read the yellow block in the notes for details.
One of the highlights of the build is bundled XML report plugin. The plugin was available for several months as a separate download and now it has reached the state we can bundle it into the distribution. But be sure to add tests reporting only if you do not see test in TeamCity UI already. Otherwise, you will get each test reported twice: once by automatic TeamCity listener and another from the XML report.
Have PMD or FindBugs reports generated during the build? Configure the report importer an get the results in TeamCity inspections browser empowered with "open in IDE" functionality.
Use Perforce and longing for the Remote Run functionality in Visual Studio? Now you get it.
Need a bird-eye view on a test in the scope of the entire project? Test details are now project-wide.
Badly want another feature? Go vote for it in our tracker (or submit a new one).
As usual, your feedback is highly appreciated.
Friday, February 20, 2009
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.
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.
Tuesday, February 3, 2009
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:
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.
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.
Subscribe to:
Posts (Atom)
