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

Fix a internal link to PLUGINS.md. Fix some typos. (#1434) 

Co-authored-by: Joseph Petersen <josephp90@gmail.com>
This commit is contained in:
Mads Jensen 2020-07-19 04:52:01 +02:00 committed by GitHub
parent 1ca90c9ddf
commit b2fe968da8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/COMPATIBILITY.md
View File

@ -5,7 +5,7 @@ Because of how the JCasC was designed, plugins _should_ be expected to work out
We rely heavily on data bindings so if a plugin is not setup according to expected design pattern for data binding.
JCasC cannot communicate properly with the plugin without fixing their data binding issues or writing a special configurator.
The path of least resistence is fixing the data binding, since other plugins in the Jenkins eco-system relies heavely on data binding.
The path of least resistance is fixing the data binding, since other plugins in the Jenkins eco-system rely heavily on data binding.
The list of already known issues in the Jenkins issue tracker, are tracked through using the label `jcasc-compatibility` [see dashboard][dashboard].
@ -13,7 +13,7 @@ The list of already known issues in the Jenkins issue tracker, are tracked throu
Create an issue at [issues.jenkins-ci.org](https://issues.jenkins-ci.org) with the label `jcasc-compatibility` and fill out the details.
[Link to create issue][new-jira-issue]
Create an github issue for crosslink purposes on this repository.
Create a Github issue for crosslink purposes on this repository.
If you prefer the [new issue for plugin compatibility][new-github-issue] should take you through the entire workflow.

2
docs/IMPLEMENTATION.md
View File

@ -94,7 +94,7 @@ Jenkins has hundreds of Descriptors, most of them for internal technical reasons
so only the ones that have a `global` view are accessible from JCasC.
For Descriptors to work well with JCasC, they need to follow
[some design best practices](docs/PLUGINS.md) in terms of data binding. This is not such a common thing,
[some design best practices](PLUGINS.md) in terms of data binding. This is not such a common thing,
so we expect this will require some evangelism on plugin developers.
As short term workaround, a custom `Configurator` glue-code implementation can be implemented.