jenkinsci
/
configuration-as-code-plugin
mirror of https://github.com/jenkinsci/configuration-as-code-plugin.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clear information about overwriting configuration keys (#1533) 

Co-authored-by: Benjamin Balder Bach <benjamin@overtag.dk>
Co-authored-by: Oleg Nenashev <o.v.nenashev@gmail.com>
This commit is contained in:
Benjamin Balder Bach 2021-02-04 09:04:11 +01:00 committed by GitHub
parent d995f5ad46
commit 48e4706bff
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -130,6 +130,8 @@ If `CASC_JENKINS_CONFIG` points to a folder, the plugin will recursively travers
:x: `/jenkins/.configs/casc_configs/..dir2/config.yaml` :x: `/jenkins/.configs/casc_configs/..dir2/config.yaml`
</details> </details>
All configuration files that are discovered MUST be supplementary. They cannot overwrite each other's configuration values. This creates a conflict and raises a `ConfiguratorException`. Thus, the order of traversal does not matter to the final outcome.
Instead of setting the `CASC_JENKINS_CONFIG` environment variable, you can also define using Instead of setting the `CASC_JENKINS_CONFIG` environment variable, you can also define using
the `casc.jenkins.config` Java property. This is useful when installing Jenkins via a package the `casc.jenkins.config` Java property. This is useful when installing Jenkins via a package
management tool and can't set an environment variable outside of a package-managed file, which could management tool and can't set an environment variable outside of a package-managed file, which could