As the service isn’t returning any additional details in the response in terms of what it doesn’t like about the request Jira is making, it’s hard to say why the installation is failing strictly from a Jira perspective. Jira is receiving a 400 HTTP response from the Octopus Deploy service during the installation attempt. Unfortunately, that isn’t telling us much more than what you were already able to identify via the browser console. Ĭaused by: .: Error contacting remote application 400:: 17:46:32.249ĞRROR .-safeĚn exception occurred while installing the plugin. I took a look at the Jira application logs and discovered the following errors. I tried to install the Octopus Deploy add-on in your site and ran into the same behavior you describe. The email was really clear and it seems like it would be helpful to just paste it into this thread verbatim: I’ve received a reply back from Atlassian Support. Going off of your “Gut-Feeling” - have you tried removing your cache and cookies or even just running chrome in incognito mode for the re-installation of the app? I have tested the removal and re-adding of the Octopus app and it’s currently working fine for me. I 100% agree with you, it definitely seems to be an issue between cloud based Jira and the atlassian marketplace. I assumed that it meant the Cloud based Jira instance was having a problem reaching out to the Cloud based Octopus Deploy ConnectApp. However, my explanation definitely wasn’t detailed enough, so my apologies. If you are behind a corporate firewall you may be able to access “ ” and its sub-pages however a url that starts with marketplace may be blocked, which I thought may cause issues. During installation of the app, your browser also does a direct call to: “ ”. That article seems to be directed towards people that have an on-premise based Atlassian/Jira instance. However, it’s difficult to troubleshoot the new error because there is no Message associated with it. The difference between the messages kind of makes sense, because the old url probably shouldn’t be responding. This is the error that is returned when the system is using the new url. In the middle of this deployment, I switched the url to the new one, which leads to … This is the error that is returned when the system is using the original url. Response code: BadRequest, Message: An error occurred while posting deployment info to Jira: Response status code does not indicate success: 500 (Internal Server Error). In the screenshot below, you will be able to see two different error messages. Unfortunately, ever since the change, we have been receiving errors within our Octo/Jira integration. We needed to update a handful of integrations to use the new url. Yesterday morning () we worked with Jira to change our Jira instance name/url. We have an integration between an on-premise Octopus Deploy instance and a cloud Jira instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |