search

jvican / sbt-release-early

Opinionated sbt plugin to release your artifacts early, both on merge and via git tag.
Mozilla Public License 2.0
91 stars 9 forks source link

Cannot release artifacts of multiple Scala versions to Sonatype when running in Travis CI #32

Closed Atry closed 4 years ago

Atry commented 5 years ago

I have a Scala library that crosses multiple Scala versions, and I want to release early to Sonatype in Travis CI. Therefore I have the following configuration in .travis.yml:

scala:
  - 2.11.12
  - 2.12.8
  - 2.13.0-M4

Travis CI started three containers for the three different Scala versions. When sbt releaseEarly is executed, each container created a staging repository, and run sonatypeRelease command after artifacts are published to the staging repository.

Unfortunately, since there are three staging repositories in total, sonatypeRelease reports an error message as following:

[error] Multiple repositories are found:
[error] [comthoughtworksdsl-1037] status:open, profile:com.thoughtworks.dsl(bb5bd533a8c47) description: Implicitly created (auto staging).
[error] [comthoughtworksdsl-1038] status:open, profile:com.thoughtworks.dsl(bb5bd533a8c47) description: Implicitly created (auto staging).
[error] [comthoughtworksdsl-1039] status:open, profile:com.thoughtworks.dsl(bb5bd533a8c47) description: Implicitly created (auto staging).

The full CI log can be found at https://travis-ci.org/ThoughtWorksInc/Dsl.scala/builds/506086649

JanBessai commented 4 years ago

Not sure, if this is fixed now. Otherwise you can try to do

sbt +releaseEarly sonatypeBundleRelease

with cross scala versions set in sbt instead of maven. Here is an example, where I got things working: https://github.com/combinators/shapeless-feat

jvican commented 4 years ago

Yes, this should be fixed now, I'm closing