So I have a cache that I created in pipeline1 made to setup the cache which I then use in pipeline2. This cache called "bin" is cached from the root directory in pipeline1.
The output of pipeline2 reads:
Next, in one step, I ran a "ls -la" cmd in the root, but the bin folder did not show up. That step has the line "cache: - bin", so I know it is included.
Is there a reason it is not showing up?
And when trying to access this cache, does it need something other than "cd"?
@Joshua von Damm cache feature is embedded, but it works automatically, so it is supposed , that you should not cd to it or ls manually.
Anyway, caches are lying in the appropariate directory where appropriate app, like docker, would create a cache. Look at the doc, table in the section Pre-defined caches
Thanks for the reply! I should have specified that I am using a custom cache, and based on the same article you linked, it should by default be in the root dir.
But I came across a fix that I don't think should have worked.
For whatever reason, adding the $BITBUCKET_CLONE_DIR variable which specifies the root dir fixed the issue. This means that they could be lying about custom caches, and that it doesn't really start at the root dir unless you specifically tell it to.
Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events