Caching docker image between steps

[Sergei Beilin]

I was thinking of splitting a pipeline into two steps:

• build the docker image and run the tests,
• push the image to registry and "deploy".

This separation seems logical but the image built in the first step is not available in the second one.

Any suggestions, best practices?

[Richard Quadling]

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).