Jira integration with CI/CD

 

Jira Code

Click Code in the project menu. This screen links you to every repository that is connected with your project. You can navigate directly to a specific repository by clicking on the repository icon.

Bitbucket

Screenshot of Bitbucket Jira code

GitHub

Screenshot of Github

GitLab

Screenshot of gitlab

Jira Deployments

Click Deployments in the project menu. The Deployment page shows aggregated activity across the project. Insights provide metrics such as Deployment frequency and Cycle time. This data is automatically generated when developers label commits with Jira issue tags.

Screenshot of Jira deployments

Jira Project pages

Click Project pages in the project menu. Project pages aggregates all Confluence pages connected to this project, and provides some helpful templates to create new pages.

Screenshot of project pages

Jira updates from CI/CD

Note, the details of this section are subject to change depending on which source control, and CI/CD tools are integrated with Jira. The screenshots below are based on a Bitbucket integration. Similar functionality exists for GitHub, and GitLab, but the details may vary.

Go to Jira, and click on the Jira issue for adding the s3_infra repository.

Screenshot of updates from CICD

Look in the Development section to see an overview of what work was done. You can click on the development section to bring up the development screen.

Screenshot of update summaries

Commits

You can see all commits linked to this issue in the Commits tab. This linking is accomplished when the Jira issue ID is added to the commit message, as shown in the Message column.

Screenshot commits tab

Pull requests

You can see all pull requests linked to this issue in the Pull requests tab.

screenshots of pull requests

Deployments

You can see all deployments linked to this issue across all Environments in the Deployments tab.

screenshots of deployments

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more