[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-48835 Testing a connection results in "The item does not exist" Change By: John Westcott Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187621.1515346312000.4807.1578495420783%40Atlassian.JIRA.
[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48835 Testing a connection results in "The item does not exist" Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187621.1515346312000.4810.1578495420827%40Atlassian.JIRA.
[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott commented on JENKINS-48835 Re: Testing a connection results in "The item does not exist" Filip Reimer you are correct about the API transforming the urls to end with a /. In Jenkins, when you add a / to the end of the URL Jenkins ends up making calls to Tower like https:api/v2/ping (note the double slash at the start of the path in the URL. This is why the test fails with the message "The item does not exist". I just released an 0.8.3 version of the plugin which will string the ending / of the URL so the plugin should now work with a url of https://towerserver.something.com/ or https://towerserver.something.com. It normally takes a couple hours for the new version of the plugin to propagate. If you get a chance can you test this change and let me know if its now working either way for you? Alexandr Suprunevich can you test the 0.8.3 version of the plugin and let me know if this change now remediates the issue you were having? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title Filip Reimer commented on JENKINS-48835 Re: Testing a connection results in "The item does not exist" The same behavior is seen if the URL entered ends with /, the url towards the API gets transformed to /v1/job_templates/ instead of /api/v1/job_templates/. Simply changing the URL from https://towerserver.something.com/ to https://towerserver.something.com fixes this issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
