Jesse Glick edited a comment on Bug JENKINS-17677

My guess is that whatever produces the updates.jenkins-ci.org content was changed to assume that the digest would be computed from JSON canonicalized by the new JSON library, whereas older versions of Jenkins have slightly different content.

Emergency workaround:

  1. Shut down Jenkins.
  2. Download http://jenkins-updates.cloudbees.com/update-center.json?version=1.480.3 and save it somewhere.
  3. Edit the file, stripping off the first and last lines: updateCenter.post( and );
  4. Save as $JENKINS_HOME/updates/default.json.
  5. Restart Jenkins.
  6. /pluginManager/available should now list the right plugins. Ignore those marked Jenkins Enterprise by CloudBees Plugin since they would require a Jenkins Enterprise license to run.
  7. Repeat 1–5 to check for new updates.

I would have thought 1–5 could be done simply by saving a new URL in /pluginManager/advanced but it seems this does not work; even if you click Check now Jenkins does not even try to download the specified update center content. Not sure why not.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to