score:31

Accepted answer

Scala 2.12 or 2.13

quick version (sbt)

Global / resolvers += "scala-integration" at
  "https://scala-ci.typesafe.com/artifactory/scala-integration/"
scalaVersion := "2.13.9-bin-abcd123"

for a 2.12 nightly, substitute e.g. 2.12.17 for 2.13.9; in either case, it's the version number of the next release on that branch

for abcd123, manually substitute the first 7 characters of the SHA of the latest green build on the 2.13.x or 2.12.x branch on Travis-CI.

A quick way to find out the full version number of a current nightly is to use scala-cli, as follows.

quick version (scala-cli)

on scala-cli 0.1.3 or newer, you can run nightlies with:

scala-cli repl -S 2.12.nightly
scala-cli repl -S 2.13.nightly
scala-cli repl -S 2.nightly     # same as 2.13.nightly
# Scala 3, too!
scala-cli repl -S 3.0.nightly
scala-cli repl -S 3.1.nightly
scala-cli repl -S 3.2.nightly
scala-cli repl -S 3.nightly     # same as 3.2.nightly at present

Of course, not only repl works but also all the other scala-cli subcommands such as compile and run. It also works with //> directives in your script itself, for example:

//> using scala "3.nightly"

longer explanation

The Scala team no longer publishes -SNAPSHOT versions of Scala. (Starting that again could be a community contribution; see this ticket.)

But the team does publish nightly builds, each with its own fixed version number. The version number of a nightly looks like e.g. 2.13.1-bin-abcd123. (-bin- signals binary compatibility to sbt; all 2.13.x releases since 2.13.0 are binary compatible with each other.)

The old Jenkins-based answer that used to be here no longer works, since we (in 2018) moved publishing of nightlies off Jenkins and onto Travis-CI.

To tell sbt to use one of these nightlies, you need to do three things.

First, add the resolver where the nightlies are kept:

Global / resolvers += "scala-integration" at
  "https://scala-ci.typesafe.com/artifactory/scala-integration/"

Second, specify the Scala version:

scalaVersion := "2.13.1-bin-abcd123"

But that isn't a real version number. Manually substitute a version number containing the 7-character SHA of the last commit in the scala/scala repository for which a nightly build was published. Look at https://travis-ci.org/scala/scala/branches and you'll see the SHA in the upper right corner of the 2.13.x (or 2.12.x) section. For example:

enter image description here

As soon as 2.13.1 is released, the version number in the nightly will bump to 2.13.2, and so on.

If you have a multiproject build, be sure you set these settings across all projects when you modify your build definition. Or, you may set them temporarily in the sbt shell with ++2.13.1-bin-abcd123 (sbt 0.13.x) or ++2.13.1-bin-abcd123! (sbt 1.x; the added exclamation point is necessary to force a version not included in crossScalaVersions to be used).

Ideally, we would suggest an automated way to ask Travis-CI for the right SHA. This is presumably possible via Travis-CI's API, but (to my knowledge) nobody has looked into it yet. (Is there a volunteer?)

Note that we call these “nightly” builds informally, but technically it's a misnomer. A so-called “nightly” is built for every merged PR.

Scala 2.11

No further 2.11.x releases are planned, so we (the Scala team at Lightbend) aren't publishing 2.11 nightlies anymore, either.


Related Query

More Query from same tag