From 54a8f4c5e483c6a2d28242a1e06f436453579e5b Mon Sep 17 00:00:00 2001 From: Anuj Singh <30765911+underscoreanuj@users.noreply.github.com> Date: Thu, 31 Oct 2019 10:52:22 +0530 Subject: [PATCH] Update migration.md --- website/content/en/docs/Getting Started/latest/migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/en/docs/Getting Started/latest/migration.md b/website/content/en/docs/Getting Started/latest/migration.md index 4465b2cb..571900a2 100644 --- a/website/content/en/docs/Getting Started/latest/migration.md +++ b/website/content/en/docs/Getting Started/latest/migration.md @@ -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 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). Instead, you can make sure the operator is running correctly by inspecting its logs, e.g.: