[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"

filip@reiimer.se (JIRA)

unread,

Apr 13, 2018, 5:15:02 AM4/13/18

to jenkinsc...@googlegroups.com

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)

john.westcott.iv@redhat.com (JIRA)

unread,

Apr 13, 2018, 10:08:02 AM4/13/18

to jenkinsc...@googlegroups.com

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://<server>//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?