From 124e148fc0563523cd693f69867e59dc96861966 Mon Sep 17 00:00:00 2001 From: Ewelina Wilkosz Date: Mon, 15 Jan 2018 15:52:43 +0100 Subject: [PATCH] WIP #32 shor description created, not finished yet --- docs/migrate.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 docs/migrate.md diff --git a/docs/migrate.md b/docs/migrate.md new file mode 100644 index 00000000..12a53e3d --- /dev/null +++ b/docs/migrate.md @@ -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