I see there are predefined caches in pipelines now...that's great. We are using maven, so I'll use that as an example here.
I am, however, unclear on how they work. I could see it one of two ways.
I've been trying to configure it assuming option #1 above, but it does not seem to work properly -- or at least the reported cache size is very small (eg <900 B), so I don't think it is working based on that.
It would be nice if the documentation of Pipelines Caching were updated with more details, about this issue and all around.
Thanks for your question.
Pre-defined caches work like you described as 2. They are just a convenient mapping of commonly cached directories so that users won't need to define them. Indeed they'll cache the entire m2 repository.
Caches are private to the repo. Could you describe your security requirements a little further?
Re: caches being <900B, looks like we have an issue where for some Docker images, caches are saved empty. The dev team are looking into.
Thanks for the feedback, I'll update our documentation to clarify this.
Thanks for the response.
Our security concerns are just born out of this line the docs:
To me, this implies that there is a security risk with the caching, but perhaps no more so than any other part of our source code and artifacts being available to pipelines, so I'm sure it's fine.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs