Update migration-guide-0.1.1-to-0.2.0.md
This commit is contained in:
parent
fc669bee2b
commit
b07f217701
|
|
@ -18,9 +18,13 @@ spec:
|
||||||
configurationAsCode:
|
configurationAsCode:
|
||||||
configurations:
|
configurations:
|
||||||
- name: jenkins-operator-user-configuration-<cr_name>
|
- name: jenkins-operator-user-configuration-<cr_name>
|
||||||
|
secret:
|
||||||
|
name: jenkins-operator-user-configuration-<cr_name>
|
||||||
groovyScripts:
|
groovyScripts:
|
||||||
configurations:
|
configurations:
|
||||||
- name: jenkins-operator-user-configuration-<cr_name>
|
- name: jenkins-operator-user-configuration-<cr_name>
|
||||||
|
secret:
|
||||||
|
name: jenkins-operator-user-configuration-<cr_name>
|
||||||
```
|
```
|
||||||
|
|
||||||
Jenkins configuration jobs (Configure Seed Jobs, jenkins-operator-base-configuration, jenkins-operator-user-configuration) have been removed from Jenkins.
|
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.
|
Now, when Jenkins configuration jobs are removed, you must use this command to see if configuration was failed.
|
||||||
```bash
|
```bash
|
||||||
$ kubectl -n logs deployment/jenkins-operator
|
$ kubectl -n logs deployment/jenkins-operator
|
||||||
```
|
```
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue