-
Notifications
You must be signed in to change notification settings - Fork 3k
Publish SNAPSHOTs to JBoss Nexus #51337
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
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
|
@gsmet any chance to have this merged before the Snapshot deployment job kicks in? |
|
I have no idea what JBoss Nexus is, so I'll defer to @gsmet on this |
rsvoboda
left a comment
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.
https://github.com/quarkusio/quarkus/blob/main/CONTRIBUTING.md#using-snapshots needs to be updated too
|
Given our history with JBoss Nexus, I'm not really excited about that. Let's try to push on the Sonatype front but I need to understand exactly what's going on. |
|
Snapshots deploy fails with Could not transfer metadata io.quarkus:quarkus-rest-qute:999-SNAPSHOT/maven-metadata.xml from/to quarkus-publish (https://central.sonatype.com/repository/maven-snapshots/): status code: 429, reason phrase: Too Many Requests (429) @gsmet Does the release process is using different strategy than snapshots push? It seems https://github.com/quarkusio/quarkus-release doesn't have any issues. Or maybe it's beacause the release is done in several step / over longer period of time? |
|
AFAIR Non-snapshot deployments use a different strategy: it uploads a single ZIP file so it doesn't face this issue |
99e7b56 to
70a641a
Compare
This should avoid rate limits imposed by Sonatype
70a641a to
36f00f5
Compare
This should avoid rate limits imposed by Sonatype