Hi there, I have the following in my pipeline to send production deployment info from Jenkins to Jira:
jiraSendDeploymentInfo environmentId: 'prod', environmentName: 'prod', environmentType: 'production'
However, it gives the following error:
[ATLASSIAN CLOUD PLUGIN] [INFO] jiraSendDeploymentInfo(mydomain.jira.com): SKIPPED_ISSUE_KEYS_NOT_FOUND_AND_SERVICE_IDS_ARE_EMPTY: No issue keys found in the change log and service ids were not provided. Not sending deployment information to Jira: mydomain.jira.com.
This is despite the issue key - "ISSU-1234" being present in the commit message:
Merge pull request #68 from mydomain/ISSU-1234-issue-key
I don't have this problem when sending dev deployment info from Jenkins to Jira using:
jiraSendDeploymentInfo environmentId: 'dev', environmentName: 'dev', environmentType: 'development'
In this successful case the commit message was "ISSU-1234: Details of my change".
Both dev and prod deployments take place from the main branch so I am relying on the commit messages containing the issue key.
I wondered if it could not detect the issue key in my commit message for my production deployment but I checked out the source code at https://github.com/jenkinsci/atlassian-jira-software-cloud-plugin and ran the commit message against the unit tests in there and it was able to successfully obtain the issue key.
Would greatly appreciate any assistance you can offer. Thanks
