UrbanCode Deploy & JIRA Integration Part One

Today I’m going to show you how to integrate UrbanCode Deploy with the well-known Atlassian Issue Tracking System Jira.

First of all we need the UrbanCode Deploy JIRA plugin .

Once downloaded and installed we will find a new menu item:  Issue tracking ->Jira Plugin into our step palette:

We will use, in particular, the Transition Issue step to put “IN PROGRESS” an open task and then, at the end of our Application Process flow, put the task in “DONE” status.

So let’s create a component process, called: “Start Jira Task”  and insert the Jira Transition Issue step:

At least we need “Issue ID”, “Transition Name”, “JIRA Base URL”, “JIRA Username” and “JIRA Password”.

For “JIRA Base URL” and “JIRA Username” we can use  System Properties sharing their values all over the environments.

The “Transition Name” it depends of your Jira Workflow. A JIRA Workflow is a set of statuses and transitions that an issue moves through during its lifecycle.

Here the workflow we are going to use:

The “Transition Name ”  will be  “Start Progress”

The “Issue ID ” will be a variable representing the ID of our Jira task.

At this point create another component Process, called:  “Close Jira Task” and insert another  Jira Transition Issue step.

In this case change only the Step Name and the “Transition Name” like in figure:

Then create your Application Process adding two Jira Component Processes previously created.

The example below shows a typical deployment flow with Stop Server/install Application/Start Server steps.

Put Start Task Jira at the beginning of the flow while Close Task will go at  the end.

Now the most important thing:

How do I pass the Issue ID to the flow process?

Issue ID it’s not a component property,  it’s not an application property, neither an environment property.

[to be continued]

Operations Engineer working with Cloud Infrastructure, Containers, Kubernetes, CI/CD pipelines, CDRA processes, GitOps.