Improve error message for customers when sending build/deployment object to Jira fails.
One of our customers opened a support ticket asking about some of the logs they saw in one of their failed pipelines:
`3:01:33 [ATLASSIAN CLOUD PLUGIN] [INFO] jiraSendDeploymentInfo(jira-instance.atlassian.net): FAILURE_DEPLOYMENTS_API_RESPONSE: Failed to send deployment information to Jira: {jira-instance}.atlassian.net. {"timestamp":"2022-09-13T11:01:33.520+00:00","status":424,"error":"Failed Dependency"}
Why does this error happen?
What does "Failed Dependency" mean in this context?
How can we prevent that the error happens and report reliably the deployment status?`
We checked the Forge logs and there was an error when getting the secrets for that integration, so then the call failed. It was a one-off event that hasn't happened again so this PR just improves the log message since a 424 is not really helpful for them but that's what we get back from the Forge app.
Improve error message for customers when sending build/deployment object to Jira fails. One of our customers opened a support ticket asking about some of the logs they saw in one of their failed pipelines:
We checked the Forge logs and there was an error when getting the secrets for that integration, so then the call failed. It was a one-off event that hasn't happened again so this PR just improves the log message since a 424 is not really helpful for them but that's what we get back from the Forge app.