Today we publish yet another bug-fix EAP build. In addition to a number of fixed issues (see the whole list), this build adds an ability to change project level parameters by means of REST API. See the release notes.
Download and try it!
Looking forward to your feedback!
The closer we get to the finial TeamCity 7.0 release date, which by the way is a matter of few weeks, the more we need your feedback on the EAP builds. So we decided to publish them more often than we usually do. Today’s build comes with a number of improvements and bug-fixes that mostly address REST API, user interface and build triggers. See the release notes.
We have also added support for Subversion 1.7 for both checkout on server and checkout on agent, and introduced new permission “View user profile” that restricts/allows access to user email and settings.
We encourage you to try the latest EAP build and give us more feedback.
Enjoy!
Today’s TeamCity 7.0 EAP is the last EAP build with new features in it, as starting from it we are going to focus on fixing bugs and polishing already announced functionality. So basically, this build is more or less what TeamCity 7.0 is going to look like. So here’s what we have for you today.
A feature request to allow build configuration editing via REST, that has been around for a while, has finally been implemented, so now you can get complete settings of a build configuration or template via REST and change them as well. Moreover, you can create and delete build configurations, projects and VCS roots.
See the details in release notes.
We would appreciate if you could try the updated REST API and let us know about any issues or suggestions that you might have.
If you have been following the EAP program you’re probably already familiar with the new Dependencies graph that shows all build chains of a particular configuration or a build.
However, with this EAP build you will have much more control over your build chains, for example start dependent parts of the chain using the same revision for dependent builds.
The whole thing is similar to a “pipeline”, at any stage of your release process you can easily prolong pipeline to some further stage.
TeamCity now uses Java based back-end for handling NuGet feeds. This should simplify setup of NuGet in TeamCity and as an additional benefit you can use TeamCity NuGet feed feature if server is installed on Unix.
Both Maven2 and Maven3 are now bundled with TeamCity. You can choose required version of Maven on the Maven runner page.
Additionally you can instruct Maven runner to use unique local artifacts repository for the builds of build configuration.
See the complete release notes, back up your TeamCity instance, try the build and share your feedback with us!
We’re going to try to publish bug-fix builds more often than regular EAP builds, preferably once in two weeks, so stay tuned!
Twitts about TeamCity