public_git
/
kubernetes-operator
mirror of https://github.com/jenkinsci/kubernetes-operator.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Update migration.md

This commit is contained in:
Anuj Singh 2019-10-31 10:52:22 +05:30 committed by Paweł Prażak
parent 059e61bbb6
commit 54a8f4c5e4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/en/docs/Getting Started/latest/migration.md
View File

@ -19,7 +19,7 @@ We've had disabled master executors for security reasons.
In `v0.1.x` **Jenkins Operator** user configuration application was implemented using **Jenkins** jobs In `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. 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. 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.
In `v0.1.x` you can see if any of the configuration jobs failed or succeded in the **Jenkins** UI (job build logs). In `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.: Instead, you can make sure the operator is running correctly by inspecting its logs, e.g.: