Skip to content

Use SBT Release Plugin (https://github.com/sbt/sbt-release). #106

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

Merged
merged 1 commit into from
Feb 25, 2015

Conversation

gslowikowski
Copy link
Member

Next proposal related to #85

Use SBT Release Plugin (https://github.com/sbt/sbt-release) instead of manual release process.
To release next version of SCoverage just run "sbt release" (not "sbt +release"!!!).

…se next version of SCoverage just run "sbt release".
@gslowikowski
Copy link
Member Author

@sksamuel, if it's OK, you can use this plugin in sbt-scoverage module as well.

@Kwestor
Copy link
Contributor

Kwestor commented Feb 24, 2015

LGTM

@gslowikowski
Copy link
Member Author

SBT Release pipeline can be customized. I used this feature to test plugin usage on local git repo (without pushing) and without running unit tests (one fails now).
In case someone will find it useful I replaced:

  ) ++ ReleasePlugin.releaseSettings ++ Seq(
    ReleaseKeys.crossBuild := true,
    ReleaseKeys.publishArtifactsAction := PgpKeys.publishSigned.value
  )

with

    ReleaseKeys.releaseProcess := Seq[ReleaseStep](
      checkSnapshotDependencies,
      inquireVersions,
      //(one test fails) runTest,
      setReleaseVersion,
      commitReleaseVersion,
      tagRelease,
      publishArtifacts,
      setNextVersion,
      commitNextVersion //,
      //(I have not defined a tracking branch) pushChanges
    )

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

Successfully merging this pull request may close these issues.

3 participants