This blog post is part 1 of a Configuration-as-Code series
Jenkins is highly flexible and is today the de facto standard for implementing CI/CD, with an active community to maintain plugins for almost any combination of tools and use-cases.
But flexibility has a cost: in addition to Jenkins core, many plugins require some system-level configuration to be set so they can do their job.
In some circumstances,...