-
Notifications
You must be signed in to change notification settings - Fork 76
Setup releases from CI #58
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
Conversation
Upgrades the build to sbt 1.2 so that we can use sbt-ci-relase to automate releases from Travis CI.
6ad2542
to
767c1a2
Compare
project/build.properties
Outdated
@@ -1 +1 @@ | |||
sbt.version=0.13.17 | |||
sbt.version=1.2.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lihaoyi can we scrap JDK 7 support? Upgrading the build to use 2.12 results in errors on JDK 7
java.lang.UnsupportedClassVersionError: scala/Option : Unsupported major.minor version 52.0
|
||
# Release stable release on tag push and snapshot on merge to master | ||
- stage: release | ||
script: sbt ci-release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lihaoyi are you OK if I configure publishing credential in the Travis UI to publish releases on tag push?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went ahead and included the credentials as secret environment variables in the Travis web UI settings. Please let me know if we should revert. I generated a fresh gpg key only to publish sourcecode.
e2e50e9
to
ed3fbc4
Compare
Upgrades the build to sbt 1.2 so that we can use sbt-ci-relase to
automate releases from Travis CI.