Dear TeamCity users,
We invite you to share your feedback with us!
Stay tuned for the news on the Teamcity 9.0 RC and happy building!
Dear TeamCity users,
We invite you to share your feedback with us!
Stay tuned for the news on the Teamcity 9.0 RC and happy building!
If you want a jump start improving software development with automation, consider this workshop with Wes Higbee in New York, NY. This two day workshop will provide hands on examples and the opportunity to apply the techniques to your own software projects.
There are many more details on the workshop Eventbrite page including details about what’s in it for you, the agenda, links to videos and sample materials.
Sign up before November 25th and get 10% off individual tickets and team passes. If you own TeamCity you are eligible for a separate discount on individual tickets and team passes. Please contact Wes from the Eventbrite page.
To learn more and register for this workshop visit the official page, Improving Software Development through Automation with TeamCity.
Continuous Integration is all about quick feedback on changes in our code. TeamCity lets us subscribe to important events that may take place during the build process, such as succesful builds, build failures and so on. Email, Jabber, IDE and Windows Tray notifications are supported out of the box, but we can also post these notifications to Visual Studio Online Team Rooms using a newly released plugin.
With Visual Studio Online Team Rooms, we can keep a record of things that happen in our team – checkins, work item updates, code reviews and so on. Team members can have conversations with each other directly in the team room. TeamCity can contribute to the conversation, by posting notifications around builds to the team room. Let’s see how we can configure this integration.
After installing the plugin, we have to enable the integration from the Administration | Server Administration | VS Online Notifier page. Once done, we can configure notifications from within a user profile. In the top right corner of the screen, we can click the arrow next to our username and select My Settings & Tools from the drop-down. We can then setup notifications under the VS Online Notifier tab.
Team Room notifications will be sent by the user profile we configure here. We’ll have to provide the Visual Studio Online account name, the full Team Room name and a username and password to connect to it. Do make sure to enable alternate credentials in Visual Studio Online to be able to send notifications on behalf of this user.
Once the connection has been tested and saved, we can tell TeamCity which notifications we want to see for one or more build configurations. Check the documentation for a list of the available notification options and how to work with them.
After saving the rule, TeamCity will send notifications to the configured Visual Studio Online Team Room as events happen.
Every TeamCity user can configure these notifications. In the above screenshot, we’ve created a special “TeamCity user” in Visual Studio Online. It’s perfectly possible to send notifications from other users, too. When multiple users have configured the same events, TeamCity will merge these messages in one so the Team Room is not flooded with the same information.
We can add more information to the notifications if needed, by customizing notification templates. For example, we can add the error messages from the build log or add additional build details in the notification.
Continuous Integration only makes sense if there’s an easy way to verify the quality of our codebase and when we can easily correlate builds with our issue tracker and the source code itself. Out of he box, TeamCity provides integration with YouTrack, JIRA and Bugzilla. We can also install plugins to integrate with other issue trackers like GitHub and FogBugz. Today, we’re happy to announce another issue tracker integration: the Visual Studio Online Work Items plugin.
We’ve already blogged about how we can link Visual Studio Online source control with TeamCity and run our builds.When using Visual Studio Online (VSO) as an issue tracking system as well, we can use the Work Items plugin to provide a direct link between the build and version control history in TeamCity and the Work Items that were associated with them.
After installing and configuring the Visual Studio Online Work Item plugin, TeamCity will parse version control check-in messages and transforms the Work Item ID into a link that brings us to the full work item. A direct link will be available on the Changes tab of our build results. The Issues tab will show us a list of all Work Items that are associated with the build. And in the build configuration home page, we can also review Work Items mapped to comments from the Issue Log tab.
The plugin does not look at the Work Item Association, but instead uses the check-in message to provide these links. This has a big advantage: it works with both Team Foundation Version Control (TFVC)-based projects as well as the increasingly popular Git-based projects. This does mean we have to keep two things in mind:
To enable integration, we need to first install the Visual Studio Work Items plugin. Next, we have to create a connection to our Visual Studio Online project from the Administration | Issue Tracker page. After selecting the Visual Studio Online connection type, we have to provide a display name, our Visual Studio Account name, and a username and password to connect to it. Do make sure to enable alternate credentials in Visual Studio Online!
We also have to provide the collection, the project name and the issue pattern to detect. The default is
#(\d+), which will recognize Work Item IDs that look like #10, #99 and so on. We can customize this so we can detect other patterns. The Test Connection button lets us verify all connection details are correct.
Once saved, TeamCity starts to match each Work Item ID it recognizes in the project’s check-in history.
Hello, our dear readers! Have we got the most exciting news for you! Although it feels like we just announced opening the TeamCity 9.0. EAP, it’s almost time for the release and we are presenting TeamCity 9.0 EAP3 build 31886 today!
We promised you the ability to move projects among servers as one of the great new features of TeamCity 9.0, and in this EAP you get the feel of what it’s eventually going to be. We were contemplating on different implementation approaches, and initially considered to add the ability to export projects from a TeamCity server, but then we realized that we already have what we need in a regular backup file, so we switched to project import! Now all you need to do is create a backup file on the source server and then select projects you want to import on the target server. Read more in our Release notes.
Another useful feature of this release is favorite builds – you can now star your favorite builds and they will be listed on a dedicated page. Optionally, you can also configure notifications for your favorites.
The TeamCity web UI is getting more and more user-friendly: now you can create and modify custom charts right from the UI.
Those of you who use meta-runners will love the new option to create a build configuration from a Meta-Runner, which makes it easier to fix problems in the Meta-Runner and verify the fixes.
Among other features is the ability to compress artifacts to a 7-zip archive, new options for Perforce VCS roots, the ability to push parameters to dependent builds when using snapshot dependencies, etc.; these and about 150 fixed issues are listed in our Release notes.
A large number of TeamCity users are working with Microsoft technologies and platforms such as Visual Studio Online and Azure, both fantastic tools in their respective areas. We are really excited to announce several new integration points between TeamCity and these tools!
Today we are launching a special offer in partnership with Microsoft. All MSDN subscribers are eligible for a 50% discount on new TeamCity Enterprise licenses. Visit the MSDN special offers page to see the details and apply for the discount.
This is the first time TeamCity offers such a bargain for its commercial licenses. If you were planning on upgrading to Enterprise, this is definitely the right time to do it!
Visual Studio Online provides excellent source control, with support for Team Foundation Version Control and Git. TeamCity supports building projects that are hosted on Visual Studio Online and provides a powerful and comprehensive continuous integration story because of its advanced features to automatically run builds for feature branches, automatic merge and many others. Read more in the dedicated blog post on TeamCity and VSO source control.
Continuous integration becomes more powerful when we have full traceability from source control to builds to issue tracking and vice-versa. The Visual Studio Online Work Items plugin gives us a direct link between the build and version control history in TeamCity and the Work Items that were associated with them.
Quick feedback on changes and communication are the corner stones of agile teams. Visual Studio Online users can collaborate in a Team Room and discuss what is going on in the project. With the Visual Studio Online Team Rooms plugin for TeamCity, the build server becomes a member of our team by posting notifications around builds to the team room.
Very often it is difficult to predict the load on build agents, for example during releases. One minute we need only one or two build agents, the next minute we have 50 builds queued up. Using the elastic nature of cloud platforms like Microsoft Azure, we can scale out our build farm when needed. The TeamCity Azure plugin provisions and deprovisions virtual machines when needed, perfectly aligning capacity demand of our build farm with its running cost.
If you’re using or planning to use Visual Studio Online together with TeamCity, give these plugins a try! They provide great interoperability between both products, providing a best-of-breed solution for development teams. Keep an eye on this blog, as we’ll be writing more about these integrations in the coming days.
And remember: all MSDN subscribers are eligible for a 50% discount on new TeamCity Enterprise licenses. Visit the MSDN special offers page to see the details and apply for the discount.
In a large TeamCity setup with many projects, it’s often very difficult to predict the load on build agents, for example during releases. One minute we need only one agent to be running, the next minute we need 50. Not to worry! TeamCity supports scaling out builds to Amazon EC2, and starting today, also Microsoft Azure!
For each queued build, TeamCity first tries to start it on one of the regular, non-cloud agents. If there are no regular agents available, TeamCity finds a virtual machine or virtual machine image with a compatible agent and starts it on Azure. TeamCity ensures that the configured maximum number of instances is never exceeded. Let’s have a look at how we can get started with a Windows or Linux build agent farm on Microsoft’s cloud platform.
First things first, of course. The TeamCity Azure plugin is not bundled and therefore has to be installed on our TeamCity server. It is compatible with TeamCity 8.1 and the EAP of TeamCity 9. Shutdown the TeamCity server, download the latest version of the plugin from our build server and copy the downloaded zip archive to the <TeamCity Data Directory>/plugins directory. Next, start the TeamCity server again and verify the plugin was loaded correctly from the Administration | Plugins List page.
Once that’s done, we can get started with creating a virtual machine or virtual machine image for our build farm.
We’ll need to create a virtual machine (image) on which our builds will run. In short, we need to create a Windows or Linux virtual machine:
If we want TeamCity to create virtual machines for us, we will also have to create a generalized image of he virtual machine we’ve just created. Check the full documentation for a detailed list of steps involved in creating a build agent virtual machine (image).
Once we have the plugin installed and have a virtual machine (image) our builds can run on, we can configure the TeamCity Azure plugin. From the TeamCity | Administration | Server Administration | Agent Cloud page, we can create a cloud profile with the “Azure” type.
We will need at least a name for our cloud profile. The Terminate Instance Idle Time is an important one to configure: it tells TeamCity how long an instance can be idle before it will be stopped. As Microsoft calculates costs based on the number of minutes a machine runs, it is recommended to adjust this setting according to our usual build length. This reduces the amount of time a virtual machine is running and thus, reduces the cost.
TeamCity will need two more things to be able to provision virtual machines on Azure: a management certificate and the ID of the subscription in which to deploy build agents. After downloading the publish settings, find these values in the downloaded XML files and paste them in the plugin configuration.
Clicking Add Image lets us specify the virtual machine (image) we want TeamCity to run. The TeamCity Azure plugin supports two modes of operation:
Let’s go with an image-based approach and provision up to 10 agents based on the TC-Agent image I’ve created. We have to specify the service in which we want to provision virtual machines. The service must be either empty or contain only a virtual machine deployment. It is recommended to create a new, empty service for this.
After adding the image and saving the cloud profile, TeamCity does a test start for them to learn about the agents configured on them. Once agents are connected, TeamCity stores their parameters to be able to correctly process build configurations-to-agents compatibility.
From now on, TeamCity will first try to start builds on regular build agents. If none are available, it will start compatible agents in Azure. We can see the running images from the Agents | Cloud page and optionally start/stop them as needed.
Head over to the documentation for the TeamCity Azure plugin and give it a try.
Happy building in the cloud!
We’d like to thank each and every of the 891 participants of our CI Tools Survey. It’s great to know that we’ve got such an active and responsive community! You really gave us food for thought and we do hope that it will help us make TeamCity your favorite tool ever!
Today we are happy to announce the three lucky winners of $300 Amazon.com certificates who were chosen randomly. So put your hands together for a round of applause for:
We’ll send a personal email to each of the winners with details on obtaining the prize. In case your name is in the list, but you do not get information from us today, please give us a shout in the comments on this post.
Congratulations from all of JetBrains, and especially from the TeamCity development team!
And in case you missed the new TeamCity 9.0 EAP build – here is the download link – give it a try and let us know what you think!
Have a great weekend and happy building!
The fall has clearly arrived at our neck of the woods with yellow and scarlet foliage, rains, first frosts and a rich apple harvest. And while almost everyone seems to be busy baking apple pies, our developers are tirelessly cooking the new TeamCity version, carefully weighing out and mixing all the best ingredients which nicely turned into this TeamCity 9.0 EAP2 build.
Regardless of the season and the temperature outside, you do want your server to be available 24/7 and this is exactly what we have been able to achieve by moving the build history clean-up to the background.
Besides, the work on synchronizing the project settings with version controls continues, and now you can store your settings in a Mercurial repository.
Our developers make an effort to improve TeamCity integration with different version controls:
largefilesextension which in our case used to slow down the
hg pullcommand significantly in repositories. After removing the
largefilesextension, collecting changes time reduced to a few seconds compared to 10 minutes before.
This is by far not all – see our Release Notes for the complete list of the features and fixes in this new EAP version.
The recording of our October 2nd webinar with Alex Yates of Red Gate, 7 Steps to Build a Database Deployment Pipeline with Red Gate and TeamCity, is now available on JetBrains YouTube Channel.
In this practical demo, Alex Yates, Pre-Sales Engineer at Red Gate, demonstrates how to set up continuous delivery for your SQL databases using TeamCity, Red Gate’s SQL Automation Pack, and Octopus Deploy.