What is this? Why?
see the README
Who maintains this?
Primarily the Scala team at Lightbend, with help from:
- the maintainers of the included libraries (you?)
- the dbuild maintainers
- others at Lightbend and the Scala Center
See the repo commit log to see who specifically has been most active recently.
What projects are included?
as of August 2019, there are 199 repos in the config file
Where does this run?
The community builds run on Scala's Jenkins-based CI, as documented in the scala-jenkins-infra README.
Can I run it against a pull request in scala/scala?
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 to grant you the needed Jenkins 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.)
Can I run it locally?
Sure, just clone the repo and
It takes a long time. For more details, see Local runs.
What variations of the build exist?
There are currently six:
|branch name||JDK version||Jenkins job|
In general, most changes happen on the 2.12.x branch, which is expected to be entirely green. From there, changes are merged backwards to 2.11.x and forward to 2.13.x.
Further details on these variations is here.
Is my project eligible?
Is Scala.js or Scala Native supported?
Sorry, not yet. We do build Scala.js itself and run its tests, but we cannot (yet?) build Scala.js or Scala Native projects.
Of course, many included projects support multiple back ends. That's okay; we just disable the non-JVM portions.
How do I add my project?
2.12.x branch (usually), edit
community.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.
How do I help maintain the community build?
Where I can talk to someone about this?
Good starting places for new folks to ask general questions about this include:
Detailed technical discussion can happen on https://gitter.im/scala/community-builds.
And of course, we can also talk using issues and pull requests in this repo.