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

Cross-publish stages each Scala-version to a separate staging repository #78

Closed
ThijsBroersen opened this issue Dec 17, 2018 · 3 comments

Comments

@ThijsBroersen
Copy link

When I cross-publish with '+publishSigned' the results are staged in multiple staging repositories (one for each Scala-version). Sometimes it is staged in a single repository. This seems ambiguous.
If I run 'sonatypeRelease' it fails when multi-repositories are found, but putting 'sonatypeReleaseAll' in my travis-build is not desired as there can be staging repositories (other builds, other projects).

I looked in the source code and tried some manual testing. It looks like 'sonatypeStagingRepositoryProfile' keeps a reference to a staging-repository. Is it possible to keep multiple references and have 'sonatypeRelease' promote and close this list of staging-repositories?

@xerial
Copy link
Owner

xerial commented Dec 18, 2018

I guess #77 is related.

@ThijsBroersen
Copy link
Author

ThijsBroersen commented Dec 18, 2018

I guess #77 is related.

Not sure, but I apologize I forgot to mention similar issues. E.g. #66 #73 and #49 where is reported about multiple parallel publishSigned commands somtimes publish to the same repository.

@xerial
Copy link
Owner

xerial commented Sep 5, 2019

@ThijsBroersen I've redesigned the release flow. By using the flow described here https://github.com/xerial/sbt-sonatype#multi-module-projects, it should be possible to use the same staging repository to publish.

This feature is added since sbt-sonatype 3.0

@xerial xerial closed this as completed Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants