Are Bitbucket Pipelines Cache with Globs Broken?

[Roman Stoffel]

Context: I'm trying to work around the 1GByte limit for caches. That 1GByte limit is really painful, creating a lot of work to try to come up with work-arounds.

Anyway, I' tried to split up a cache by using Globs. According to the documentation you can use globs in a cache path.

So, I declared a cache, like this:

coursier-cache-orgs:
  key:
    files:
      - "**/*.sbt"
  path: '~/.cache/coursier/v1/https/*.org'

It does cache the data in that glob. However, it completely screws up the restoring of the cached items.

The original layout of the directory is something like:

• ~/.cache/coursier/v1/https/repo1.maven.org
• ~/.cache/coursier/v1/https/repo.jenkins-ci.org

So, it does cache these *.org directories, but it fuses them. So, when restoring it is:

• ~/.cache/coursier/v1/https/*.org/

That is of course completely useless, as the layout got changed.

[Ben]

Hi @Roman Stoffel 

We'll need to look at your repository, and full YML configuration in context to allow us to troubleshoot this further. Our system requires us to have a formal support ticket to grant us the necessary access to do so.

As you have a Premium paid workspace, I've raised a ticket on your behalf with our support team in the GMT+2 timezone, please check your email for further correspondence.

Cheers!

- Ben (Bitbucket Cloud Support)

[Roman Stoffel]

Thanks

I asked support. There it got immediately recognized as a known bug: https://jira.atlassian.com/browse/BCLOUD-23246