Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A change in core affected the plugin.</p> <p>Briefly, there is a conflict between versions of Bouncy Castle in core and the plugin. As the plugin has to support a wide range of Jenkins versions, it includes a version of Bouncy Castle, and requests that this be loaded in an isolated classloader... Under certain circumstances core will resolve the classloaders differently when looking for extensions, and the extension can end up resolving a different version of Bouncy Castle... which results in the extension (free-license-plugin) not being found, and the corresponding NPE.</p> <p>We fixed this issue a couple of days after 1.490 was released. The fix is in cloudbees-license 3.5 and free-license 3.2 (also in nectar-license 3.3 - but that is only of relevance if you are running any of the Jenkins Enterprise plugins)</p> <p>To get a borked system back to working here is the set of steps to follow:</p> <ol> <li>Stop Jenkins (if you haven't already)</li> <li>Remove the following directories <code>$JENKINS_HOME/plugins/cloudbees-license</code>, <code>$JENKINS_HOME/plugins/free-license</code> and if present <code>$JENKINS_HOME/plugins/nectar-license</code></li> <li>Remove the following files <code>$JENKINS_HOME/plugins/cloudbees-license.hpi</code>, <code>$JENKINS_HOME/plugins/cloudbees-license.jpi</code>, <code>$JENKINS_HOME/plugins/free-license.hpi</code>, <code>$JENKINS_HOME/plugins/cloudbees-license.jpi</code>, and if present <code>$JENKINS_HOME/plugins/nectar-license.hpi</code> or <code>$JENKINS_HOME/plugins/nectar-license.jpi</code> (<em>Note:</em> normally there will only be either the <code>.hpi</code> <em>or</em> the <code>.jpi</code> file present. Which is present depends on what version of Jenkins was installed when you downloaded the plugin originally. It doesn't matter which.</li> <li><p>Download the latest versions of the plugins that you removed: (<em>Note:</em> only download the <code>nectar-license</code> plugin if you removed it in steps 2 and 3)</p> <ul> <li><a href="http://jenkins-updates.cloudbees.com/download/plugins/cloudbees-license/3.5/cloudbees-license.hpi" rel="nofollow">cloudbees-license</a></li> <li><a href="http://jenkins-updates.cloudbees.com/download/plugins/free-license/3.2/free-license.hpi" rel="nofollow">free-license</a></li> <li><a href="http://jenkins-updates.cloudbees.com/download/plugins/nectar-license/3.3/nectar-license.hpi" rel="nofollow">nectar-license</a> (only if needed)</li> </ul> <p>It is up to you whether you rename the <code>.hpi</code> to <code>.jpi</code>. Jenkins will pick it up either way, but for longer-term compatibility I would recommend renaming them to the <code>.jpi</code> extension.</p></li> <li><p>Start Jenkins</p></li> <li>Do the <a href="http://www.youtube.com/watch?v=DH2gGu8cGHY" rel="nofollow">funky-chicken dance</a></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload