Reordering tests order to run recently failed or modified tests first
If your build uses Ant runner and JUnit/TestNG tasks to run your tests (or Ipr runner with tests configured or tests run via post-build Ant script), now you have the option to instruct TeamCity to change the order of running your tests. Available options are to run the recently failed tests first, or recently modified tests first.
This is as simple as checking an option in the runner's settings and allows you to know if the tests were fixed in a much less time.
The tests are reordered within each junit/testng Ant task on the test case (not individual test) level.
Of course, the options are safe to use only if your tests order does not affect tests functioning (which is a good thing). If the tests order is significant, but this is an undesired behavior, you can still use the option to discover such dependencies
Now each project has a dedicated page. Currently it is only a list of the project build configurations and selected charts for the build configurations. The work is still in progress, more statistics and project-level reports will be included.
Here is how the project charts can look like (the LOC metric is added as a custom graph, we will publish the instructions on how to do that in your builds with further EAP releases)
Your suggestions so to the page content/necessary information on it are highly welcome.
Now, "first failure/success" notifications are also supported for "Builds with my changes" notifications. What's more, now you can fine-tune notifications by customizing the order in which the notification rules are processed. The first one that matched the build is executed, the rest are ignored. This provides you with an ability for example to suppress notifications for certain build configurations.
Custom statistics now supports multiple series display on a single chart
You can display several values on the custom values chart now:
Read more about custom statistics feature in the online documentation.
- Ability to view the builds that used artifacts of this one. See Dependencies tab of the build results.
- Now you can download tests list in CSV format for off-line analyzing. The download link is available form the Tests page of the build results.
- Ability to check artifact dependencies right from the configuration page: no need to run a build to check the dependencies configuration.
- Multiple performance improvements
- Reworked build stopping logic under Linux/Mac OS X. No more native libraries dependencies.
- Now when cleaning sources on agent you can select the build configurations to be affected.
- Now plugin authors can package plugins more easily and plugin deployment become more straight-forward with a separate plugin storage under TeamCity Data directory (.BuildServer). Stay tuned for details in the future EAP releases.
- New plugins to ease tests reporting for Python, C++.
- We also opened EAP for the Rake runner plugin. In you develop in Ruby and use Rake for building your projects, give it a try.
- Due to improved VCS hash calculation, all build configurations will perform clean checkout on the first run with this new build. The default checkout directories (hash) names will also be changed.