#348 Fix code review issues
This commit is contained in:
parent
4563b1851f
commit
5e6c031f03
|
|
@ -89,6 +89,14 @@ kubectl apply -f deploy/crds/jenkins_v1alpha2_jenkins_cr.yaml
|
|||
2020-04-27T10:00:06.140+0200 INFO controller-jenkins jenkins/jenkins_controller.go:338 User configuration phase is complete, took 3m26s {"cr": "example"}
|
||||
```
|
||||
|
||||
Two log lines says that Jenkins Operator works correctly:
|
||||
|
||||
* `Base configuration phase is complete` - ensures manifests, Jenkins pod, Jenkins configuration and Jenkins API token
|
||||
* `User configuration phase is complete` - ensures Jenkins restore, backup and seed jobs along with user configuration
|
||||
|
||||
> Details about base and user phase can be found [here](https://jenkinsci.github.io/kubernetes-operator/docs/how-it-works/architecture-and-design/).
|
||||
|
||||
|
||||
```bash
|
||||
kubectl get jenkins -o yaml
|
||||
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ spec:
|
|||
|
||||
You can change their versions.
|
||||
|
||||
The **Jenkins Operator** will then automatically install plugins after the Jenkins master pod restarts.
|
||||
The **Jenkins Operator** will then automatically install plugins after the Jenkins master pod restart.
|
||||
|
||||
#### Apply plugin's config
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue