Get our free guides to start using Jira and Confluence Cloud like a pro.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

This feature is available for JIRA Jira Server only.

Starting from version 2.2.0, you can run builds in TeamCity right from JIRAJira.This can be achieved with the custom field that is added into the necessary screens of JIRAJira. This custom field also stores the history of builds that were run from it.

Info

Your administrator should configure the TeamCity Build Runner custom field for the specific JIRA Jira project.

As an alternative, you can use the Run a Build post function that can remotely trigger builds in TeamCity from JIRAJira.

Running Builds

  1. Open the JIRA Jira issue.
  2. Locate the Trigger build link and click it.
  3. In the Trigger build form, define parameters for running a new build, as follows:
    1. Branch - select the branch which a new build is triggered in.
    2. Properties - click the Pencil icon and enter additional properties for running a new build. This field may be hidden if the administrator does not allow its editing by users.
    3. Build comment - enter the comment that will be appended to the build. This field may be hidden if the administrator does not allow its editing by users.
  4. To run the build in TeamCity, click Confirm.
  5. Once you have run the build, the notification will be displayed in the form.
  6. In case of any unexpected error, the corresponding notification will be displayed in the form too.

...

  1. You can view the build history while viewing the JIRA Jira issue or when triggering a build.
  2. Open the JIRA Jira issue.
  3. Click the View history link. Alternatively, you can open the Trigger build form and click View history link.
  4. In the opened Builds history form, you can view the following information about the build:
    • Branch - TeamCity branch which the build relates to.
    • Build Number - build number within the project.
    • Start Date - time and date when the build was run.
    • Changes - description of changes specified by the developer.
    • Duration - duration of the build procedure.
    • Tests - number of passed tests.
  5. Click Close when complete.