From b07f217701ee8e14c2774562bf2522e0bd4e79f1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tomasz=20S=C4=99k?= <31410181+tomaszsek@users.noreply.github.com> Date: Wed, 23 Oct 2019 12:22:02 +0200 Subject: [PATCH] Update migration-guide-0.1.1-to-0.2.0.md --- documentation/migration-guide-0.1.1-to-0.2.0.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/documentation/migration-guide-0.1.1-to-0.2.0.md b/documentation/migration-guide-0.1.1-to-0.2.0.md index 3b604c12..7a76f329 100644 --- a/documentation/migration-guide-0.1.1-to-0.2.0.md +++ b/documentation/migration-guide-0.1.1-to-0.2.0.md @@ -18,9 +18,13 @@ spec: configurationAsCode: configurations: - name: jenkins-operator-user-configuration- + secret: + name: jenkins-operator-user-configuration- groovyScripts: configurations: - name: jenkins-operator-user-configuration- + secret: + name: jenkins-operator-user-configuration- ``` Jenkins configuration jobs (Configure Seed Jobs, jenkins-operator-base-configuration, jenkins-operator-user-configuration) have been removed from Jenkins. @@ -29,4 +33,4 @@ In v0.1.1 you can see if configuration failed or successfully updated in Jenkins Now, when Jenkins configuration jobs are removed, you must use this command to see if configuration was failed. ```bash $ kubectl -n logs deployment/jenkins-operator -``` \ No newline at end of file +```