Docs: Tweak the wording regarding artifact completion
This commit is contained in:
parent
11bb3b53bc
commit
04d9c3b271
|
@ -7,9 +7,9 @@
|
|||
> - Starting with GitLab 8.17, builds are renamed to jobs.
|
||||
> - This is the administration documentation. For the user guide see [pipelines/job_artifacts](../user/project/pipelines/job_artifacts.md).
|
||||
|
||||
Artifacts is a list of files and directories which are attached to a job
|
||||
after it completes successfully. This feature is enabled by default in all
|
||||
GitLab installations. Keep reading if you want to know how to disable it.
|
||||
Artifacts is a list of files and directories which are attached to a job after it
|
||||
finishes. This feature is enabled by default in all GitLab installations. Keep reading
|
||||
if you want to know how to disable it.
|
||||
|
||||
## Disabling job artifacts
|
||||
|
||||
|
@ -42,8 +42,9 @@ To disable artifacts site-wide, follow the steps below.
|
|||
|
||||
## Storing job artifacts
|
||||
|
||||
After a successful job, GitLab Runner uploads an archive containing the job
|
||||
artifacts to GitLab.
|
||||
GitLab Runner can upload an archive containing the job artifacts to GitLab. By default,
|
||||
this is done when the job succeeds, but can also be done on failure, or always, via the
|
||||
[`artifacts:when`](../ci/yaml/README.md#artifactswhen) parameter.
|
||||
|
||||
### Using local storage
|
||||
|
||||
|
|
|
@ -1189,9 +1189,9 @@ skip the download step.
|
|||
> - Job artifacts are only collected for successful jobs by default.
|
||||
|
||||
`artifacts` is used to specify a list of files and directories which should be
|
||||
attached to the job after success.
|
||||
attached to the job when it [succeeds, fails, or always](#artifactswhen).
|
||||
|
||||
The artifacts will be sent to GitLab after the job finishes successfully and will
|
||||
The artifacts will be sent to GitLab after the job finishes and will
|
||||
be available for download in the GitLab UI.
|
||||
|
||||
[Read more about artifacts](../../user/project/pipelines/job_artifacts.md).
|
||||
|
|
|
@ -16,7 +16,7 @@
|
|||
> [administration/job_artifacts](../../../administration/job_artifacts.md).
|
||||
|
||||
Artifacts is a list of files and directories which are attached to a job
|
||||
after it completes successfully. This feature is enabled by default in all
|
||||
after it finishes. This feature is enabled by default in all
|
||||
GitLab installations.
|
||||
|
||||
## Defining artifacts in `.gitlab-ci.yml`
|
||||
|
@ -36,12 +36,14 @@ pdf:
|
|||
A job named `pdf` calls the `xelatex` command in order to build a pdf file from
|
||||
the latex source file `mycv.tex`. We then define the `artifacts` paths which in
|
||||
turn are defined with the `paths` keyword. All paths to files and directories
|
||||
are relative to the repository that was cloned during the build. These uploaded
|
||||
artifacts will be kept in GitLab for 1 week as defined by the `expire_in`
|
||||
definition. You have the option to keep the artifacts from expiring via the
|
||||
[web interface](#browsing-artifacts). If the expiry time is not defined,
|
||||
it defaults to the [instance wide
|
||||
setting](../../admin_area/settings/continuous_integration.md#default-artifacts-expiration-core-only).
|
||||
are relative to the repository that was cloned during the build.
|
||||
|
||||
The artifacts will be uploaded when the job succeeds by default, but can be set to upload
|
||||
when the job fails, or always, if the [`artifacts:when`](../../../ci/yaml/README.md#artifactswhen)
|
||||
parameter is used. These uploaded artifacts will be kept in GitLab for 1 week as defined
|
||||
by the `expire_in` definition. You have the option to keep the artifacts from expiring
|
||||
via the [web interface](#browsing-artifacts). If the expiry time is not defined, it defaults
|
||||
to the [instance wide setting](../../admin_area/settings/continuous_integration.md#default-artifacts-expiration-core-only).
|
||||
|
||||
For more examples on artifacts, follow the [artifacts reference in
|
||||
`.gitlab-ci.yml`](../../../ci/yaml/README.md#artifacts).
|
||||
|
|
Loading…
Reference in New Issue