You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Jenkins is the leading open-source automation server used by startups and enterprise teams to build, test and deploy code to production. We are excited to announce an official integration between Jenkins and Jira Software Cloud. The integration is open-sourced and adds to the growing list of CI/CD integrations, Jira Software now integrates with the top seven CI/CD tools on the market!
We also built a brand new way to connect your self-hosted development tools with the cloud version of Jira Software which means you have more ways to connect your favorite tools, regardless of if they are running behind your firewall or in a public cloud.
Use Jenkins build information in Jira Software to create a workflow between QA and developers and create a rapid feedback loop for testing at any point in your development process.
Similar to our other integrations with CI/CD tools, this integration allows teams to automatically send build and deployment information from Jenkins and display it across Jira issues, boards and query it via JQL. Teams using the integration will have up-to-date information about their Jenkins builds and any deployments on Jira issues with deep links to quickly investigate failed builds or deployments in Jenkins. Read more about this functionality in our launch blog.
OAuth Credentials - This Client ID and Secret is used by the Jenkins plugin to securely send information via the Jira API.
In addition to the Jenkins integration we also build a brand new way to integrate your behind-the-firewall apps with Jira Software Cloud. You can now generate OAuth Credentials (2LO) to securely connect these tools without having to open any holes in your firewall. The credential is tied to a specific Jira site, can be generated by Jira admins, and is used to communicate between a self-hosted application (e.g. a Jenkins server) and your Jira Software Cloud site.
The OAuth credential is currently scoped to only send build and deployment information via the Jira APIs. We are excited about the potential to expand the scope of the OAuth credential to enable more behind-the-firewall apps to connect with our cloud products. Stay tuned for more!
We hope these improvements will give your team deeper insights into their development pipeline and save time spent on manual updates or context switching across tools.
Interested in contributing or forking this plug-in? Head over to our project on the Jenkins GitHub repo to get started.
Head of Product, Compass
5 accepted answers