Local runs

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. You must use Java 8. (Perhaps Java 9 works, we haven't tried it yet.)

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-bin-933bab2 ./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.)

Can I use a locally built Scala?

Yes, version= works with any Scala version dbuild can resolve.

After publishLocal in scala/scala you'll see e.g.

published ivy to /Users/tisue/.ivy2/local/org.scala-lang/scala-compiler/2.12.5-bin-SNAPSHOT/ivys/ivy.xml

So then you can:

version=2.12.5-bin-SNAPSHOT ./run.sh

This works because configs/resolvers.conf includes local.