jenkinsci/configuration-as-code-plugin

Health v2 · maintenance only

Adoption not part of the score

2795 stars · 754 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

The Jenkins Configuration as Code (JCasC) plugin lets administrators configure Jenkins controllers and plugins via human-readable declarative YAML files instead of the web UI or Groovy init scripts. It supports secrets handling, config export, validation via JSON schema, and hot configuration reload.

Use cases

• configure jenkins from a yaml file
• automate jenkins controller setup
• version-control jenkins configuration
• replace groovy init scripts for jenkins
• reload jenkins configuration without restart
• manage jenkins secrets in configuration
• export current jenkins configuration as code
• validate jenkins config with json schema

When to choose

• you want reproducible, version-controlled Jenkins setup
• you provision Jenkins controllers in Docker or Kubernetes
• you want declarative config without learning Jenkins internals
• you need to audit or export existing Jenkins configuration

When to avoid

• you run Jenkins without plugin support or on very old versions
• your plugins lack JCasC support and you need to configure them
• you prefer imperative Groovy scripts needing full Jenkins API access

Facets

plugin · maturity active

configuration-management developer-tools yaml secrets-management self-hosted developer-tools jvm self-hosted jenkins jcasc declarative-configuration ci-cd infrastructure-as-code devops automation docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="jenkinsci/configuration-as-code-plugin")