[#incident-53970] Backport image replication workaround to 7.78.x#50420
Draft
AliDatadog wants to merge 1 commit into7.78.xfrom
Draft
[#incident-53970] Backport image replication workaround to 7.78.x#50420AliDatadog wants to merge 1 commit into7.78.xfrom
AliDatadog wants to merge 1 commit into7.78.xfrom
Conversation
Contributor
Gitlab CI Configuration ChangesChanges Summary
ℹ️ Diff available in the job log. |
Contributor
Files inventory check summaryFile checks results against ancestor 6e93cda2: Results for datadog-agent_7.78.3~rc.2.git.2.ad56b95.pipeline.111713397-1_amd64.deb:No change detected |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Backport the image replication target workaround from #50409 to
7.78.x.7.78.xdoes not include the earlier prerequisite from #50378, so this applies the final behavior directly:DataDog/images@masterRELEASE_STAGING=trueand clearRELEASE_PRODonly for non-tag/custom buildsWhy
This limits custom branch image replication while JIT replication is not reliable enough for these images.
Validation
git diff --check -- .gitlab/deploy/internal_image_deploy/internal_image_deploy.ymlruby -e 'require "yaml"; YAML.load_file(".gitlab/deploy/internal_image_deploy/internal_image_deploy.yml"); puts "yaml ok"'