Skip to content
Seth Tisue edited this page Nov 30, 2016 · 23 revisions

Local runs

Should I run it locally?

If you're a library author, yes.

If you're maintaining the community build as a whole, go the Jenkins route first and get familiar with that as it's usually more practical. You can decide later whether to supplement Jenkins with local runs.

How do I run it locally?

You might want to set JAVA_HOME first. The 2.11.x community build assumes Java 6; the others, Java 8.

Then do:

./run.sh

That's it. It will take hours, so while you wait, make yourself a sandwich. (Even better, make yourself a sandwich-making machine.)

You're also free to specify the nightly Scala you want, e.g.:

version=2.12.1-933bab2-nightly ./run.sh

but you don't have to. If you don't, the last successful nightly will be used.

You can build just a subset if you want:

./run.sh scalatest,scalacheck,specs2,utest

This will build only the listed projects and their dependencies. (In the Jenkins GUI, use the projects setting for this.)

Clone this wiki locally