Impact of the new feature
This affects repository maintenance and release operations for dbs2go.
No direct runtime impact is expected for external clients such as CRAB3, WMCore, WMAgent, or DBSUploader. The affected area is the repository release procedure: image build and image upload/publication after an intentional tag creation.
Is your feature request related to a problem? Please describe.
Yes.
Following the resolution of #152, automated CI/CD execution in this repository should be reduced or disabled where it performs privileged release operations.
The current GitHub Actions workflows still describe automated actions such as:
- tag-triggered build/release flow;
- stable vs release-candidate detection;
- Go setup and build;
- GitHub release/prerelease creation;
- binary upload to the GitHub release;
- Docker image build using CMSKubernetes docker assets;
- registry.cern.ch login;
- image publication to
registry.cern.ch/cmsweb/dbs2go;
- imagebot-based deployment update.
The current Makefile already provides manual targets for build, release script invocation, vet, platform builds, tests, and test groups. However, the release/image publication operations currently described in GitHub Actions are not fully available as explicit manual Make targets.
Describe the solution you'd like
Add explicit Make targets for the release operations currently automated in GitHub Actions and then disable the corresponding automated CI/CD pipelines.
The required manual flow should be limited to:
- maintainer intentionally creates a release tag;
- maintainer runs a Make target to build the image for that tag;
- maintainer runs a Make target to upload/publish the image.
The Makefile should provide clear manual targets for at least:
- image build for a selected tag;
- image upload/publication to
registry.cern.ch/cmsweb/dbs2go;
- any required preparation of CMSKubernetes docker assets.
This issue is not about refactoring GitHub Actions into thin wrappers around Make targets. That may be considered later. The goal here is to make the privileged release operations manually executable and to stop relying on automatically triggered CI/CD pipelines for them.
Describe alternatives you've considered
Keeping the current GitHub Actions release automation is not preferred after the Megalodon CI incident and the cleanup handled in #152.
A later refactoring could make GitHub Actions call Make targets as wrappers, but that is explicitly outside the scope of this issue.
Additional context
Related cleanup issue:
#152
The intended outcome is to remove automatic CI/CD execution for privileged release operations from this repository and replace it with explicit, maintainer-driven Make targets.
The minimal required release procedure is:
create tag intentionally
make <image-build-target>
make <image-upload-target>
This keeps release operations auditable, explicit, and locally controlled.
Impact of the new feature
This affects repository maintenance and release operations for
dbs2go.No direct runtime impact is expected for external clients such as CRAB3, WMCore, WMAgent, or DBSUploader. The affected area is the repository release procedure: image build and image upload/publication after an intentional tag creation.
Is your feature request related to a problem? Please describe.
Yes.
Following the resolution of #152, automated CI/CD execution in this repository should be reduced or disabled where it performs privileged release operations.
The current GitHub Actions workflows still describe automated actions such as:
registry.cern.ch/cmsweb/dbs2go;The current
Makefilealready provides manual targets for build, release script invocation, vet, platform builds, tests, and test groups. However, the release/image publication operations currently described in GitHub Actions are not fully available as explicit manual Make targets.Describe the solution you'd like
Add explicit Make targets for the release operations currently automated in GitHub Actions and then disable the corresponding automated CI/CD pipelines.
The required manual flow should be limited to:
The Makefile should provide clear manual targets for at least:
registry.cern.ch/cmsweb/dbs2go;This issue is not about refactoring GitHub Actions into thin wrappers around Make targets. That may be considered later. The goal here is to make the privileged release operations manually executable and to stop relying on automatically triggered CI/CD pipelines for them.
Describe alternatives you've considered
Keeping the current GitHub Actions release automation is not preferred after the Megalodon CI incident and the cleanup handled in #152.
A later refactoring could make GitHub Actions call Make targets as wrappers, but that is explicitly outside the scope of this issue.
Additional context
Related cleanup issue:
#152
The intended outcome is to remove automatic CI/CD execution for privileged release operations from this repository and replace it with explicit, maintainer-driven Make targets.
The minimal required release procedure is:
This keeps release operations auditable, explicit, and locally controlled.