Hi Atlassian community,
We are using JIRA cloud and AWS CI/CD pipeline services (CodeBuild, CodeDeploy, CodePipeline) for managing our continuous integration and deployment pipeline.
How can we populate the Build and Deployment view of JIRA issues to see build and deployment status on tickets. We've integrated with GitHub to view the Development information on JIRA tickets, but we can't view the builds and deployments for an issue.
Welcome to the Atlassian Community!
To populate the Jira Software Cloud build and deployment view, you need to either implement a full-fledged Atlassian Connect app that provides the build and deployment modules, or an OAuth 2.0 (3LO) app as outlined in Integrating Jira Software Cloud with on-premises tools.
Both approaches require to map the resp. CodeBuild and CodePipeline lifecycle event data to the JSON payloads required by the resp. Jira Software Cloud builds and deployments REST APIs (beware that some required fields are not available and need to be substituted etc.).
PS: We are working on such an OAuth 2.0 (3LO) integration ourselves and are contemplating to publish it as a (low-priced) commercial app in the Marketplace down the road, so feel free to get in touch if you would be interested (and are not in a hurry).
Hi @Simran ,
Sorry for the late reply, I missed the notification (we need to automate tracking our community posts it seems).
We have indeed made notable progress and won an encouraging honorable mention for our Develop with AWS (Jira) submission to Codegeist 2021, which aims to "integrate your AWS development toolchain with the Jira Software Open DevOps experience". We'll initially support CodePipeline, CodeBuild, and likely CodeCommit, but aim to also cover other applicable services like CodeDeploy, CodeArtifact, CloudFormation, Step Functions, AppConfig etc. over time.
As summarized on our new Develop with AWS landing page, the app is still in the works while we are waiting on support for Jira Software Cloud data providers [Open DevOps] (FRGE-472) in Forge, which is more or less blocking a public release in the Atlassian Marketplace (while the OAuth 2.0/3LO integration discussed above is sufficient to explore the concept, it has significant limitations that are likely not suitable for the majority of users).
We hope to learn more about Atlassian's resp. roadmap priorities in January, though depending on their timeline we may need to pivot to one of the two conceivable workarounds (Connect or OAuth 2.0) - if that turns out to be the case, we'd be happy to discuss whether the resulting tradeoffs might be acceptable for your use case.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...