This roadmap comprises the features selected for implementation in TeamCity 4.0 release (codename Calcutta) that is scheduled to arrive in the fall 2008. The list includes only the most noteworthy features. Of course we will also address many more smaller ones. If you want to let us know that one of the minor features is important for you, please find and vote for it (or create it) in our issue tracker.
Please note that not all of the mentioned features will be included in the final release. While we strive to deliver as many new features as possible, we prefer to deliver less but maintain the quality high.
Legend:
- Already partly implemented, you can try them in the scope of EAP.
- Composite builds and enhanced build dependencies
Ability to divide a single build procedure into several parts/builds that can be run on different agents both in sequence or in parallel. Ability to use the same set of sources in all of them.
- History builds
Repeat a build using the same revision of the sources as a finished build.
- Tests reordering/selection
Run "risk group" tests first (failed in previous builds, frequently failing).
- Project-wide and comparative statistics
Display project charts (from different build configurations) on a single page.
More statistics types, like number of changes per developer, failures per project.
- Take Responsibility Improvements
Allow to take responsibility per-problem (test or compilation failure), assign responsibility.
- Comments
Ability to add a comment for a finished build, agent.
- Improve Eclipse plugin
Allow to commit failed pre-tested commit manually, list previous commit messages in the remote run dialog, etc.
- Improve plugin support
Load plugins from dedicated directory, pack bundled plugins as plugins.
- Ease large setups administration
Introduce user groups to assign roles
- .Net frameworks integration improvements
Improve MSTest integration.
Dedicated runner for FxCop.
- Tools integration
Mercurial VCS support
Rake runner support for building Ruby projects
Features planned for post-4.0 releases
- Build promotion
Ability to execute a build based on a finished build, e.g trigger functional tests for the same sources, deploy a build, upload build artifacts to FTP, etc.
- Project-wide and comparative statistics
Ability to compare metrics across projects.
- Flaky tests marking
Mark tests as ignored so that they are run but not used for the build success/failure state determining.
Help to identify tests that tend to fail occasionally without any changes.
- Team changes tracking
Merge prevention: notify if someone on the team has uncommitted changes that are incompatible with yours.
Ability to see current change lists for any team member, ability to download patch from the web for personal builds.
- Per-failure builds analyzing approach
Commit personal build when no new test failed, notify only on new problems in the build, display tests found and lost since previous build.
- Ease large setups administration
Support for comparing build configurations settings, LDAP integration improvements.
We want to hear your feedback on these or missing features, do not hesitate to drop us a line.