#Teamcity jira integration how to#
#Teamcity jira integration software#

Once you create a VCS root you can reuse it across build configurations. The button is located down the bottom of the page: Before you save, make sure to ‘Test connection’ so that TeamCity can find your repository with the settings you have provided. I leave the rest of the settings to their default values. We want to also monitor pull request branches so we set the ‘Branch specification’ to +refs/pull/*/merge which uses wildcard to monitor pull request merged branches.

If you’re wondering where that comes from run git show-ref master command on your git repo. So we set it to refs/heads/master which is the git master branch. ‘Default branch’ should be set to your master branch which is where your CI should focus more.If you’re using GitHub you can grab this from your project’s GitHub home page (the SSH one requires authentication so you might grab the https URL): Fetch URL: this tells TeamCity where it should look for the source code.VCS root name and ID: use a unique name preferably related to your project so it’s easy to spot it amongst other VCS roots you might have in your TeamCity.Once you choose Git you are provided with a page to setup your git repository connection:

#Teamcity jira integration how to#

Once your build config is created you should set the ‘VCS settings’ so TeamCity knows how to get the code needed for the build.ĭifferent VCS engines have different settings so the first step is to pick the VCS you want to use - in our case Git (for GitHub): This is basically the value that gets injected into %unter%.

‘Build counter’ starts from 1 and increases on each build.

This is one setting that you will be changing rather often: in my case any time I want to release a new version with a different major or minor. I use 1.0.%unter% because the project I am setting up, Humanizer, is currently on version 1 and I want the future builds to continue from there. You can hardcode this value or could use the TeamCity provided value %unter% as part of your build number.

‘Build number format’ is the build number.

‘Description’ is optional but having a description there makes it easier for the person maintaining the project.

‘Build configuration ID’ is a unique identifier for this build configuration.

CI’ so the next person knows that this is a CI build configuration and also that it’s the first build config. You can do so by clicking on the ‘Create build configuration’ button on the project home page:Īfter clicking on the button you will be taken to the ‘Create build configuration’ page: The first step is to create a build configuration for Continuous Integration. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.

#Teamcity jira integration software#

So you now have a TeamCity project and want to setup Continuous Integration for your project:Ĭontinuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. There is also a ‘Create Project’ button (if you are System Administrator) to create new projects:Īfter clicking on the ‘Create Project’ button you see the following page where you can enter your project details:Īfter you create the project, you are taken to the project home page where you can setup the build configurations: That takes you to a page showing a list of projects. On the TeamCity admin console go to Administration (and click on the Projects from the left navigation bar). So before anything else we need to create a TeamCity project which is a simple grouping of build configurations.

Setting up build agents, users and roles.įor this post, I assume that you have a running TeamCity server and a user with System administrator rights and you’re logged into the admin console.

Setting up build notification for GitHub pull requests.

That said many of the topics in this post are more or less applicable to other technologies. Net which is where Humanizer is deployed to.

XUnit: the testing framework I am using in Humanizer.

Git and GitHub: Humanizer repository is git and the project is hosted on GitHub.

Net: the programming language used for Humanizer. This is the technology stack I am using in the project, Humanizer, for which I am setting up the TeamCity project: This is an end to end tutorial for setting up Continuous Integration (AKA CI) and Continuous Delivery (AKA CD) for a GitHub project using TeamCity.