Continuous deployment for Scala

June 07, 2014

Here we outline the steps to take to enable continuous deployment for Scala Web projects that are based on xsbt-web-plugin.

This builds on continuous integration for scala, adding automated .war file deployment to Heroku.


First, create a new Heroku app. In the steps below, we'll call the app scala-sd.

Scala Web project


name := "scala-cd"

Continuous integration

Follow steps outlined in continuous integration for scala.

Automate deployment to Heroku

Heroku supports deployment of .war files to Heroku using the Heroku Toolbelt and its heroku-deploy plugin. We can use this from sbt with the sbt-heroku-deploy plugin.


addSbtPlugin("com.earldouglas" % "sbt-heroku-deploy" % "0.1.0")


enablePlugins(JettyPlugin, HerokuDeploy)

herokuAppName := "scala-cd"

Next, we need to provide Travis CI with our Heroku deployment credentials, so let's encrypt them and add them to .travis.yml. See the related Travis CI docs for more information.

Run the following from your project directory:

travis encrypt HEROKU_API_KEY=`heroku auth:token` --add

This adds an encrypted version of your Heroku API Key to .travis.yml:

    secure: [a long, ecnrypted string]

Finally, we configure Travis CI to run the deployment task for successful builds. Remove the old script line from .travis.yml, and replace it with the following.


- sbt coveralls package
  if ([ "$TRAVIS_BRANCH" == "master" ] || [ ! -z "$TRAVIS_TAG" ]) &&
      [ "$TRAVIS_PULL_REQUEST" == "false" ]; then
    sbt herokuDeploy;

Now when we push changs to GitHub, Travis CI picks them up, and runs a build via sbt coveralls package. If the changes were pushed to the master branch, Travis CI pushes the packaged .war file to Heroku.