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

Perform a dry run #254

Open
erwan opened this issue Sep 20, 2019 · 3 comments
Open

Perform a dry run #254

erwan opened this issue Sep 20, 2019 · 3 comments

Comments

@erwan
Copy link

erwan commented Sep 20, 2019

Many times I published a version, only to find out there is something wrong with it (typically cross-publishing not doing what I was expected).

When that happen I have to keep publishing until it does what I want, and I end up burning version numbers with bad versions.

Maybe sbt-release could provide a way to do a "dry run" so we see what artifacts would be published, but without any impact on the source repository or the artifact repository?

@pleszczy
Copy link

That's a badly needed feature 👍

@dan-ilin
Copy link

dan-ilin commented Apr 27, 2023

As a workaround until this is implemented, you can specify the releaseProcess in build.sbt and leave out the publishArtifacts step.

@sjdurfey
Copy link

I've been setting these to publish locally to test out my changes:

publishTo := Some(Resolver.file("local-maven", file(Path.userHome.absolutePath + "/.m2/repository")))
releaseProcess := Seq[ReleaseStep](
  checkSnapshotDependencies, 
  inquireVersions,                    
  runClean,                               
  setReleaseVersion,                    
  publishArtifacts,                       
)

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

4 participants