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

WIP #32 shor description created, not finished yet

This commit is contained in:
Ewelina Wilkosz 2018-01-15 15:52:43 +01:00
parent 236ad75d9a
commit 124e148fc0
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/migrate.md Normal file
View File

@ -0,0 +1,19 @@
# How to migrate your traditionally configured Jenkins
So you're tired of manually configuring Jenkins each time you want to introduce a plugin or change existing setup?
Or maybe you're not feeling confident enough with the change you have in mind?
Jenkins Configuration as Code solves both problems - you don't need to access Jenkins to implement a change and you can always revert to previous version of configuration (if you keep your configuration under version control)
## [NOT SUPPORTED YET] Export existing configuration
To be able to do that - once it becomes supported feature - you need to install the plugin manually on your working Jenkins instance and use export function.
## Create jenkins.yaml from scratch
We've decided to use yaml format so writing the configuration "by hand" should be easy. Your existing Jenkins can be also used as a documentation - yaml file tries to mimic UI you're used to as much as possible.
Plugin provides documentation generated for your specific Jenkins instance - after you install it, and it is available at:
http://[your_jenkins_url]/plugin/configuration-as-code/
Various samples of plugins' configuration can be found in [demos](../demos) folder