Configuration as Code: A guide to the approach and benefits

Configuration as Code, or CasC, is tool-agnostic and clarifies the management of Jenkins® instances by capturing their configurations in human-readable, declarative configuration files. These files are maintained as first-class revision-controlled artifacts that can easily apply back to controllers if a configuration fails, or adjust, depending on the team environment.

Key benefits of CasC for Jenkins users include:

  • Prevention of configuration drift

  • Easily auditable changes

  • Automatically reproducible Jenkins instances

Read this guide to learn more about the CasC approach and other benefits of scale, governance, and autonomy it can bring to development teams.

Jenkins® is a registered trademark of LF Charities Inc.

Register to download the whitepaper

Loading form...
Passwords must be at least 8 characters and contain at least 3 of the following 4 types of characters: a lower-case letter, an upper-case letter, a number, a special character (such as !@#$%^&*).