Open lrytz opened 7 years ago
If we're going to change publishing, should also consider changing the versioning, so that sbt can derive the right binary version: https://github.com/scala/scala-dev/issues/252
Let's think about how to reuse these artifacts/jobs as much as possible. It would be good to have a canonical job and long-term artifact cache that can publish once, and then be used for bisecting, benchmarking, running the community build, building nightlies,....
not sure if this should stay open since I'm not really familiar with the bench stuff
The benchmark tool currently uses the ordinary
-integrate-bootstrap
jobs which publish toscala-release-temp
. We should have a repo that is lesstemp
to keep those builds (ideally forever, if there's enough space).We'll also need a new build job that allows passing in compiler flags and customizing the artifact name, see https://github.com/scala/compiler-benchq/issues/4.