Closed BeethovenKodar closed 6 months ago
I think that this certainly helps agilize local builds, but the CI seems to be very sad about this change :). I will try to trace down the root cause of the CI failures. In the past there was also a problem associated with downloading too many times from jitpack
, which simply destroyed some CI jobs... it does not seem to be case here though.
I would argue, based on what was output in a randomly picked CI test, that Error downloading com.github.forsyde.IDeSyDe:build-java-blueprints:develop-SNAPSHOT
should not be affected by the scala cache behavior. But who knows! Might be a tricky bug that got introduced.
That's a good argument. Let's merge this and see if any mysterious problems are awaken; CI is not fully in our control at the moment anyways.
This seems safe to do and vastly reduces the build time. https://www.scala-sbt.org/1.x/docs/Cached-Resolution.html