Compiling and testing
sbt projects on hosted CI platfroms like Travis and Gitlab CI is dominated by downloading
the required dependencies from Maven Central.
Oftentimes you have four to five minutes of downloading and less than one minute of compiling and testing.
Some offer a feature which is supposed to speed up these always-the-same download tasks by caching the dependencies in an S3 bucket.
Caching dependencies for Scala in Travis is relatively straight forward however I couldn’t find an example to do this for Gitlab CI. After a bit of trial and error I figured it out.
Here is the
# some parts originally from https://github.com/randm-ch/units-of-information/blob/master/.gitlab-ci.yml image: "hseeberger/scala-sbt:8u141-jdk_2.12.3_1.0.2" variables: SBT_OPTS: "-Dsbt.global.base=sbt-cache/sbtboot -Dsbt.boot.directory=sbt-cache/boot -Dsbt.ivy.home=sbt-cache/ivy" COURSIER_CACHE: sbt-cache/coursier #only needed if you use coursier cache: # if you want to have a separate cache per branch, uncomment the next line # key: "$CI_BUILD_REF_NAME" untracked: true paths: - "sbt-cache/ivy/cache" - "sbt-cache/boot" - "sbt-cache/sbtboot" - "sbt-cache/target" - "sbt-cache/coursier" #only needed if you use coursier stages: - test test: script: - sbt test
Sometimes it takes a few times for it to actually work so just commit it and try it more than once.
Edit 2017-09-20: I updated the directories and the base image slightly.