Use sbt-sonatype bundle release to speed up publishing #59
Conversation
|
hell |
tpolecat
force-pushed
the
bundle-publish
branch
from
8a10f3a
to
1725b04
Compare
| @@ -89,7 +89,7 @@ object CiReleasePlugin extends AutoPlugin { | |||
| } else { | |||
| println("Tag push detected, publishing a stable release") | |||
| sys.env.getOrElse("CI_RELEASE", "+publishSigned") :: | |||
There was a problem hiding this comment.
Could this be necessary as well? I can't tell from the sbt-sonatype readme, but my intuition is that the speedups are gained from not running publishSigned (which is usually bottleneck).
| sys.env.getOrElse("CI_RELEASE", "+publishSigned") :: | |
| sys.env.getOrElse("CI_RELEASE", "+publishLocalSigned") :: |
There was a problem hiding this comment.
My reading was that publishSigned goes into an archive thing locally if you set publishTo := sonatypePublishToBundle.value and then it's all shipped atomically when you do sonatypeBundleRelease. Maybe @xerial can clarify?
There was a problem hiding this comment.
Thank makes sense, let's give it a try and see it how fares!
There was a problem hiding this comment.
Looks like it failed with
[error] java.io.IOException: Supplied file /home/travis/build/olafurpg/sbt-ci-release/target/sonatype-staging/sbt-ci-release-1.3.0 is a not an existing directory!
The local directory was
info] published sbt-ci-release to /home/travis/build/olafurpg/sbt-ci-release/target/sonatype-staging/plugin-1.3.0/com/geirsson/sbt-ci-release_2.12_1.0/1.3.0/sbt-ci-release-1.3.0-javadoc.jar.asc
It looks like sonatypePublishToBundle is using the project's id and sonatypeBundleRelease is using the moduleName 🤔
There was a problem hiding this comment.
There was a problem hiding this comment.
With publishTo := sonatypePublishToBundle.value setting, publishSigned task will create a local staging folder.
It's a bit confusing, but publishLocalSigned task is for storing artifacts into ~/.ivy2/ folder.
olafurpg
changed the title
| @@ -89,7 +89,7 @@ object CiReleasePlugin extends AutoPlugin { | |||
| } else { | |||
| println("Tag push detected, publishing a stable release") | |||
| sys.env.getOrElse("CI_RELEASE", "+publishSigned") :: | |||
There was a problem hiding this comment.
Thank makes sense, let's give it a try and see it how fares!
|
There's a new version already. Investigating. |
This resolves #58 in principle but despite changing the sbt-sonatype version to 3.4
libraryDependenciesstill shows 2.6 and thesonatypePublishToBundlekey is not found. I am completely baffled. Any ideas?Also unclear how to test this.