2016-11-18 15:56:25 +00:00
|
|
|
# Test and deploy to Heroku a Scala application
|
2016-02-26 11:31:35 +00:00
|
|
|
|
2016-06-18 07:23:31 +00:00
|
|
|
This example demonstrates the integration of Gitlab CI with Scala
|
|
|
|
applications using SBT. Checkout the example
|
|
|
|
[project](https://gitlab.com/gitlab-examples/scala-sbt) and
|
|
|
|
[build status](https://gitlab.com/gitlab-examples/scala-sbt/builds).
|
2016-02-26 11:31:35 +00:00
|
|
|
|
2016-11-18 15:56:25 +00:00
|
|
|
## Add `.gitlab-ci.yml` file to project
|
2016-02-26 11:31:35 +00:00
|
|
|
|
2016-06-18 07:23:31 +00:00
|
|
|
The following `.gitlab-ci.yml` should be added in the root of your
|
|
|
|
repository to trigger CI:
|
2016-02-26 11:31:35 +00:00
|
|
|
|
2016-06-18 07:23:31 +00:00
|
|
|
``` yaml
|
2016-03-10 16:32:37 +00:00
|
|
|
image: java:8
|
|
|
|
|
2016-11-18 15:56:25 +00:00
|
|
|
stages:
|
|
|
|
- test
|
|
|
|
- deploy
|
|
|
|
|
2016-02-26 11:31:35 +00:00
|
|
|
before_script:
|
2016-06-18 07:23:31 +00:00
|
|
|
- apt-get update -y
|
|
|
|
- apt-get install apt-transport-https -y
|
2016-11-18 15:56:25 +00:00
|
|
|
## Install SBT
|
2016-02-26 11:31:35 +00:00
|
|
|
- echo "deb http://dl.bintray.com/sbt/debian /" | tee -a /etc/apt/sources.list.d/sbt.list
|
|
|
|
- apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 642AC823
|
|
|
|
- apt-get update -y
|
|
|
|
- apt-get install sbt -y
|
|
|
|
- sbt sbt-version
|
|
|
|
|
|
|
|
test:
|
2016-11-18 15:56:25 +00:00
|
|
|
stage: test
|
2016-02-26 11:31:35 +00:00
|
|
|
script:
|
|
|
|
- sbt clean coverage test coverageReport
|
2016-11-18 15:56:25 +00:00
|
|
|
|
|
|
|
deploy:
|
|
|
|
stage: deploy
|
|
|
|
script:
|
|
|
|
- apt-get update -yq
|
|
|
|
- apt-get install rubygems ruby-dev -y
|
|
|
|
- gem install dpl
|
|
|
|
- dpl --provider=heroku --app=gitlab-play-sample-app --api-key=$HEROKU_API_KEY
|
2016-02-26 11:31:35 +00:00
|
|
|
```
|
|
|
|
|
2016-06-18 07:23:31 +00:00
|
|
|
The `before_script` installs [SBT](http://www.scala-sbt.org/) and
|
|
|
|
displays the version that is being used. The `test` stage executes SBT
|
|
|
|
to compile and test the project.
|
|
|
|
[scoverage](https://github.com/scoverage/sbt-scoverage) is used as an SBT
|
|
|
|
plugin to measure test coverage.
|
2016-11-18 15:56:25 +00:00
|
|
|
The `deploy` stage automatically deploys the project to Heroku using dpl.
|
2016-02-26 11:31:35 +00:00
|
|
|
|
2016-06-18 07:23:31 +00:00
|
|
|
You can use other versions of Scala and SBT by defining them in
|
|
|
|
`build.sbt`.
|
2016-02-26 11:31:35 +00:00
|
|
|
|
2017-02-13 16:59:57 +00:00
|
|
|
## Display test coverage in job
|
2016-06-18 07:23:31 +00:00
|
|
|
|
|
|
|
Add the `Coverage was \[\d+.\d+\%\]` regular expression in the
|
2017-05-11 19:21:14 +00:00
|
|
|
**Settings ➔ Pipelines ➔ Coverage report** project setting to
|
2016-11-18 15:56:25 +00:00
|
|
|
retrieve the [test coverage] rate from the build trace and have it
|
2017-02-13 16:59:57 +00:00
|
|
|
displayed with your jobs.
|
2016-06-18 07:23:31 +00:00
|
|
|
|
2017-02-13 16:59:57 +00:00
|
|
|
**Pipelines** must be enabled for this option to appear.
|
2016-11-18 15:56:25 +00:00
|
|
|
|
|
|
|
## Heroku application
|
|
|
|
|
|
|
|
A Heroku application is required. You can create one through the
|
|
|
|
[Dashboard](https://dashboard.heroku.com/). Substitute `gitlab-play-sample-app`
|
|
|
|
in the `.gitlab-ci.yml` file with your application's name.
|
|
|
|
|
|
|
|
## Heroku API key
|
|
|
|
|
|
|
|
You can look up your Heroku API key in your
|
|
|
|
[account](https://dashboard.heroku.com/account). Add a secure [variable] with
|
|
|
|
this value in **Project ➔ Variables** with key `HEROKU_API_KEY`.
|
|
|
|
|
|
|
|
[variable]: ../variables/README.md#user-defined-variables-secure-variables
|
|
|
|
[test coverage]: ../../user/project/pipelines/settings.md#test-coverage-report-badge
|