-
Notifications
You must be signed in to change notification settings - Fork 353
Configuration to use Depot on GitLab Ci to avoid rate limiting with Maven Central. #12222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
AlexeyKuznetsov-DD
wants to merge
3
commits into
master
from
alexeyk/use-depot-to-avoid-rate-limiting
+3
−2
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
e3069e7
Configuration to use Depot on GitLab Ci to avoid rate limiting with M…
AlexeyKuznetsov-DD 2e952f6
Merge branch 'master' into alexeyk/use-depot-to-avoid-rate-limiting
AlexeyKuznetsov-DD 357e8a8
Merge branch 'master' into alexeyk/use-depot-to-avoid-rate-limiting
AlexeyKuznetsov-DD File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI or external builds that export an unset optional proxy variable as an empty string can fail all general dependency resolution before tests run.
Assertion details
MAVEN_REPOSITORY_PROXYorORG_GRADLE_PROJECT_mavenRepositoryProxyis present but empty or whitespace-only, such as when shell setup exports an undefined variable.Normalize both proxy values before repository selection and treat blank or whitespace-only values as absent, retaining Maven Central. This requires coordinated changes in both changed files and coverage for blank environment/property values, so no single inline suggestion is complete.MAVEN_REPOSITORY_PROXYnow produces only an empty proxy repository, while a present-but-empty Gradle property suppressesmavenCentral(); clean dependency resolution therefore has no usable general repository. Existing tests cover non-empty fixture proxies but not blank default-repository selection.Was this helpful? React 👍 or 👎
🤖 Datadog Autotest · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest