Why are core upgrades not shown in CJP 2.7.19.1 and 2.7.19.0.1?

Issue

Why are core upgrades not shown in CJP 2.7.19.1 and 2.7.19.0.1?

Environment

  • CloudBees Jenkins Enterprise 2.7.19.1 and 2.7.19.0.1
  • CloudBees Jenkins Operations Center 2.7.19.1 and 2.7.19.0.1

Resolution

There is a known issue (internal code CJP-5676) in the specified versions that causes the Manage Jenkins page to show an error when a core upgrade is available. To avoid this error, when using the CloudBees Update Centers from this version, and only from these affected versions, no core upgrades will be offered, so they should be downloaded manually from CloudBees Network

The related release notes are:

CloudBees Jenkins Enterprise 2.7.19.1
CloudBees Jenkins Operations Center 2.7.19.1
CloudBees Jenkins Enterprise 2.7.19.0.1
CloudBees Jenkins Operations Center 2.7.19.0.1

Please be advised that you may be affected by the underlying issue if you are using a custom and / or CJOC-provided Update Centers that offers a core upgrade.

Recommended action is:

  • Upgrading to version 2.7.20.2 or later if you are on 2.7.19.1 (rolling train)
  • Upgrading to version 2.7.20.0.2 or later if you are on 2.7.19.0.1 (fixed train)

Until an upgrade can be performed, the administrative monitor causing the error can be disabled by running
the following script at the $JENKINS_URL/script page (Script Console):

AdministrativeMonitor.all().each {
  if (it instanceof UpdateCenter$CoreUpdateMonitor) {
    if (it.isEnabled()) {
      it.disable(true);
    }
    println "Core update monitor should be disabled."
  }
}

Once the upgrade has been performed, the administrative monitor can be enabled again by executing the following script in the Script Console:

AdministrativeMonitor.all().each { 
  if (it instanceof UpdateCenter$CoreUpdateMonitor) { 
    if (!it.isEnabled()) { 
      it.disable(false); 
    } 
    println "Core update monitor should be enabled."
  } 
}
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.