Try Maven Central before hitting repository.apache.org
#3816
+8
−0
Conversation
This file contains 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
We have noticed some builds causing many 404 errors on `repository.apache.org`, causing GitHub Actions runners to be banned (https://infra.apache.org/infra-ban.html). Looking at various logs, it looks like this workflow may be one of the jobs triggering this problem. Including Maven Central explicitly in the repositories section will make Maven check that repository first, which should help a lot.
adoroszlai
approved these changes
Dec 23, 2024
There was a problem hiding this comment.
[INFO] Downloading from apache-public-repository-group: https://repository.apache.org/content/groups/public/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloading from jenkins-releases: https://repo.jenkins-ci.org/releases/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloading from repo.jenkins-ci.org: https://repo.jenkins-ci.org/public/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloaded from repo.jenkins-ci.org: https://repo.jenkins-ci.org/public/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom (11 kB at 277 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.pom (11 kB at 39 kB/s)
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.
Description:
We have noticed some builds causing many 404 errors on
repository.apache.org, causing GitHub Actions runners to be banned (https://infra.apache.org/infra-ban.html).Looking at various logs, it looks like this workflow may be one of the jobs triggering this problem. Including Maven Central explicitly in the repositories section will make Maven check that repository first, which should help a lot.
Please make sure that your PR meets the following requirements:
Issue-XYZ Subject[0.9.x] Issue-XYZ SubjectHow to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.