Skip to content
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

sbt-sonatype race condition between guardrail-maven-plugin #31

Open
blast-hardcheese opened this issue Nov 3, 2019 · 2 comments

Comments

@blast-hardcheese
Copy link
Collaborator

@blast-hardcheese blast-hardcheese commented Nov 3, 2019

The way sbt-sonatype works currently is publishSigned doesn't maintain which staging repository it just published to.

As a result, if the maven plugin is published at the same time, sbt-guardrail sonatype release fails because sonatypeClose and sonatypeRelease get confused as it doesn't know which one to use.

@blast-hardcheese

This comment has been minimized.

Copy link
Collaborator Author

@blast-hardcheese blast-hardcheese commented Nov 3, 2019

Meant to open against guardrail repo

@blast-hardcheese

This comment has been minimized.

Copy link
Collaborator Author

@blast-hardcheese blast-hardcheese commented Nov 3, 2019

whoops, no I didn't. Misread the title, there's another issue I meant to open against main guardrail repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.