Publish images via dd-pkg publish-image instead of public-images trigger - #1323
Publish images via dd-pkg publish-image instead of public-images trigger#1323AliDatadog wants to merge 2 commits into
Conversation
…images trigger Replaces the legacy trigger: project: DataDog/public-images job with the shared .dd-pkg-publish template used by other BARX-1757 migrations, calling dd-pkg publish-image directly against artifact-gateway. Same IMG_SOURCES/IMG_DESTINATIONS/IMG_REGISTRIES per image flavor, unchanged.
|
There was a problem hiding this comment.
Pull request overview
This PR migrates the image publishing step in the generated GitLab pipeline away from the legacy downstream DataDog/public-images trigger to a direct dd-pkg publish-image invocation (via a shared .dd-pkg-publish template), aligning this repository with the BARX-1757 migration approach.
Changes:
- Introduces a reusable
.dd-pkg-publishjob template that runsdd-pkg publish-imagewith configurable registries/sources/destinations. - Updates the per-flavor
publish image (...)job toextends: .dd-pkg-publishand removes the downstream pipeline trigger. - Keeps the per-flavor image source/destination/registry variables as-is while moving signing defaults into the shared template.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Problem
This repo's image publish jobs trigger the legacy
public-imagesGitLab project as a downstream pipeline. BARX-1757 is migrating all such triggers onto a directdd-pkg publish-imagecall against artifact-gateway.Change
Replaces
trigger: project: DataDog/public-imageswith the shared.dd-pkg-publishtemplate used by the other repos in this migration wave, callingdd-pkg publish-imagedirectly.IMG_SOURCES/IMG_DESTINATIONS/IMG_REGISTRIESper image flavor are unchanged.Part of BARX-1962 / BARX-1757.