Skip to content

Commit

Permalink
Release from travis (#202)
Browse files Browse the repository at this point in the history
* Add publishing stage

* Document that tagging the release should take care of things
  • Loading branch information
raboof authored Oct 1, 2019
1 parent 7c0029c commit dd59198
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 4 deletions.
15 changes: 12 additions & 3 deletions .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,18 @@ env:
before_install: curl -Ls https://git.io/jabba | bash && . ~/.jabba/jabba.sh
install: jabba install "$TRAVIS_JDK" && jabba use "$_" && java -Xmx32m -version

script:
# Increasing ReservedCodeCacheSize minimizes scala compiler-interface compile times
- sbt -J-XX:ReservedCodeCacheSize=256M ++$SCALA_VERSION test
stages:
- name: test
- name: release
if: tag =~ ^v AND NOT fork

jobs:
include:
- stage: test
# Increasing ReservedCodeCacheSize minimizes scala compiler-interface compile times
script: sbt -J-XX:ReservedCodeCacheSize=256M ++$SCALA_VERSION test
- stage: release
script: echo $PGP_SECRET | base64 --decode | gpg --import && sbt +publishSigned

before_cache:
- find $HOME/.sbt -name "*.lock" | xargs rm
Expand Down
2 changes: 1 addition & 1 deletion RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
* the next tag version (e.g. `v0.11`)
* title and release description including notable changes
* link to the [milestone](https://github.com/lightbend/genjavadoc/milestones) showing an overview of closed issues for this release
2. Checkout the newly created tag and publish the release by running `sbt +publishSigned`. You will have to have Sonatype OSS repository rights to publish under `com.typesafe` organisation.
2. This should push the release to sonatype from travis
3. Login to [Sonatype](https://oss.sonatype.org/) to close and release the repository.

## Back-releasing for a new Scala version
Expand Down

0 comments on commit dd59198

Please sign in to comment.