-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Install plugin version: 2.0.3
Jenkins version: 2.303.1
The Jenkins console output shows that the commit message has the Jira issue key:
{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 Commit message: "Merged in hotfix/TB-5521 (pull request #1398)" }}
{{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}}
but later no deployment info is sent:
[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.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: foo.atlassian.net.
The PR had a branch name of `hotfix/TB-5521` but the PR name, single commit's message and PR body do not contain the Jira issue key. The Jenkins job is building a branch named `aws-qa` which this PR has been merged into.{}
If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit.
Changes
Summary
- -Cascade save and delete from AppDomain to Config
| Commit a2c74e3e9efc5de10cc2c3138f4f8be1e100e303 by author- Cascade save and delete from AppDomain to Config |
[JENKINS-73472] jiraSendDeploymentInfo reports no issue keys found even though build console output reference the merge commit with issue key in message
Kira
created issue -
Kira
made changes -
| Attachment | New: Screenshot 2024-07-17 at 1.17.43 PM.png [ 62992 ] |
Kira
made changes -
| Description |
Original:
The Jenkins console output shows that the commit message has the Jira issue key:
{quote}{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 *Commit message: "Merged in hotfix/TB-5521 (pull request #1398)"* }} {{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}} {quote} {{but later no deployment info is sent:}} {quote}{{[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.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: foo.atlassian.net.}} {quote} {{{}The PR had a branch name of `{}}}{{{}*hotfix/TB-5521`* but the PR name, commit message and body do not contain the Jira issue key. It was my understanding that the branch name would be sufficient from documentation [here|https://plugins.jenkins.io/atlassian-jira-software-cloud/] though: {}}} {quote}{{> it will look for Jira issue keys in the commit messages and branch names of code being built}} {quote} {{If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit but I think that is normal.}} h1. Changes h2. Summary # -Cascade save and delete from AppDomain to Config |Commit a2c74e3e9efc5de10cc2c3138f4f8be1e100e303 by author- Cascade save and delete from AppDomain to Config| |
New:
The Jenkins console output shows that the commit message has the Jira issue key:
{quote}{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 *Commit message: "Merged in hotfix/TB-5521 (pull request #1398)"* }} {\{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}} {quote} {{but later no deployment info is sent:}} {quote}{{[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.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: foo.atlassian.net.}} {quote} {{{}The PR had a branch name of `{}}}{{{}*hotfix/TB-5521`* but the PR name, single commit's message and PR body do not contain the Jira issue key. It was my understanding that the branch name would be sufficient from documentation [here|https://plugins.jenkins.io/atlassian-jira-software-cloud/] though: {}}} {quote}{{> it will look for Jira issue keys in the commit messages and branch names of code being built}} {quote} {{If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit but I think that is normal.}} h1. Changes h2. Summary # -Cascade save and delete from AppDomain to Config |Commit a2c74e3e9efc5de10cc2c3138f4f8be1e100e303 by author- Cascade save and delete from AppDomain to Config| |
Kira
made changes -
| Summary | Original: jiraSendDeploymentInfo reports no issue keys found even though build changelogs reference github commit with issue key in message | New: jiraSendDeploymentInfo reports no issue keys found even though build console reference github commit with issue key in message |
Kira
made changes -
| Summary | Original: jiraSendDeploymentInfo reports no issue keys found even though build console reference github commit with issue key in message | New: jiraSendDeploymentInfo reports no issue keys found even though build console output reference the merge commit with issue key in message |
Kira
made changes -
| Description |
Original:
The Jenkins console output shows that the commit message has the Jira issue key:
{quote}{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 *Commit message: "Merged in hotfix/TB-5521 (pull request #1398)"* }} {\{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}} {quote} {{but later no deployment info is sent:}} {quote}{{[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.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: foo.atlassian.net.}} {quote} {{{}The PR had a branch name of `{}}}{{{}*hotfix/TB-5521`* but the PR name, single commit's message and PR body do not contain the Jira issue key. It was my understanding that the branch name would be sufficient from documentation [here|https://plugins.jenkins.io/atlassian-jira-software-cloud/] though: {}}} {quote}{{> it will look for Jira issue keys in the commit messages and branch names of code being built}} {quote} {{If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit but I think that is normal.}} h1. Changes h2. Summary # -Cascade save and delete from AppDomain to Config |Commit a2c74e3e9efc5de10cc2c3138f4f8be1e100e303 by author- Cascade save and delete from AppDomain to Config| |
New:
The Jenkins console output shows that the commit message has the Jira issue key:
{quote}{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 *Commit message: "Merged in hotfix/TB-5521 (pull request #1398)"* }} {\{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}} {quote} {{but later no deployment info is sent:}} {quote}{{[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.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: foo.atlassian.net.}} {quote} {{{}The PR had a branch name of `{}}}{{{}*hotfix/TB-5521`* but the PR name, single commit's message and PR body do not contain the Jira issue key. The Jenkins job is building a branch named `aws-qa` which this PR has been merged into.{}}}{{{}{}}} {{If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit but I think that is normal.}} h1. Changes h2. Summary # -Cascade save and delete from AppDomain to Config |Commit a2c74e3e9efc5de10cc2c3138f4f8be1e100e303 by author- Cascade save and delete from AppDomain to Config| |
Kira
made changes -
| Description |
Original:
The Jenkins console output shows that the commit message has the Jira issue key:
{quote}{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 *Commit message: "Merged in hotfix/TB-5521 (pull request #1398)"* }} {\{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}} {quote} {{but later no deployment info is sent:}} {quote}{{[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.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: foo.atlassian.net.}} {quote} {{{}The PR had a branch name of `{}}}{{{}*hotfix/TB-5521`* but the PR name, single commit's message and PR body do not contain the Jira issue key. The Jenkins job is building a branch named `aws-qa` which this PR has been merged into.{}}}{{{}{}}} {{If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit but I think that is normal.}} h1. Changes h2. Summary # -Cascade save and delete from AppDomain to Config |Commit a2c74e3e9efc5de10cc2c3138f4f8be1e100e303 by author- Cascade save and delete from AppDomain to Config| |
New:
The Jenkins console output shows that the commit message has the Jira issue key:
{quote}{{ > git checkout -f 6db08a0ec4b8fc9395b696cba7419bc6cf4ce5cf # timeout=10 *Commit message: "Merged in hotfix/TB-5521 (pull request #1398)"* }} {\{ > git rev-list --no-walk 3b1a9984adfb06956a8626b5d3c2b54a639e9dc7 # timeout=10}} {quote} {{but later no deployment info is sent:}} {quote}{{[Pipeline] jiraSendDeploymentInfo jiraSendDeploymentInfo(foo.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: foo.atlassian.net.}} {quote} {{{}The PR had a branch name of `{}}}{{{}*hotfix/TB-5521`* but the PR name, single commit's message and PR body do not contain the Jira issue key. The Jenkins job is building a branch named `aws-qa` which this PR has been merged into.{}}}{{{{}}{}}} {{If it helps to debug, the Jenkins "Changes" tab contains a link to the commit that is bundled in the merge commit. The Changes tab doesn't reference the merge commit.}} h1. Changes h2. Summary # -Cascade save and delete from AppDomain to Config |Commit a2c74e3e9efc5de10cc2c3138f4f8be1e100e303 by author- Cascade save and delete from AppDomain to Config| |
