From: David Galloway Date: Mon, 15 Jun 2026 21:29:22 +0000 (-0400) Subject: doc: Document restarting failed release builds X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=937ffe0d03efa135cf08d3a4f90f07dacf3449ca;p=ceph.git doc: Document restarting failed release builds Signed-off-by: David Galloway --- diff --git a/doc/dev/release-process.rst b/doc/dev/release-process.rst index 7a5781b0e996..6bb5c2c5f5f2 100644 --- a/doc/dev/release-process.rst +++ b/doc/dev/release-process.rst @@ -87,7 +87,7 @@ Once QE has determined a stopping point in the working (e.g., ``squid``) branch, Notify the "Build Lead" that the release branch is ready. -2. Starting the build +2a. Starting the build ===================== We'll use a stable/regular 19.2.2 release of Squid as an example throughout this document. @@ -123,6 +123,37 @@ NOTE: if for some reason the build has to be restarted (for example if one distr 5. Click ``Build``. +2b. What to do if your build fails +================================== + +The ceph-release-pipeline parent job has three stages. + +If your build fails during the "create ceph release tag" stage, troubleshoot the child ceph-tag job and re-run the parent ceph-release-pipeline job with the same parameters. + +---- + +If your build fails during the "package build" stage, troubleshoot the child ceph-dev-pipeline job. If only one variant failed to build (e.g., centos9 arm64), start a new ceph-release-pipeline job specifying:: + + DISTROS=centos9 + ARCHS=arm64 + TAG=false <-- VERY IMPORTANT + +This will leave the version commit and previously-created tag intact in ceph-releases.git. You will want the subsequent ceph-dev-pipeline job to reuse that SHA/tag. + +Once all of your variants are successfully built, you will have to manually run the ceph-tag job. For example,:: + + BRANCH=tentacle + TAG=true + TAG_PHASE=push + VERSION=20.2.0 + RELEASE_TYPE=STABLE + +Then proceed with the normal release process. + +---- + +If your build fails during the "push ceph release tag" stage, troubleshoot the child ceph-tag job and re-run **just** the ceph-tag job again manually. Do not re-run ceph-release-pipeline. + 3. Release Notes ================