-
Bug
-
Resolution: Fixed
-
Minor
-
None
Hi
trying to use the Atlassian Jira Software Cloud plugin in jenkins to send deployment data to jira like this:
jiraSendDeploymentInfo site: 'sundaysky.atlassian.net', environmentId: 'prod', environmentName: 'prod', environmentType: 'production'
I get an error response:
jiraSendDeploymentInfo: FAILURE_DEPLOYMENTS_API_RESPONSE: Failed to send deployment information to Jira: sundaysky.atlassian.net. Error response code 403 when submitting update to Jira
When sending build info all is working as expected
jiraSendBuildInfo site: 'sundaysky.atlassian.net'
so it seems that it's not a credentials issue.
would be very happy to get help with this issue.
Thanks!
[JENKINS-66237] jiraSendDeploymentInfo returns error code 403
Ishay
created issue -
Navya
made changes -
| Assignee | Original: Rafal Myslek [ rafalmyslek ] | New: Navya [ nsurendran ] |
Navya
added a comment - ishaymelcer, May I know the data you were trying to send to jiraSendBuildInfo. The error response that is received is from Jira API. It looks like Jira APi is sending forbidden response to jenkins plugin.
Can you provide console logs of jenkins deployment as well?
Navya
added a comment - ishaymelcer , May I know the data you were trying to send to jiraSendBuildInfo. The error response that is received is from Jira API. It looks like Jira APi is sending forbidden response to jenkins plugin.
Can you provide console logs of jenkins deployment as well? 
Ishay
added a comment - this is what i use for jiraSendBuildInfo:
jiraSendBuildInfo site: 'sundaysky.atlassian.net'
and this is the output:
[Pipeline] jiraSendBuildInfojiraSendBuildInfo: SUCCESS_BUILD_ACCEPTED: Successfully sent build information to Jira: sundaysky.atlassian.net. Accepted builds: [BuildKeyResponse\{pipelineId='RaaS/sundaysky-raas-globalcache-fuse/master', buildNumber=17}].
and this is for the jiraSendDeploymentInfo:
jiraSendDeploymentInfo site: 'sundaysky.atlassian.net', environmentId: 'prod', environmentName: 'prod', environmentType: 'production'
and this is the output:
[Pipeline] jiraSendDeploymentInfojiraSendDeploymentInfo: FAILURE_DEPLOYMENTS_API_RESPONSE: Failed to send deployment information to Jira: sundaysky.atlassian.net. Error response code 403 when submitting update to Jira
Ishay
added a comment - this is what i use for jiraSendBuildInfo:
jiraSendBuildInfo site: 'sundaysky.atlassian.net'
and this is the output:
[Pipeline] jiraSendBuildInfojiraSendBuildInfo: SUCCESS_BUILD_ACCEPTED: Successfully sent build information to Jira: sundaysky.atlassian.net. Accepted builds: [BuildKeyResponse\{pipelineId='RaaS/sundaysky-raas-globalcache-fuse/master', buildNumber=17}] .
and this is for the jiraSendDeploymentInfo:
jiraSendDeploymentInfo site: 'sundaysky.atlassian.net' , environmentId: 'prod' , environmentName: 'prod' , environmentType: 'production'
and this is the output:
[Pipeline] jiraSendDeploymentInfojiraSendDeploymentInfo: FAILURE_DEPLOYMENTS_API_RESPONSE: Failed to send deployment information to Jira: sundaysky.atlassian.net. Error response code 403 when submitting update to Jira
Navya
made changes -
| Attachment | New: 060BA121-978F-47AF-BAA7-E28562602841.jpeg [ 55341 ] |
Navya
added a comment - ishaymelcer, Can you make sure whether you have given permissions in Jira OAuth to send deployment information to jira?
Can you try creating a new OAUth credentials by ticking both builds and deployments and using that OAuth credentials try sending deployment information to jira?
Navya
added a comment - ishaymelcer , Can you make sure whether you have given permissions in Jira OAuth to send deployment information to jira?
Can you try creating a new OAUth credentials by ticking both builds and deployments and using that OAuth credentials try sending deployment information to jira?
Navya
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Navya
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
We are looking into this issue.