Jenkins is an open source automation server that development teams use to build, test and deploy their applications. If you have worked in an environment with CI/CD pipelines, chances are that you have used Jenkins. And because Jenkins has so many configuration options and plugins available, it can be quite an effort to set up.

Now imagine configuring all of your infrastructure as code, but configuring the tool that builds, tests and deploys your infrastructure and applications through a web UI. Sounds counterintuitive, right?

In the blogs in this repo, I’ll show you how to configure Jenkins as code. Even setting up your pipeline configuration in a fully automated, version controlled way. If you already know why you use Jenkins, you can skip the first paragraph:

• (Blog 1) Why a build server, and why Jenkins?
• (Blog 1) Jenkins: Configuration as Code (JCasC) plugin
• (Blog 1) Automating Jenkins configuration with Docker and JCasC
• (Blog 2) Automating pipeline setup: Jenkins Job DSL plugin
• (Blog 2) Why I did not get the ‘perfect’ setup running yet..
• (Blog 3) Passing secrets to your Jenkins container from AWS ECS