We have an integration between an on-premise Octopus Deploy instance and a cloud Jira instance. Yesterday morning (2020-12-03) we worked with Jira to change our Jira instance name/url.
We needed to update a handful of integrations to use the new url. Unfortunately, ever since the change, we have been receiving errors within our Octo/Jira integration.
In the screenshot below, you will be able to see two different error messages.
The first error
Unable to publish data to Jira. Response code: BadRequest, Message: An error occurred while posting deployment info to Jira: Response status code does not indicate success: 500 (Internal Server Error).
This is the error that is returned when the system is using the original url
In the middle of this deployment, I switched the url to the new one, which leads to …
The second error
Unable to publish data to Jira. Response code: BadRequest, Message:
This is the error that is returned when the system is using the new url
The difference between the messages kind of makes sense, because the old url probably shouldn’t be responding. However, it’s difficult to troubleshoot the new error because there is no
Message associated with it.
Here’s the configuration information from my test machine:
So, why not ask Atlassian/Jira about this?
My first thought was to ask them, and so I went to look at the configuration in Jira. And … the configuration looked almost like it hadn’t been configured. However, it’s been soo long since I looked at this page/screen that I have no point of reference to really compare it to.
To me, the page seems to indicate that if I want to know anything about the configuration, I need to click the Get started button.
When I click the Get started button, it starts to redirect to a new screen, but hangs on the loading spinner while it tries to connect to
If I wait long enough, the connection will time out and I will get a
Something's gone wrong error toaster from Jira’s standard error handling.
So, I then followed the Support and issues link from the page with the Get started button, which brought me to these forums. That’s why I’m posting here.
My gut feeling is that changing the url with Atlassian/Jira messed up the ConnectApp configuration with Octopus Deploy. So, I’m wondering what might be the right path to take in order to look further into this?
Octopus Installation Info
Octopus Deploy Server On-Premise
This forum is kind of public, so I can supply that info; but maybe in a different communication area.