
# Jenkins

Automation server for building, testing and delivering software through configured pipelines.

Canonical page: https://launchinyourcloud.com/directory/jenkins/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Jenkins

Automation server for building, testing and delivering software through configured pipelines.

- Listing: https://launchinyourcloud.com/directory/jenkins/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses.
- Licensing model: open-source
- Installation: Run the official Jenkins Docker image or supported server package and attach appropriately isolated build agents.
- Architecture: Customer-operated Jenkins controller and build agents with persistent configuration
- Operations: Customer manages controller and agents, plugins, secrets, job permissions, storage, backups and security updates.
- Product website: https://www.jenkins.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Pipeline code, agents and plugins can access external source hosts, registries and deployment targets. A controller installed in an account does not contain every pipeline integration. Jenkins weekly 2.591 enables Content Security Policy enforcement on the Jenkins UI by default. Test installed plugins and custom UI integrations before adopting this weekly release; compatibility is tracked upstream. Administrators can use report-only mode while resolving incompatibilities, but disabling enforcement removes the protection.

MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Jenkins controller and build agents with persistent configuration. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- devops: Automation server for continuous integration, build, test and delivery pipelines; agents and plugins provide workload-specific integrations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/developer/jenkins/configure-on-linux-vm (checked 2026-11-12). 


### Cloud deployment evidence

- Jenkins installation on AWS (aws): https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/
  The Jenkins project documents installing the Jenkins server on a customer EC2 instance, not merely deploying build output to AWS.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Jenkins installation on an Azure Linux VM (azure): https://learn.microsoft.com/en-us/azure/developer/jenkins/configure-on-linux-vm
  Microsoft documents installing Jenkins on an Ubuntu VM in the customer subscription. Harden public access and review the current Jenkins and Java versions rather than copying old version pins.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Jenkins publishes community governance, contributor recognition and a release changelog updated in November 2026; these show sustained maintenance and community participation.

Reviewed 2026-11-10.

- Project governance: https://www.jenkins.io/project/governance/

- Current release changelog: https://www.jenkins.io/changelog/

- Community contributor recognition: https://www.jenkins.io/

### Sources

- Official installation and runtime: https://www.jenkins.io/doc/book/installing/docker/

- Upstream project and capabilities: https://github.com/jenkinsci/jenkins

- Current upstream license: https://www.jenkins.io/license/

- Jenkins weekly 2.591 release: https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.591

- Jenkins CSP default and upgrade guidance: https://github.com/jenkinsci/jenkins/pull/27727

### Licensing sources

- https://www.jenkins.io/license/

### Infrastructure sources

- https://www.jenkins.io/doc/book/installing/docker/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The security guide documents delegating authentication to an external identity provider using SAML/OIDC. The relevant plugins are not necessarily installed; match supported plugin/controller versions and configure authorization separately. Scope: Jenkins plugin-based security realm; not automatic core federation. Source: https://www.jenkins.io/doc/book/security/managing-security/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The installation guide identifies the official Jenkins image and persistent controller home. Build agents, privileged Docker access, plugins and workload resources require a separate security/capacity plan. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://www.jenkins.io/doc/book/installing/docker/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/jenkins/jenkins. Artifact reference: select an LTS or weekly versioned image tag.

- Minimum footprint / sizing: Documented. The guide lists 256 MB RAM and 1 GB disk as basic minima, with 10 GB suggested for Docker. A small team is recommended 4 GB+ RAM and 50 GB+ disk; build-agent resources are separate. Scope: Controller baseline, not total CI/build infrastructure. Source: https://www.jenkins.io/doc/book/installing/docker/ (reviewed 2026-11-14).

- License pricing: Documented. Jenkins core is MIT licensed. Plugins and bundled components have their own licences; commercial distributions, support, agents and infrastructure are separate costs. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/jenkinsci/jenkins/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is jenkins-2.591, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream jenkinsci/jenkins release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.591 (reviewed 2026-11-17).






