In 2019, ASF and CloudBees reached an agreement to allow the Foundation to use CloudBees Core to have a farm of managed Jenkins masters. This allows the ASF to give larger projects their own dedicated Jenkins master, which can be custom configured for the project. They can readily manage this farm of Jenkins masters centrally, including push updates to all masters and their plugins. Naturally, this also reduces contention, as well as providing increased security for project-level credentials. CouchDB is the first project to use this setup, via https://ci-couchdb.apache.org/ (aka https://jenkins-cm1.apache.org/)
Only members of the ASF LDAP group couchdb-pmc
have write access to the Jenkins CI server, and all jobs are set to not trust changes to the Jenkinsfile from forked repos (see below).
Further, IBM is sponsoring CouchDB with cloud-based worker nodes, for the project's exclusive use. Combined with the FreeBSD and OSX nodes the project already had, this will provide the necessary compute resources to meet the needs of the project for some time to come.
All jobs on the new Jenkins master are contained in a CouchDB folder. Credentials for the project are placed within this folder; this is a unique capability of CloudBees Core at this time.
To implement build-a-PR functionality in the same way that Travis performs builds, Jenkins offers the Multibranch Pipeline job. Here‘s how it’s configured for CouchDB through the GUI:
user:email
and repo:status
.build-aux/Jenkinsfile.pr
[1]: https://issues.jenkins-ci.org/browse/JENKINS-44598 explains why we have the build set to Clean Before Checkout every time, and why clones are not shallow.
[2]: https://issues.apache.org/jira/browse/INFRA-17449 explains why “Discover pull requests from forks/Trust” has been set to “Nobody.”
main
and release branchesOur original Jenkins job (formerly /Jenkinsfile
) is now build-aux/Jenkinsfile.full
. This builds CouchDB on main
, all of our release branches (2.*
, 3.*
, etc.) as well as any branch prefixed with jenkins-
for testing on a wide variety of supported operating systems.
Settings are as follows:
user:email
and repo:status
.build-aux/Jenkinsfile.pull
The apache/couchdb-ci repo contains the dockerfiles that we use to generate the container images used for our container-based builds. These images are hosted on Docker Hub in the following repos:
The apache/couchdb-pkg repo contains a set of helper scripts to build binary packages for Debian / CentOS / Ubuntu from the contents of a release tarball. The packaging stage of our “Full Platform Builds” pipeline clones this repo to produces the package artifacts.