On Monday, we replaced the "ceph-dev-new-trigger" Jenkins job which triggered package and container builds based on ceph-ci.git push events. The main purpose of the new job is to enable opt-in testing of a new build pipeline, called ceph-dev-pipeline. The new trigger job allows you to optionally use git trailers to signal to Jenkins which distros, flavors, etc. you want to build by adding parameters to the HEAD commit of your branch. ceph-dev-pipeline currently replaces the ceph-dev-new jobs; here is a list of some of the differences: - Package builds are done inside a container providing an isolated, sterile, portable build environment - Eliminates building the source tarball multiple times per branch - Can build multiple flavors concurrently - Uses sccache by default - Disables dwz by default - Uses a newer, faster sub-job to generate the source distribution by creating one compressed tarball instead of multiple To use the new pipeline, you can start by adding "CEPH-BUILD-JOB: ceph-dev-pipeline" above or below your "Signed-off-by:" line in the HEAD commit of your branch. For more information, see: https://github.com/ceph/ceph-build/blob/main/ceph-trigger-build/README.md. Omitting those git trailers will continue using the old non-containerized build jobs and will build the default distro/flavor/arch combinations. For now, this pipeline is opt-in only but we encourage you to try it and let us know of any bugs you encounter as it will eventually become the default for all builds.