Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-21396

Local cache/artifacts for Self-hosted Pipelines Runner

XMLWordPrintable

    • 9
    • 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.

      Pipelines team did a great job releasing self-hosted pipeline runners, and it is time to go further and make them even better =)

       

      Currently, runners in my projects spend way too much time uploading/downloading caches and intermediate artifacts. It can take up to 90% for fast jobs like linters, and is complete waste of time, since the cache has already been downloaded in previous step. Because of that I cannot split my jobs to smaller ones - if I do so, it will end with pipelines taking more time to finish, which is inapropriate. Every cache defined adds a time to upload/download and compress/uncompress (my projects currently have 8 caches at most, but this number will soon grow).

      I suggest a local cache and artifacts for self-hosted runners. In case they are all running at the same machine (which is definitely doable for most of the projects), it will decrease pipelines duration, because no unnecessary network traffic will occur.

       

      You can also get some inspiration from Gitlab CI cache system =)

              Unassigned Unassigned
              e39b98aecdce Tim Kovalev
              Votes:
              34 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: