I was thinking of splitting a pipeline into two steps:
This separation seems logical but the image built in the first step is not available in the second one.
Any suggestions, best practices?
I'm not an expert!!
But, normally, for anything to be carried over from one step to another, you need to have an `artifacts` entry in the step that generates the assets.
If this can work for docker images/layers, I've no idea.
This approach may be more suitable to assets built within the checkout (a `dist` folder for example).
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
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