# jenkinsci/configuration-as-code-plugin

Jenkins Configuration as Code Plugin

Repository: https://github.com/jenkinsci/configuration-as-code-plugin
Canonical: https://ross.abutalabs.com/products/configuration-as-code-plugin
Homepage: https://plugins.jenkins.io/configuration-as-code
Language: Java
License: MIT
License Family: permissive
Topics: configuration-as-code, jenkins, jenkins-configuration, jcasc, hacktoberfest
Last push: 2026-08-24T02:33:14+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 97, longevity 100
- inputs: {"age_days": 3239, "days_push": 10, "days_rel": 23, "gap_med": 7, "n_releases_24m": 48}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2795, forks 754 (observed 2026-08-28T04:07:22.312344+00:00)

## What it is
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
- artifact type: plugin
- maturity: active
- function: configuration-management, developer-tools, yaml, secrets-management
- domain: self-hosted, developer-tools
- platform: jvm, self-hosted
- tags: jenkins, jcasc, declarative-configuration, ci-cd, infrastructure-as-code, devops, automation, docker

## Member repositories
- jenkinsci/configuration-as-code-plugin (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:22.312344+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T08:14:40.607878+00:00, confidence not recorded.
  - readme: https://github.com/jenkinsci/configuration-as-code-plugin (fetched 2026-08-28T04:07:22.312344+00:00, sha b4f7c492856f)
  - homepage: https://plugins.jenkins.io/configuration-as-code (fetched 2026-08-29T09:55:00.811093+00:00, sha 3238dbef96e7)
  - site_page: https://plugins.jenkins.io/configuration-as-code/releases (fetched 2026-08-29T09:55:00.820460+00:00, sha 4fb7e4b8fb96)
  - site_page: https://jenkins.io/security/advisory/2019-07-31 (fetched 2026-08-29T09:55:00.822519+00:00, sha 2f576864b82f)
- Data as of 2026-08-30T08:39:29.467469+00:00.