Recently, we've released a bugfix update 4.5.5 (see the fixed issues). Update is recommended for all users. Most notable additions are support in Eclipse plugin for Perforce 2009.1 integration plugin and improved compatibility with the latest IntelliJ IDEA (Maia EAP) builds.
Also a new EAP build is published.
The most important feature added are templates for the build configurations. Now you can create a template configuration and reuse its settings in others. Current approach does not allow to change much in the configurations using templates: except for the basic settings, only the build configuration properties can be altered. This means that if a value is intended to be changed in the build configurations using the template, it should be defined with a property reference. As a note, VCS roots do not support properties references and probably will not in the nearest future. However, the references are supported in the checkout rules.
We wait for your feedback on the feature to know how good this covers your cases and what improvements you definitely need.
The work is also ongoing on:
- Maven integration: trigger builds on repository artifact change is a new addition to creating a configuration from pom.xml;
- Amazon EC2 integration: can now create profiles in the web UI. We are working on dynamic agents start/shutdown - see the next EAP build;
- UI improvements: see the revamped My Changes and improved change details pages;
- Backup/restore: improved stability.
This EAP build also is compatible with the latest Maia EAP (build 10762).
If you care about any of the features mentioned, please let us know what you think and what improvements you might need.
BTW, you can also voice your thoughts in person to Pavel and me if you participate in CITCON Europe 2009 this weekend :)
Wednesday, September 16, 2009
Tuesday, July 21, 2009
TeamCity 5.0 Codename Darjeeling EAP is Open
Today we published the first build of TeamCity 5.0 EAP. It includes all the fixes of 4.5.4 and lots of new features and fixes.
The complete list of new features is available on the EAP change log.
A bit of detail about the features that we want your feedback most about.
Once you configure the issue tracker connections on the Server Configuration > Issue Tracker page and specify a project key (e.g. "TW"), each TW-5286 -style text in the commit comments and build comments will get a drop-down with the issue details. Also, a build gets "Issues" tab with the list of the issues related to the build (mentioned in the commit comments). A Build Configuration page gets Issue Log tab much like Change Log.
TeamCity can determine in what build an issue is fixed. This works good provided each fix to an issue have issue id in the commit comment and the issue is resolved by the developer. (The build the issue is fixed in is obviously the last one with a related change.) If the issue is reopened or another related fix is committed, the issue will automatically be bound as fixed to the newer build.
Does this case suits your issue tracker usage scenarios? Do you want TeamCity to support other cases? Tell us what you think about it.
What's next?
The next EAP release will introduce enhanced Maven2 support and ability to create TeamCity backup right from the web UI. And there is more.
Stay tuned!
- Some obsolete projects cluttering the UI? — Archive them
- Like to watch the build printing lines into console? — Now you can do that in TeamCity too.
- Need easier integration with NCover or PartCover? — Now you get it in .Net-specific runners.
- Shoulda understood how Cucumber is related to testing? — See the updated Rake runner settings.
- Want to see TeamCity internal server logs? — Grab them form the web UI.
- Need Java code coverage without class files instrumentation? — Use IntelliJ IDEA Coverage that is now bundled in TeamCity.
The complete list of new features is available on the EAP change log.
A bit of detail about the features that we want your feedback most about.
Issue tracker integration
We've added support for Jira, Bugzilla and Charisma (JetBrains tracker). If your favorite tracker is not listed you can add the support with a custom TeamCity plugin.Once you configure the issue tracker connections on the Server Configuration > Issue Tracker page and specify a project key (e.g. "TW"), each TW-5286 -style text in the commit comments and build comments will get a drop-down with the issue details. Also, a build gets "Issues" tab with the list of the issues related to the build (mentioned in the commit comments). A Build Configuration page gets Issue Log tab much like Change Log.
TeamCity can determine in what build an issue is fixed. This works good provided each fix to an issue have issue id in the commit comment and the issue is resolved by the developer. (The build the issue is fixed in is obviously the last one with a related change.) If the issue is reopened or another related fix is committed, the issue will automatically be bound as fixed to the newer build.
Does this case suits your issue tracker usage scenarios? Do you want TeamCity to support other cases? Tell us what you think about it.
Eclipse and MS Visual Studio plugin changes
The Remote Run dialog was reworked in both. If you use one of these - tell us what you think so that we can consider your feedback and improve things before the release.What's next?
The next EAP release will introduce enhanced Maven2 support and ability to create TeamCity backup right from the web UI. And there is more.
Stay tuned!
Wednesday, July 8, 2009
Teamcity 4.5.4 bugfix release is ready
Tuesday, June 16, 2009
TeamCity 4.5.3 is here to fix 4.5.2
It happened that 4.5.2 release had Rake runner nonfunctional :(
Sorry about that. We fixed the issue right away but need to provide updated distribution so that less users are affected.
So here it is: TeamCity 4.5.3.
The main development is already done in to-be-5.0 trunk but for the week since 4.5.2 release we integrated several fixes and improvements into 4.5.x branch. Here is what our tracker reports for 4.5.3.
BTW, "Cheers" to all the users who showed up at our JavaOne booth. Thank you for the feedback and do not hesitate to post and discuss more in the forums.
Sorry about that. We fixed the issue right away but need to provide updated distribution so that less users are affected.
So here it is: TeamCity 4.5.3.
The main development is already done in to-be-5.0 trunk but for the week since 4.5.2 release we integrated several fixes and improvements into 4.5.x branch. Here is what our tracker reports for 4.5.3.
BTW, "Cheers" to all the users who showed up at our JavaOne booth. Thank you for the feedback and do not hesitate to post and discuss more in the forums.
Tuesday, June 9, 2009
Teamcity 4.5.2 is available
Hello everyone,
The second update of TeamCity 4.5 is available for download.
The second update of TeamCity 4.5 is available for download.
The list of changes is available in our tracker and on our main site.
This build contains an updated version of SVNKit library (1.3.0), so it should behave more nicely with Subersion 1.6 repositories.
Let us know about issues found, if any.
Kind regards,
KIR
Labels:
4.5.2,
announcement,
maintenance,
release,
subversion,
svn
Monday, May 25, 2009
Meet us at JavaOne
Want to meet in person with guys behind TeamCity, IDEA or MPS? Eager to see the products in action or describe pain points? Come to JetBrains booth at JavaOne (June 2-5).
Thursday, May 7, 2009
Subscribe to:
Posts (Atom)