Add a bit of extra words to make complete sentences
This commit is contained in:
parent
e65508bd19
commit
6cb180cda1
|
|
@ -7,12 +7,12 @@ description: >
|
||||||
How to customize Jenkins
|
How to customize Jenkins
|
||||||
---
|
---
|
||||||
|
|
||||||
Jenkins can be customized using groovy scripts or the configuration as code plugin. All custom configuration is stored in
|
Jenkins can be customized using by groovy scripts or the Jenkins Configuration as Code Plugin. All custom configuration is stored in
|
||||||
the **jenkins-operator-user-configuration-<cr_name>** ConfigMap which is automatically created by the **Jenkins Operator**.
|
the **jenkins-operator-user-configuration-<cr_name>** ConfigMap, which is automatically created by the **Jenkins Operator**.
|
||||||
|
|
||||||
The **Jenkins Operator** creates a **jenkins-operator-user-configuration-<cr_name>** secret where the user can store sensitive
|
The **Jenkins Operator** creates a **jenkins-operator-user-configuration-<cr_name>** secret where the user can store sensitive
|
||||||
information used for custom configuration. If you have an entry in the secret named `PASSWORD` then you can use it in the
|
information used for custom configuration. If you have an entry in the secret named `PASSWORD` then you can use it in the
|
||||||
Configuration as Plugin as `adminAddress: "${PASSWORD}"`.
|
Jenkins Configuration as Code Plugin as `adminAddress: "${PASSWORD}"`.
|
||||||
|
|
||||||
```
|
```
|
||||||
kubectl get secret jenkins-operator-user-configuration-<cr_name> -o yaml
|
kubectl get secret jenkins-operator-user-configuration-<cr_name> -o yaml
|
||||||
|
|
@ -63,8 +63,8 @@ metadata:
|
||||||
namespace: default
|
namespace: default
|
||||||
```
|
```
|
||||||
|
|
||||||
When the **jenkins-operator-user-configuration-<cr_name>** ConfigMap is updated Jenkins automatically
|
When the **jenkins-operator-user-configuration-<cr_name>** ConfigMap is updated, Jenkins automatically
|
||||||
runs the **jenkins-operator-user-configuration** Jenkins Job which executes all scripts then
|
runs the **jenkins-operator-user-configuration** Jenkins Job which executes all scripts, and then
|
||||||
runs the **jenkins-operator-user-configuration-casc** Jenkins Job which applies the Configuration as Code configuration.
|
runs the **jenkins-operator-user-configuration-casc** Jenkins Job which applies the Configuration as Code configuration.
|
||||||
|
|
||||||
## Install Plugins
|
## Install Plugins
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue