Jenkins K8s

  • Canonical IS DevOps
Channel Revision Published Runs on
latest/stable 127 07 Nov 2024
Ubuntu 22.04
latest/edge 128 19 Nov 2024
Ubuntu 22.04
juju deploy jenkins-k8s
Show information

Platform:

How to configure restart-time-range

Configure restart-time-range

Use the restart-time-range configuration to set the time interval when jenkins-k8s

  1. automatically applies the latest patches for the current LTS version.
  2. automatically remove plugins that are installed on the system but are not part of the plugins configuration option.

The minimum time interval is 1 hour. The time range is applied each day of the week.

juju config jenkins-k8s restart-time-range=<desired-time-range>

# desired-time-range example: 22-03 to allow patching from 10PM-03AM UTC.

Assuming the installed Jenkins LTS version to be 2.387, the output of juju status should look similar to the following before the update:

Model               Controller          Cloud/Region        Version  SLA          Timestamp
jenkins-tutorial    microk8s-localhost  microk8s/localhost  2.9.43   unsupported  <timestamp>

App                Version  Status      Scale  Charm              Channel      Rev  Address         Exposed  Message
jenkins-k8s        2.387  active          1  jenkins-k8s        latest/edge     0   <ip-address>    no

Unit            Workload  Agent  Address       Ports  Message
jenkins-k8s/0*  active    idle   <ip-address>

After the update:

Model               Controller          Cloud/Region        Version  SLA          Timestamp
jenkins-tutorial    microk8s-localhost  microk8s/localhost  2.9.43   unsupported  <timestamp>

App                Version  Status      Scale  Charm              Channel      Rev  Address         Exposed  Message
jenkins-k8s        2.387.3  active          1  jenkins-k8s        latest/edge  0    <ip-address>    no

Unit            Workload  Agent  Address       Ports  Message
jenkins-k8s/0*  active    idle   <ip-address>

Note the difference in patch version under the Version column of the application status.

You can verify that the patch has been applied by signing into the Jenkins UI and checking the version number at the bottom right corner of the footer.