How to integrate your workflows with Jira using codemagic.yaml
Jira is an issue tracking and project management product developed by Atlassian. Many software development teams use it to maintain the visibility of their projects.
It offers a REST API that can be used in conjunction with your Codemagic workflows to add comments, upload attachments, or transition the status of an issue, story, or epic.
The following example shows how to set up integration with Jira using the codemagic.yaml configuration with a native iOS project but the approach is the same for Flutter, React Native, and native Android projects.
Clone the Jira integration starter project from the Codemagic GitHub page.
You will need access to a Jira account and can sign up for free.
Create a Jira API Token once you have access to Jira.
Add the codemagic.yaml to your project
Copy the codemagic.yaml from the starter project into the root of your repository. Then, update the environment variables as indicated and use the documentation links, where required, for the values related to building your app, code signing, and app publishing.
Update the Jira environment variables
There are four environment variables that need to be updated for the Jira integration:
Updating the JIRA_AUTH environment variable
JIRA_AUTH environment variable is a base64 encoded string which consists of the email address you log into Jira with and the Jira API token you created:
You can encode these credentials in the macOS Terminal using:
echo -n 'firstname.lastname@example.org:<api_token>' | openssl base64
Alternatively, use an online tool to base64 encode this string.
This value is used in the Authorization header used in cURL requests to the Jira API.
Adding the JIRA_BASE_URL environment variable
This is the subdomain you chose when you set up your Jira account e.g. “YOUR_SUBDOMAIN.atlassian.net”. Put the subdomain including “atalassian.net” in the
JIRA_BASE_URL environment variable.
Specifying the JIRA_ISSUE environment variable
Issues, epics, and stories have a unique id, usually in the format ‘XXXX-N’, and is visible on your issues either in the bottom right or top left when looking at an issue. Put this value in the
JIRA_ISSUE environment variable.
Finding and updating the JIRA_TRANSITION_ID environment variable
If you want to transition your issue to another status, you will need to know what transition ids are available. You can obtain the available transition ids using a cURL request as documented in the Jira API documentation. Once you know the transition id then put this value in the
JIRA_TRANSITION_ID environment variable.
Adding formatted comments to a Jira issue
Copy the .templates folder to the root of your project. This folder contains a template file called jira.json, which adds formatted comments to a Jira issue.
The Atlassian Document Format (ADF) is used to format the comment layout and style. Click here for more information about ADF and how to modify this template.
Note that it contains strings beginning with
$, which the scripts use to replace values in the JSON using
sed before it is added as JSON payload to the
Understanding the ‘Post to Jira’ script
The script section for publishing to Jira contains several actions which set environment variables, update the comment template, and then use cURL requests to add a comment and upload files to a specific Jira issue.
Using jq to parse $FCI_ARTIFACT_LINKS
First, it uses jq (a command-line tool for parsing JSON) to parse the contents of the Codemagic environment variable
$FCI_ARTIFACT_LINKS to find information such as the articact URL, filename, bundle id, and version name and store the values in environment variables.
See this link about the JSON data that $FCI_ARTIFACT_LINKS contains.
Setting additional environment variables
Additional environment variables are then set, such as the build number, build date, and commit number. These environment variables are used to replace values in the jira.json comment template using sed, a stream editor for parsing and transforming text.
Making cURL requests to the Jira API
- The script performs a request to add a comment to the Jira issue specified using the jira.json as the payload.
- Another request is used to transition the issue to a different status.
- The script checks to see if XML test results have been generated. See here for information about using
test_reportto generate a test report .xml output. If xml test results are available, then they will be uploaded to the Jira issue.
- If release notes have been created, then these are uploaded to the Jira issue.