Run your continuous integration, automated testing, and continuous delivery jobs at scale with Jenkins for DC/OS. Instead of the static partitions so typical of other Jenkins clusters, Jenkins for DC/OS can create and destroy agents as demand increases and decreases. With multiple Jenkins masters sharing a single pool of compute resources, you can achieve much more efficient and resilient automations.
Jenkins for DC/OS needs a directory on disk to store its configuration and build data. To get up and running quickly, you can pin it to a single agent and use this to store the data. However, should the agent go down, your data will be lost.
Before going into production, you should set up a single POSIX-compliant file system that each agent mounts using the same path. Some options include NFS, Ceph, HDFS, and iSCSI.
Jenkins for DC/OS Beta Release Notes
Discover the new features, updates, and known limitations in this release of the Jenkins for DC/OS Service…Read More
Configuration Options Matrix
Configuration changes in this release of the Jenkins Service…Read More
Jenkins for DC/OS Quickstart
Jenkins for DC/OS can be installed using either the web interface or the DC/OS CLI.…Read More
Provisioning Jenkins for DC/OS
This topic describes when and how to provision Jenkins with a service account.…Read More
Customizing your install
The Jenkins for DC/OS package accepts a range of custom configuration parameters at install.…Read More
Jenkins for DC/OS Service Architecture
The Jenkins for DC/OS service bundles the Jenkins Automation Server with the Jenkins Mesos Plug-in.…Read More
Jenkins for DC/OS can be uninstalled using either the web interface or the CLI.…Read More