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

Propose fix some typos (#117)

This commit is contained in:
John Eismeier 2018-02-20 01:38:12 -05:00 committed by Ewelina Wilkosz
parent 40b2c83fca
commit 771b136ca1
2 changed files with 27 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
IMPLEMENTATION.md
View File

@ -13,7 +13,7 @@ It has:
* a `name` to match a YAML entry,
* a `target` component type
* a `describe` method to document the attributes the target component exposes to configuraiton
* a `describe` method to document the attributes the target component exposes to configuration
* a `configure` method to configure the target component
From a yaml node with associated `Configurator`, configuration-as-code will handle every
@ -53,7 +53,7 @@ will be detected as Attribute named `foo` with target type `Foo` with multiple v
### Configuration
Configurator also has to implement the `configure` method to process yaml content and instanciate or configure
Configurator also has to implement the `configure` method to process yaml content and instantiate or configure
target component. The actual mechanism depends on the target. Configuration-as-Code do provide generic
mechanisms which cover most Jenkins components.
@ -100,4 +100,3 @@ As a short terms workaround, a custom `Configurator` glue-code implementation ca
Initial secrets are handled by the concrete implementations of the [SecretSource](https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/src/main/java/org/jenkinsci/plugins/casc/SecretSource.java). In order to implement a new
secret source, subclass `SecretSource` by extending it, and mark the new class with the `@Extension` annotation.

4
README.md
View File

@ -119,7 +119,7 @@ For this purpose, we delegate to the popular [job-dsl-plugin](https://wiki.jenki
and run a job-dsl script to create an initial set of jobs.
Typical usage is to rely on a multi-branch, or organization folder job type, so further jobs will be dynamically
created. So a multi-branch seed job will prepare a master to be fully configured for CI/CD targetting a repository
created. So a multi-branch seed job will prepare a master to be fully configured for CI/CD targeting a repository
or organization.
Job-DSL plugin uses groovy syntax for it's job configuration DSL, so you'll have to mix yaml and groovy within your
@ -163,7 +163,7 @@ If all those 4 are present, Configuration-as-Code will try to gather initial sec
## Supported plugins
Here is a list of plugin we have successfuly tested to support configuration-as-code approach :
Here is a list of plugin we have successfully tested to support configuration-as-code approach :
- [x] active directory plugin ([details](demos/credentials/README.md))
- [x] artifactory plugin ([details](demos/artifactory/README.md))