Inspiration

With the companies we have worked for, we have seen a multitude of projects. The projects run on more than one application. Jira is commonly used for issue tracking and project management. In addition, they have Jenkins server or URL for the CI-CD pipeline. We already have a webhook feature to trigger a Jenkins job via GIT. But that holds a dependency on the Jira administrator to add a webhook for every transition. Since Jira is used by the development team to work on their user stories, we want to integrate the Jira with Jenkins. This thought inspired our solution to trigger the jenkins script when the user changes the status of a story on Jira. Let's assume that the developer wants to perform unit tests, and moves the story to "In Dev", the jenkins instance is triggered and runs the unit tests. The same concept applies to the integration tests and the functional tests.

What it does

We build a front end web app using Forge which helps the user to store the url, user name, api key or password, jenkins server details Another app called the workflow app is built using Forge that triggers the scripts based on the status of the story on Jira We build a front end web app using Forge which helps the user to store the url, user name, api key or password, jenkins server details Another app called the workflow app is built using Forge that triggers the scripts based on the status of the story on Jira

Once the jenkins triggers the script, the outcome of execution is returned to Jira If the tests don't meet the criteria, the status of the story steps backward to fix the issues. If the tests meet the criteria, the status of the story steps forward to perform the next set of actions.

How we built it

We have used the ForgeApp We have used the Forge UI Kit to store the value in the custom field and the Forge workflow validator to trigger the jenkins job

Challenges we ran into

We've faced a few challenges, the major one is that we had to ensure jenkins server is on the https protocol since the forge manifest back end supports the https protocol alone

Accomplishments that we're proud of

The idea of integrating Jira with Jenkins Learning new technology and applications Able to think out of the box to come up with a solution

What we learned

We are capable of converting the ideas into working models. Integrating Jira and Jenkins without using the webhook.

What's next for Integris

Trigger Jenkins jobs with parameters Integrate the reporting and Build return back status. Creating the Dashboard for the live monitoring Via Jira.

Built With

Share this project:

Updates