If you are using Jira and Jenkins, you know that some of your Jira users do not have (or do not want) access to Jenkins. However, the same users ask you to launch deployments or request the status of those deployments.
Hopefully, with our new Apwide Jenkins Shared Library, it has never been so easy to integrate Jira with Jenkins! Most importantly, we have published examples that will only require a copy-paste and a few edits.
As a result, no more time wasted answering to Jira users who cannot connect to Jenkins.
Soon you will note improvements in several areas:
- People will know the Environments’ statuses (Up, Down, Slow…) For that, Jenkins is used to monitor your Test Environments and update the statuses automatically.
- People will know the application versions deployed on each Environment. For that, Jenkins jobs update your Environments’ deployed versions in Jira automatically.
- People will trigger deployments and new Environment provisining themselves, thanks to an Environment Self-Service built inside Jira.