CDRIVER-5814 Use less Artifactory for Earthly images #1927
Merged
Conversation
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
eramongodb
approved these changes
Mar 18, 2025
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.
Follow-up to #1794
Use of Artifactory is likely the cause of frequently encountered HTTP errors (example). Quoting slack:
Using Artifactory is not needed. Quoting DEVPROD-12970:
Unqualified images names (e.g.
ubuntu:22.04) are used rather than a qualified image name (e.g.docker.io/library/ubuntu:22.10). This may help enable using a different registry for CI and local development. DEVPROD-15649 proposes AWS ECR.Artifactory is still used for the
sign-fileandsilkbombtargets.