Pass artifacts between steps/builds

When using Docker executors, no mechanism exists to store images between builds. This would enable, for example, exporting Docker images for production use, or even refreshing an image to use for testing in a subsequent build step so that the code under test maintains parity with the container it's running in.

See https://forum.gitlab.com/t/deploy-cant-use-output-from-build/1460

Possible overlap: #44 (closed)

Possible overlap: #56 (closed)

Possible overlap: #97 (closed)

Possible overlap: #147 (closed)

Yes, we see demand for this feature.

We are currently finishing work on build artifacts feature that should help with that case. We still haven't defined the mechanics how the artifacts should be downloaded for next stages, but we are looking into it.

This is planned for 8.3.

Reassigned to @ayufan

Milestone changed to v1.0

+1 for this

Wouldn't it be possible to share the global cache for each stage? Otherwise the difference between the global cache and the job cache is not that big.

@aneumann91

I have in plan (for 8.3) to make it possible to specify the cache affinity between jobs. However, this will not solve the problem. If for example builds get executed out of order you have not way of knowing that cache contains the files that you need.

That's right, I have to make sure myself if executable exists (if [-e executable] do deploy else exit 1 done or something like this).

Hi, now 8.3 is out - did it work to pass artifacts between stages or define cache affinity, because I can't see anything of this in the docu.

Milestone changed to v1.1

Status changed to closed

This resolved by: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/80