Dependent builds (aka artifacts passing)

I want to finally solve this: https://gitlab.com/gitlab-org/gitlab-ce/issues/3423

My idea:

build:
  stage: build
  script: ...
  artifacts:
    paths:
    - binaries/

test:
  stage: test
  script: ...
  dependencies:
  - build

deploy:
  stage: deploy
  script: ...
  dependencies:
  - build

It will download all dependencies from the build in test and deploy jobs. I thought about putting that in context of artifacts, but this makes it confusing what artifacts are doing: part of the options will be used for creating an archive, and part for selecting dependencies. Using the dependencies seems like a simple and clear solution.

By default the build will depend on all past builds.

cc @grzesiek

mentioned in merge request !3182 (merged)

mentioned in commit ca3fc229

Any example of consumption of the artifacts? The documentation does not provide any, regardless of dependencies feature. I'm exporting files from test job but they are not reachable from pages job, tried ls . and ls .. without success.

@ayufan Example project from your account https://gitlab.com/ayufan/artifacts-passing is also failing now due to not reaching artifacts, see build: https://gitlab.com/jangorecki/artifacts-passing/builds/868282

@jangorecki This feature requires GitLab Runner 1.1, which is currently releases as Bleeding Edge and thus not available when using Shared Runners.

OK thanks for info, I will retry once runner 1.1 will be deployed then.

Milestone changed to 8.7

mentioned in issue #14728 (moved)

Closed by ca3fc229

Status changed to closed

Yes, already using the default artifacts passing from multiple builds, then all published by pages job. Works like a charm, thanks!

Mentioned in commit pfjason/gitlab-ce@ca3fc229

Mentioned in issue #14728 (moved)

mentioned in issue gitlab#4548