Issues with jiraSendDeploymentInfo

[jrose]

Hello,

I am seeing the following errors when trying to send deployment information to Jira:

[ATLASSIAN CLOUD PLUGIN] [INFO] jiraSendDeploymentInfo(XXX.atlassian.net): 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: XXX.atlassian.net.

The pipelines I am using now generate changelogs where they weren't before, but now I am seeing this issue when running pipelines for tagged releases unconditionally. I read through the documentation and looks like I can specify issue keys as a list of strings. The question is whether this should be a parameter or if the values can be programmatically obtained from either changelog or most the commit?

https://www.jenkins.io/doc/pipeline/steps/atlassian-jira-software-cloud/#jirasenddeploymentinfo-atlassian-jira-software-cloud-jenkins-integration-deployment

[David Taylor · Accepted solution]

I'm getting the same error now.  My commits definitely have the issue key in them, as well as the PR title. Any idea why this is happening?  

 

I would think this should be automatically retrieved. Is there some setting or additional context I need to provide?

For context here is the full warning message as well

[2024-10-31T17:59:51.661Z] [ATLASSIAN CLOUD PLUGIN] [INFO] jiraSendDeploymentInfo(xx.atlassian.net): 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: xx.atlassian.net.

[David Taylor]

@Mark Rekveld - Marvelution it seems issue keys are strictly searched for as uppercase only, while Jira github integrations are case insensitive and even the hyphen is optional.  It would be great if this add-on followed the same flexible approach to issue keys 

[Mark Rekveld - Marvelution]

Hi @David Taylor

True, the IssueKeyStringExtractor implementation of the plugin seems to only look for uppercase keys. I'm not sure why this is the case.

My app on the other hand is case insensitive to be more flexible.

You can always open a PR or issue in the github project of the plugin to address this.

[Mark Rekveld - Marvelution]

Hi @jrose 

Welcome to the community.

You are getting that message because the Jenkins plugin was not able to locate any issue key in the build data, commit message or branch name, see also the Plugin Documentation 

The official plugin only looks for issue keys in the commit messages and branch names of a build. Jenkins Integration for Jira (Disclaimer, I'm the developer of the app) also looks in other places for any valid issue key, see App Documentation 

Cheers,
Mark

[jrose]

I am using a multibranch pipeline that also uses the remote script plugin so it gets the pipeline script from git. Is it possible that it's not getting the information it needs because it's looking at git for the pipeline instead of what it's actually releasing? How would I debug this further?

[Mark Rekveld - Marvelution]

When it comes to the official plugin  don't know, I would have expected Atlassian to step up. You could try to open an issue in the github.com repo 

If you are not able to resolve the issue, and you are not getting help to debug it, then maybe look to another solution.