Ensure whitesource reports for stable versions (akka#634)

MannyCalavera92 · Dec 11, 2017 · 4bd1fc4 · 4bd1fc4
2 parents c646578 + 7d9db28
commit 4bd1fc4
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/.travis.yml b/.travis.yml
@@ -45,6 +45,7 @@ deploy:
   provider: script
   skip_cleanup: true
   script:
+    - sbt 'set credentials += Credentials("whitesource", "whitesourcesoftware.com", "", System.getenv("WHITESOURCE_KEY"))' whitesourceCheckPolicies whitesourceUpdate
     - sbt -J-XX:ReservedCodeCacheSize=128m ++$TRAVIS_SCALA_VERSION publish && curl -I https://ci.lightbend.com/job/techhub-publisher/build?token=$TECH_HUB_TOKEN
   on:
     tags: true

diff --git a/RELEASING.md b/RELEASING.md
@@ -1,5 +1,6 @@
 ## Releasing
 
+1. Ask someone in the Akka team to rename the 'alpakka-xx-stable' report in [WhiteSource](https://saas.whitesourcesoftware.com) to reflect the latest version (unfortunately this requires permissions that cannot be shared in a granular way)
 1. Check [closed issues without a milestone](https://github.com/akka/alpakka/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20no%3Amilestone) and either assign them the 'upcoming' release milestone or 'invalid'
 1. Create a [new release](https://github.com/akka/alpakka/releases/new) with:
     * the next tag version (e.g. `v0.3`)