CodeShip for Jira

Real-time CodeShip build status in Jira.

End of Life Announcement

We are announcing the End of Life for the CodeShip for Jira app.

We will be retiring this app effective 1st May 2023.

During this period, we will be complying with Atlassian’s app retirement guide.

We would like to take the opportunity to thank all our users for the support they have shown for this app.

Getting Started

To begin, add a webhook notification in your CodeShip project.

Step 1: In the CodeShip project settings, head to ‘Notifications’ & add a ‘Webhook’ notification:

Step 1

Step 2: In the ‘Webhook URL’ field, fill in the URL found in the app’s ‘Get Started’ page in your Jira instance. Each URL is unique to each instance.

Step 2

Step 3: Configure the other options as necessary. For example, select all the Build Events. Then, save the notification.

Step 4: Run builds & see build status show up.

Example Usage

Use this app to:

…get quick status of builds:

Example 1

…get details of builds (build numbers come from CodeShip):

Example 2

…get build status of Jira issues in a release:

Example 3

Frequently Asked Question (FAQ)

  1. What’s with the huge build number?

    The build number comes from CodeShip. Unfortunately Jira API only accepts integers in that field so Git commit ID can’t be use for that field.

  2. Why is the build number always 1?

    Sometimes the build number from CodeShip is an universally unique identifier (UUID). As Jira API only accepts integers in that field so we have decided to go with a static number.

  3. Why can’t I see any builds in Jira?

    There are a few reasons for this:

    • The description from CodeShip exceeded 255 characters. While we do our best to truncate it before sending it to Jira API, there are other inputs such as emojis which will go beyond the limited character length.
    • Codeship for Jira is now a paid app. Please update to the latest version available on Atlassian Marketplace to continue usage of the app.
  4. Why does the development panel showing failed builds and not the latest build?

    Unfortunately this is controlled by Atlassian. In their documentation for development panel, a red status lozenge will show “if at least one run failed for any build by any linked build server”.