• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      See https://community.atlassian.com/t5/Bitbucket-Pipelines-questions/How-to-setup-Gradle-Remote-Build-Cache/qaq-p/981395?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_answer&utm_content=topic

      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 it 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. Alternatively it would be interesting to have support for repositories in general, meaning generic HTTP, Docker and Maven similar to others like GitLab and Azure DevOps where it is a built-in feature as well.

            [BCLOUD-18103] Support Gradle Remote Build Cache

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3543404 ] New: JAC Suggestion Workflow 3 [ 3599846 ]

            Aneita added a comment -

            Hey @remom,

            Thanks for reaching out and for the suggestion. Given our current priorities, it's unlikely that we'll support this anytime soon. In the meantime however, I'll open this ticket to gauge the interest of other users in seeing the same thing.

            Thanks,
            Aneita

            Aneita added a comment - Hey @remom, Thanks for reaching out and for the suggestion. Given our current priorities, it's unlikely that we'll support this anytime soon. In the meantime however, I'll open this ticket to gauge the interest of other users in seeing the same thing. Thanks, Aneita

            R added a comment -

            in general the current setup is aggregated by BCLOUD-16314. Meaning that the current pipeline cache cannot be used as gradle build cache as it will only the cache once without the possiblity of invalidation. In the context of the Gradle build cache one would rather like to store the cached results after every build.

            R added a comment - in general the current setup is aggregated by BCLOUD-16314 . Meaning that the current pipeline cache cannot be used as gradle build cache as it will only the cache once without the possiblity of invalidation. In the context of the Gradle build cache one would rather like to store the cached results after every build.
            Geoff created issue -

              Unassigned Unassigned
              a68663853f5d R
              Votes:
              7 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: