Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60202

Error when --Jenkins-update-manager value has trailing slash

      Command line like this:

          java -jar jenkins-plugin-manager-1.0.1.jar -f plugins.txt --verbose --plugin-download-directory ~/plugins --no-download --list --war /usr/lib/jenkins/jenkins.war --jenkins-update-center https://jenkins-updates.cloudbees.com/

      fails with stack trace containing

          java.io.FileNotFoundException: https://jenkins-updates.cloudbees.com//update-center.json

      Remove the trailing slash from the desired update center and it accepts the supplied update center. (This is the workaround)

          [JENKINS-60202] Error when --Jenkins-update-manager value has trailing slash

          Will Freeman added a comment - - edited

          If you are still encountering this error, could you post the full stack trace as well as the plugins.txt file you are using?  Thanks.

           

          Edit:  based on minimal testing, it looks like it might be a a specific issue with the jenkins-updates.cloudbees.com update center.  Using another update center, with and without a trailing slash, doesn't seem to recreate the error.  

          Will Freeman added a comment - - edited If you are still encountering this error, could you post the full stack trace as well as the plugins.txt file you are using?  Thanks.   Edit:  based on minimal testing, it looks like it might be a a specific issue with the jenkins-updates.cloudbees.com update center.  Using another update center, with and without a trailing slash, doesn't seem to recreate the error.  

          Alex Earl added a comment -

          There are some changes to this in 1.0.2 I believe, have you tried with that?

          Alex Earl added a comment - There are some changes to this in 1.0.2 I believe, have you tried with that?

          Will Freeman added a comment -

          Looks like the issue is fixed in the 1.0.2 release.  Thanks. 

          Will Freeman added a comment - Looks like the issue is fixed in the 1.0.2 release.  Thanks. 

          Will Freeman added a comment -

          Issue no longer persist as URLs are handled differently and trailing slash is no longer an issue.  

          Will Freeman added a comment - Issue no longer persist as URLs are handled differently and trailing slash is no longer an issue.  

            leemeador leemeador
            leemeador leemeador
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: