This is a small hint for those who host an open-source project on code.google.com.
If you want to setup TeamCity VCS labeling for your project, use the following in your SVN labeling settings field:
Saturday, April 11, 2009
Monday, April 6, 2009
New EAP build (8870): Boosted LDAP integration
With several last-minute fixes to LDAP integration (so last-minute we are are providing them as a separate download - see the note on Download Page), we are releasing the next EAP build from 4.1 series.
LDAP integration can now retrieve user details and groups membership as well as automatically create users in TeamCity once they appear in LDAP. The latter feature is useful for sending builds notifications to the users that do not even know about CI server.
With more UI polishing and bulk group operations, user groups feature is almost finished in this build.
A detailed changes description can be found in the release notes.
If you care either about user groups or LDAP integration please give these features a try and let us know your opinion. We plan to release 4.1 in several weeks and there is still a chance to fix major issues if you spot them.
LDAP integration can now retrieve user details and groups membership as well as automatically create users in TeamCity once they appear in LDAP. The latter feature is useful for sending builds notifications to the users that do not even know about CI server.
With more UI polishing and bulk group operations, user groups feature is almost finished in this build.
A detailed changes description can be found in the release notes.
If you care either about user groups or LDAP integration please give these features a try and let us know your opinion. We plan to release 4.1 in several weeks and there is still a chance to fix major issues if you spot them.
Wednesday, April 1, 2009
Cumulative JetBrains Products Update
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.
Please welcome TeamCity's Cash Options,
IntelliJ IDEA's Voice Control Plugin
and ReSharper's Configurator.
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.
Subscribe to:
Posts (Atom)
