Details
-
Suggestion
-
Resolution: Fixed
Description
Bitbucket pipeline has a mechanism in place that allows to save and restore the Gradle cache directory. We work with larger projects (following the mono-repository approach), where this approach may not scale too well. A Gradle cache grows rather quickly and it takes substantial resources already to just pack/unpack the Gradle cache. Moreover, different steps in the pipeline may only need small parts of it.
It would be desirable to have support for https://proandroiddev.com/speed-up-your-build-with-gradle-remote-build-cache-2ee9bfa4e18. As it allows to incrementelly check whether a given task has already been performed.
A simple HTTP repository would already suffice for it. In other project we made use of Artifactory generic repositories for this purpose. Or if no such feature is planned, it would be useful if there is a possiblity to know the location of the pipeline runners and allow the manual placements by customers (us) next to them. Or maybe allow to provide runners on our own similar to it is possible in Gitlab.