Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,144
Community Members
 
Community Events
176
Community Groups

How to track Gitlab deployments in Jira?

Edited

Background

My Jira and Gitlab are integrated. I can see commits and merge requests in Jira. I enabled `Deployments` feature in JIra and can see most of my deployments on the `Deployments` page.

My GitlabCI has the deployment job `deploy_production`. Its `environment` is set to `production`.

Issue

When I run the job, I expect to see the deployment on Jira `deployments` page, but I don't see it there.

This job runs only in the `main` branch. Short living branches can deploy to `development` and they can be seen on the deployments page of Jira. It appears that Jira does not sync main branches properly. 

Is there something I might be doing wrong or is it a bug I should be waiting to be fixed?

 

deploy_production:

image: google/cloud-sdk:alpine

stage: deploy

only:

- main

needs:

- build_app

- build_storybook

environment: production

script:

- echo $SERVICE_ACCOUNT | base64 -d > /tmp/$CI_PIPELINE_ID.json

- gcloud auth activate-service-account --key-file /tmp/$CI_PIPELINE_ID.json

- gcloud --quiet --project $PROJECT_ID app deploy app.yaml

after_script:

- rm /tmp/$CI_PIPELINE_ID.json

when: manual
 

1 answer

I am also having issues with this. 

Jira is tracking commits, branches and merge to dev that contain the issue ID, but when I merge dev to main, it does not track nor recognise the pipeline. 

 

Not sure if I am missing something or this is not working for another reason

 

Thanks

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events