Github integration does not use environment mapping for deployments

Nikolas Höft February 16, 2023

Hello!

I am trying to map Github environment naming patterns to Jira environment types. The environments have a naming pattern like 'deploy_<scope>', e.g. 'deploy_staging' or 'deploy_master'. I would like to make sure that the environment 'deploy_master' it is recognized as a production environment.

I followed the steps outline in the docs (here) and created the file .jira/config.yml with the following contents:

deployments:
environmentMapping:
development:
- "*_dev"
testing:
- "*_test"
staging:
- "*_staging"
production:
- "*_master"

However, the mapping seems to get ignored, e.g. deployments in 'deploy_master' still show up as unmapped in Jira.

Is there anything else I need to do for the mapping to be applied?

2 answers

0 votes
Taras Kuz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 14, 2024

Have the same problem and in job the environment is specified!...

0 votes
Christopher James Curtin February 23, 2023

I had the same issue. It was because in my Github Actions, in the deploy job I did not specify the environment, ex:

`jobs.<job_id>.environment` is required in order for Jira to recognize the env if it's not a standard branch name.

see: https://docs.github.com/en/actions/using-jobs/using-environments-for-jobs




Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events