Semaphore for Jira

Real-time Semaphore build status in Jira.

Getting Started

To begin using the app, add a webhook secret and webhook notification in your Semaphore organisation.

Step 1: In the Semaphore organisation settings, head to ‘Secrets’ and create a new secret. You may use an existing secret if you already have one:

Step 1

Step 2: Add a new environment variable named ‘WEBHOOK_SECRET’ and for the ‘Value’, fill in the webhook secret from the app admin page.

Step 2

Step 3: In the Semaphore organisation settings, head to ‘Notifications’ & add a notification: Step 3

Step 4: In the ‘Endpoint’ field under the webhook section, fill in the webhoook url from the app admin page. For ‘Secret Name’, please fill in the name of the secret created previously. Step 3

Step 5: Fill in all the required fields such as notification name and rule name. To enable notification for all projects, use the /.*/ regular expression. Configure the other options as necessary. Then, save the notification.

Step 6: Run builds & see build status show up. It does take a while for Semaphore to send webhooks with the signature header indicating the webhook secret.

Example Usage

Use this app to:

…get quick status of builds:

Example 1

…get details of builds (build numbers are always 1 because Semaphore does not send build numbers):

Example 2

…get build status of Jira issues in a release:

Example 3

Frequently Asked Question (FAQ)

  1. Why is the build number always 1?

    Semaphore does not send build numbers for builds. As Jira API only accepts integers in that required field, we have decided to go with a static number.

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

    There are a few reasons for this:

    • The description from Semaphore 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.
  3. 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”.