-
Notifications
You must be signed in to change notification settings - Fork 60
Home
See the README.
Primarily the Scala team at Lightbend, with help from the maintainers of the included libraries.
as of October 2023, there are 250 repos in the 2.13 build.
The community builds run on Scala's Jenkins-based CI, as documented in the scala-jenkins-infra README.
Build results are viewable on scala-ci.typesafe.com. (For example, see the 2.13.x JDK 11 results.
Yes. Just comment on the PR and ask, and someone on the Scala team will manually trigger a run for you. (And if you often need to trigger such runs, you can ask us for access to trigger runs yourself.)
(How does it work?
As documented in the scala/scala README,
every PR results in a new Scala version being published to a special
resolver. The community build Jenkins is already set up to use that
resolver, so we only need to specify the version field in the
Jenkins job parameters.)
Sure, just clone the repo and ./run.
It takes a long time. But there are ways to speed it up, or run just a subset. See Local runs.
There are currently ten:
| branch name | JDK version | Jenkins job |
|---|---|---|
| 2.12.x | Temurin 8 | link |
| 2.12.x | Temurin 11 | link |
| 2.12.x | Temurin 17 | link |
| 2.12.x | Temurin 21 | link |
| 2.12.x | OpenJDK 22-ea | link |
| 2.13.x | Temurin 8 | link |
| 2.13.x | Temurin 11 | link |
| 2.13.x | Temurin 17 | link |
| 2.13.x | Temurin 21 | link |
| 2.13.x | OpenJDK 22-ea | link |
The 2.12.x build is very nearly frozen. It uses up-to-date Scala SHAs, but we are no longer adding new repos or doing any disruptive version upgrades. (We still advance a few of the project SHAs, but not if doing so requires substantial effort.)
The 2.13.x build is under somewhat more active development, but only somewhat. We will consider additions and/or version bumps on a case-by-case basis, considering the likely cost/benefit.
The report script has lists of projects that are known to fail on certain JDK versions only and thus don't prevent the Jenkins outcome from being green.
Further details on these variations is here.
See Eligibility.
In short, no. It is considered out of scope for the Lightbend team to attempt this.
Of course, many included projects support multiple back ends. That's okay; we just disable the non-JVM portions.
On the 2.13.x branch (usually), edit community.conf and projs.conf and add proj/foo.conf and submit a PR with the change. (The PR doesn't necessarily need to be fully baked; it can be a starting point for conversation and collaboration.)
The dbuild documentation might help.
See also Maintenance for a great deal of relevant practical advice.
See Maintenance.
Good starting places for new folks to ask general questions about this include:
- the Discussions tab in this repo
- the #scala-contributors channel on the Scala Discord
- https://contributors.scala-lang.org
And of course, we can also talk using issues and pull requests in this repo.