Commit 9a4a7391 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'nelbacha-master-patch-40031' into 'master'

Explicitly state what's not possible with artifact

See merge request gitlab-org/gitlab!31730
parents 5587cf3f 0dac2fce
...@@ -39,8 +39,9 @@ runtime dependencies needed to compile the project: ...@@ -39,8 +39,9 @@ runtime dependencies needed to compile the project:
- `artifacts`: **Use for stage results that will be passed between stages.** - `artifacts`: **Use for stage results that will be passed between stages.**
Artifacts are files generated by a job which are stored and uploaded, and can then Artifacts are files generated by a job which are stored and uploaded, and can then
be fetched and used by jobs in later stages of the **same pipeline**. This data be fetched and used by jobs in later stages of the **same pipeline**. In other words,
will not be available in different pipelines, but is available to be downloaded [you can't create an artifact in job-A in stage-1, and then use this artifact in job-B in stage-1](https://gitlab.com/gitlab-org/gitlab/-/issues/25837).
This data will not be available in different pipelines, but is available to be downloaded
from the UI. from the UI.
The name `artifacts` sounds like it's only useful outside of the job, like for downloading The name `artifacts` sounds like it's only useful outside of the job, like for downloading
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment