Migration from v0.1.x
Adding the seed job agent
v0.2.0 seed jobs are not run by master executors, but by a dedicated agent deployed as a Kubernetes Pod.
We’ve had disabled master executors for security reasons.
Replacing configuration jobs with Groovy scripts
v0.1.x Jenkins Operator user configuration application was implemented using Jenkins jobs
and this mechanism was replaced since
v0.2.0 with Groovy scripts implementing the same functionality.
As a result, the Jenkins configuration jobs (“Configure Seed Jobs”, “jenkins-operator-base-configuration”, “jenkins-operator-user-configuration”) are no longer visible in Jenkins UI.
v0.1.x you can see if any of the configuration jobs failed or succeded in the Jenkins UI (job build logs).
Instead, you can make sure the operator is running correctly by inspecting its logs, e.g.:
$ kubectl -n logs deployment/jenkins-operator
Making User Configuration sources configurable
v0.1.x Jenkins Operator user configuration was stored in a
ConfigMap and a
jenkins-operator-user-configuration-<cr_name>, and its name was hardcoded in the operator.
v0.2.0 the user configuration can be stored in a multiple
and has to be explicitly pointed to with
for the Configuration as Code plugin,
spec.groovyScripts.secret for the more advanced groovy scripts.
If you want to use
v0.1.x operator configuration with
v0.2.x you have to modify your Jenkins Custom Resource(s)
and add explicit references to the existing
apiVersion: jenkins.io/v1alpha2 kind: Jenkins metadata: name: <cr_name> spec: ... configurationAsCode: configurations: - name: jenkins-operator-user-configuration-<cr_name> secret: name: jenkins-operator-user-configuration-<cr_name> groovyScripts: configurations: - name: jenkins-operator-user-configuration-<cr_name> secret: name: jenkins-operator-user-configuration-<cr_name> ...