Skip to content

G
gitlab-ce
Commit 271faee6 authored by Evan Read's avatar Evan Read
Browse files
Options

Merge branch 'docs-yaml-artifacts-followup' into 'master' 

Clean up job_artifacts after review

See merge request gitlab-org/gitlab!30567
parents 5a248a19 ecef0c8a
Show whitespace changes
Inline Side-by-side
Showing with 173 additions and 173 deletions
doc/.vale/gitlab/spelling-exceptions.txt
View file @ 271faee6
...@@ -86,7 +86,7 @@ discoverability ...@@ -86,7 +86,7 @@ discoverability
Disqus Disqus
Dockerfile Dockerfile
Dockerfiles Dockerfiles
Dotenv dotenv
downvoted downvoted
downvotes downvotes
Dpl Dpl
......
doc/ci/pipelines/job_artifacts.md
View file @ 271faee6
...@@ -6,9 +6,9 @@ type: reference, howto ...@@ -6,9 +6,9 @@ type: reference, howto
# Job artifacts # Job artifacts
> - Introduced in GitLab 8.2 and GitLab Runner 0.7.0. > - Introduced in GitLab 8.2 and GitLab Runner 0.7.0.
> - Starting with GitLab 8.4 and GitLab Runner 1.0, the artifacts archive format changed to `ZIP`, and it is now possible to browse its contents, with the added ability of downloading the files separately. > - Starting with GitLab 8.4 and GitLab Runner 1.0, the artifacts archive format changed to `ZIP`, and it's now possible to browse its contents, with the added ability of downloading the files separately.
> - In GitLab 8.17, builds were renamed to jobs. > - In GitLab 8.17, builds were renamed to jobs.
> - The artifacts browser will be available only for new artifacts that are sent to GitLab using GitLab Runner version 1.0 and up. It will not be possible to browse old artifacts already uploaded to GitLab. > - The artifacts browser will be available only for new artifacts that are sent to GitLab using GitLab Runner version 1.0 and up. It won't be possible to browse old artifacts already uploaded to GitLab.
Job artifacts are a list of files and directories created by a job Job artifacts are a list of files and directories created by a job
once it finishes. This feature is [enabled by default](../../administration/job_artifacts.md) in all once it finishes. This feature is [enabled by default](../../administration/job_artifacts.md) in all
...@@ -34,7 +34,7 @@ pdf: ...@@ -34,7 +34,7 @@ pdf:
expire_in: 1 week expire_in: 1 week
``` ```
A job named `pdf` calls the `xelatex` command in order to build a pdf file from 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 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 turn are defined with the `paths` keyword. All paths to files and directories
are relative to the repository that was cloned during the build. are relative to the repository that was cloned during the build.
...@@ -42,163 +42,14 @@ are relative to the repository that was cloned during the build. ...@@ -42,163 +42,14 @@ 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 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`](../yaml/README.md#artifactswhen) when the job fails, or always, if the [`artifacts:when`](../yaml/README.md#artifactswhen)
parameter is used. These uploaded artifacts will be kept in GitLab for 1 week as defined 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 by the `expire_in` definition. You can keep the artifacts from expiring
via the [web interface](#browsing-artifacts). If the expiry time is not defined, it defaults via the [web interface](#browsing-artifacts). If the expiry time is not defined, it defaults
to the [instance wide setting](../../user/admin_area/settings/continuous_integration.md#default-artifacts-expiration-core-only). to the [instance wide setting](../../user/admin_area/settings/continuous_integration.md#default-artifacts-expiration-core-only).
For more examples on artifacts, follow the [artifacts reference in For more examples on artifacts, follow the [artifacts reference in
`.gitlab-ci.yml`](../yaml/README.md#artifacts). `.gitlab-ci.yml`](../yaml/README.md#artifacts).
## Browsing artifacts ### `artifacts:reports`
> - From GitLab 9.2, PDFs, images, videos and other formats can be previewed directly in the job artifacts browser without the need to download them.
> - Introduced in [GitLab 10.1](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/14399), HTML files in a public project can be previewed directly in a new tab without the need to download them when [GitLab Pages](../../administration/pages/index.md) is enabled. The same applies for textual formats (currently supported extensions: `.txt`, `.json`, and `.log`).
> - Introduced in [GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16675), artifacts in private projects can be previewed when [GitLab Pages access control](../../administration/pages/index.md#access-control) is enabled.
After a job finishes, if you visit the job's specific page, there are three
buttons. You can download the artifacts archive or browse its contents, whereas
the **Keep** button appears only if you have set an [expiry date](../yaml/README.md#artifactsexpire_in) to the
artifacts in case you changed your mind and want to keep them.
![Job artifacts browser button](img/job_artifacts_browser_button.png)
The archive browser shows the name and the actual file size of each file in the
archive. If your artifacts contained directories, then you are also able to
browse inside them.
Below you can see what browsing looks like. In this case we have browsed inside
the archive and at this point there is one directory, a couple files, and
one HTML file that you can view directly online when
[GitLab Pages](../../administration/pages/index.md) is enabled (opens in a new tab).
![Job artifacts browser](img/job_artifacts_browser.png)
## Downloading artifacts
If you need to download the whole archive, there are buttons in various places
in the GitLab UI to do this:
1. While on the pipelines page, you can see the download icon for each job's
artifacts archive in the right corner:
![Job artifacts in Pipelines page](img/job_artifacts_pipelines_page.png)
1. While on the **Jobs** page, you can see the download icon for each job's
artifacts archive in the right corner:
![Job artifacts in Builds page](img/job_artifacts_builds_page.png)
1. While inside a specific job, you are presented with a download button
along with the one that browses the archive:
![Job artifacts browser button](img/job_artifacts_browser_button.png)
1. And finally, when browsing an archive you can see the download button at
the top right corner:
![Job artifacts browser](img/job_artifacts_browser.png)
## Downloading the latest artifacts
It is possible to download the latest artifacts of a job via a well known URL
so you can use it for scripting purposes.
NOTE: **Note:**
The latest artifacts are created by jobs in the **most recent** successful pipeline
for the specific ref. If you run two types of pipelines for the same ref, the latest
artifact will be determined by timing. For example, if a branch pipeline created
by merging a merge request runs at the same time as a scheduled pipeline, the
latest artifact will be from the pipeline that completed most recently.
Artifacts for other pipelines can be accessed with direct access to them.
The structure of the URL to download the whole artifacts archive is the following:
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/download?job=<job_name>
```
To download a single file from the artifacts use the following URL:
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/raw/<path_to_file>?job=<job_name>
```
For example, to download the latest artifacts of the job named `coverage` of
the `master` branch of the `gitlab` project that belongs to the `gitlab-org`
namespace, the URL would be:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/download?job=coverage
```
To download the file `coverage/index.html` from the same
artifacts use the following URL:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/raw/coverage/index.html?job=coverage
```
There is also a URL to browse the latest job artifacts:
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/browse?job=<job_name>
```
For example:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/browse?job=coverage
```
There is also a URL to specific files, including html files that
are shown in [GitLab Pages](../../administration/pages/index.md):
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/file/<path>?job=<job_name>
```
For example, when a job `coverage` creates the artifact `htmlcov/index.html`,
you can access it at:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/file/htmlcov/index.html?job=coverage
```
The latest builds are also exposed in the UI in various places. Specifically,
look for the download button in:
- The main project's page
- The branches page
- The tags page
If the latest job has failed to upload the artifacts, you can see that
information in the UI.
![Latest artifacts button](img/job_latest_artifacts_browser.png)
## Erasing artifacts
DANGER: **Warning:**
This is a destructive action that leads to data loss. Use with caution.
You can erase a single job via the UI, which will also remove the job's
artifacts and trace, if you are:
- The owner of the job.
- A [Maintainer](../../user/permissions.md#gitlab-cicd-permissions) of the project.
To erase a job:
1. Navigate to a job's page.
1. Click the trash icon at the top right of the job's trace.
1. Confirm the deletion.
## Retrieve artifacts of private projects when using GitLab CI
In order to retrieve a job artifact of a different project, you might need to use a private token in order to [authenticate and download](../../api/jobs.md#get-job-artifacts) the artifacts.
## `artifacts:reports`
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/20390) in GitLab 11.2. > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/20390) in GitLab 11.2.
> - Requires GitLab Runner 11.2 and above. > - Requires GitLab Runner 11.2 and above.
...@@ -216,7 +67,7 @@ NOTE: **Note:** ...@@ -216,7 +67,7 @@ NOTE: **Note:**
If you also want the ability to browse the report output files, include the If you also want the ability to browse the report output files, include the
[`artifacts:paths`](../yaml/README.md#artifactspaths) keyword. [`artifacts:paths`](../yaml/README.md#artifactspaths) keyword.
### `artifacts:reports:junit` #### `artifacts:reports:junit`
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/20390) in GitLab 11.2. > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/20390) in GitLab 11.2.
> - Requires GitLab Runner 11.2 and above. > - Requires GitLab Runner 11.2 and above.
...@@ -250,7 +101,7 @@ concatenated into a single file. Use a filename pattern (`junit: rspec-*.xml`), ...@@ -250,7 +101,7 @@ concatenated into a single file. Use a filename pattern (`junit: rspec-*.xml`),
an array of filenames (`junit: [rspec-1.xml, rspec-2.xml, rspec-3.xml]`), or a an array of filenames (`junit: [rspec-1.xml, rspec-2.xml, rspec-3.xml]`), or a
combination thereof (`junit: [rspec.xml, test-results/TEST-*.xml]`). combination thereof (`junit: [rspec.xml, test-results/TEST-*.xml]`).
### `artifacts:reports:dotenv` #### `artifacts:reports:dotenv`
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/17066) in GitLab 12.9. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/17066) in GitLab 12.9.
> - Requires GitLab Runner 11.5 and later. > - Requires GitLab Runner 11.5 and later.
...@@ -261,16 +112,16 @@ The collected variables are registered as runtime-created variables of the job, ...@@ -261,16 +112,16 @@ The collected variables are registered as runtime-created variables of the job,
which is useful to [set dynamic environment URLs after a job finishes](../environments.md#set-dynamic-environment-urls-after-a-job-finishes). which is useful to [set dynamic environment URLs after a job finishes](../environments.md#set-dynamic-environment-urls-after-a-job-finishes).
It's not available for download through the web interface. It's not available for download through the web interface.
There are a couple of limitations on top of the [original Dotenv rules](https://github.com/motdotla/dotenv#rules). There are a couple of limitations on top of the [original dotenv rules](https://github.com/motdotla/dotenv#rules).
- The variable key can contain only letters, digits and underscore ('_'). - The variable key can contain only letters, digits and underscore ('_').
- The size of the Dotenv file must be smaller than 5 kilobytes. - The size of the dotenv file must be smaller than 5 kilobytes.
- The number of variables must be less than 10. - The number of variables must be less than 10.
- It does not support variable substitution in the Dotenv file itself. - It does not support variable substitution in the dotenv file itself.
- It does not support empty lines and comments (`#`) in Dotenv file. - It does not support empty lines and comments (`#`) in dotenv file.
- It does not support quote escape, spaces in a quote, a new line expansion in a quote, in Dotenv file. - It does not support quote escape, spaces in a quote, a new line expansion in a quote, in dotenv file.
### `artifacts:reports:cobertura` #### `artifacts:reports:cobertura`
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/3708) in GitLab 12.9. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/3708) in GitLab 12.9.
> - Requires [GitLab Runner](https://docs.gitlab.com/runner/) 11.5 and above. > - Requires [GitLab Runner](https://docs.gitlab.com/runner/) 11.5 and above.
...@@ -282,7 +133,7 @@ and will be automatically shown in merge requests. ...@@ -282,7 +133,7 @@ and will be automatically shown in merge requests.
Cobertura was originally developed for Java, but there are many Cobertura was originally developed for Java, but there are many
third party ports for other languages like JavaScript, Python, Ruby, and so on. third party ports for other languages like JavaScript, Python, Ruby, and so on.
### `artifacts:reports:terraform` #### `artifacts:reports:terraform`
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/207527) in GitLab 12.10. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/207527) in GitLab 12.10.
> - Requires [GitLab Runner](https://docs.gitlab.com/runner/) 11.5 and above. > - Requires [GitLab Runner](https://docs.gitlab.com/runner/) 11.5 and above.
...@@ -291,7 +142,7 @@ The `terraform` report collects Terraform `tfplan.json` files. The collected Ter ...@@ -291,7 +142,7 @@ The `terraform` report collects Terraform `tfplan.json` files. The collected Ter
plan reports will be uploaded to GitLab as artifacts and will be automatically shown plan reports will be uploaded to GitLab as artifacts and will be automatically shown
in merge requests. in merge requests.
### `artifacts:reports:codequality` **(STARTER)** #### `artifacts:reports:codequality` **(STARTER)**
> - Introduced in GitLab 11.5. > - Introduced in GitLab 11.5.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -302,7 +153,7 @@ as artifacts. ...@@ -302,7 +153,7 @@ as artifacts.
The collected Code Quality report will be uploaded to GitLab as an artifact and will The collected Code Quality report will be uploaded to GitLab as an artifact and will
be summarized in merge requests. It's not available for download through the web interface. be summarized in merge requests. It's not available for download through the web interface.
### `artifacts:reports:sast` **(ULTIMATE)** #### `artifacts:reports:sast` **(ULTIMATE)**
> - Introduced in GitLab 11.5. > - Introduced in GitLab 11.5.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -314,7 +165,7 @@ The collected SAST report will be uploaded to GitLab as an artifact and will be ...@@ -314,7 +165,7 @@ The collected SAST report will be uploaded to GitLab as an artifact and will be
in the merge requests and pipeline view. It's also used to provide data for security in the merge requests and pipeline view. It's also used to provide data for security
dashboards. It's not available for download through the web interface. dashboards. It's not available for download through the web interface.
### `artifacts:reports:dependency_scanning` **(ULTIMATE)** #### `artifacts:reports:dependency_scanning` **(ULTIMATE)**
> - Introduced in GitLab 11.5. > - Introduced in GitLab 11.5.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -326,7 +177,7 @@ The collected Dependency Scanning report will be uploaded to GitLab as an artifa ...@@ -326,7 +177,7 @@ The collected Dependency Scanning report will be uploaded to GitLab as an artifa
be summarized in the merge requests and pipeline view. It's also used to provide data for security be summarized in the merge requests and pipeline view. It's also used to provide data for security
dashboards. It's not available for download through the web interface. dashboards. It's not available for download through the web interface.
### `artifacts:reports:container_scanning` **(ULTIMATE)** #### `artifacts:reports:container_scanning` **(ULTIMATE)**
> - Introduced in GitLab 11.5. > - Introduced in GitLab 11.5.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -338,7 +189,7 @@ The collected Container Scanning report will be uploaded to GitLab as an artifac ...@@ -338,7 +189,7 @@ The collected Container Scanning report will be uploaded to GitLab as an artifac
be summarized in the merge requests and pipeline view. It's also used to provide data for security be summarized in the merge requests and pipeline view. It's also used to provide data for security
dashboards. It's not available for download through the web interface. dashboards. It's not available for download through the web interface.
### `artifacts:reports:dast` **(ULTIMATE)** #### `artifacts:reports:dast` **(ULTIMATE)**
> - Introduced in GitLab 11.5. > - Introduced in GitLab 11.5.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -350,7 +201,7 @@ The collected DAST report will be uploaded to GitLab as an artifact and will ...@@ -350,7 +201,7 @@ The collected DAST report will be uploaded to GitLab as an artifact and will
be summarized in the merge requests and pipeline view. It's also used to provide data for security be summarized in the merge requests and pipeline view. It's also used to provide data for security
dashboards. It's not available for download through the web interface. dashboards. It's not available for download through the web interface.
### `artifacts:reports:license_management` **(ULTIMATE)** #### `artifacts:reports:license_management` **(ULTIMATE)**
> - Introduced in GitLab 11.5. > - Introduced in GitLab 11.5.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -367,7 +218,7 @@ The collected License Compliance report will be uploaded to GitLab as an artifac ...@@ -367,7 +218,7 @@ The collected License Compliance report will be uploaded to GitLab as an artifac
be summarized in the merge requests and pipeline view. It's also used to provide data for security be summarized in the merge requests and pipeline view. It's also used to provide data for security
dashboards. It's not available for download through the web interface. dashboards. It's not available for download through the web interface.
### `artifacts:reports:license_scanning` **(ULTIMATE)** #### `artifacts:reports:license_scanning` **(ULTIMATE)**
> - Introduced in GitLab 12.8. > - Introduced in GitLab 12.8.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -379,7 +230,7 @@ The License Compliance report will be uploaded to GitLab as an artifact and will ...@@ -379,7 +230,7 @@ The License Compliance report will be uploaded to GitLab as an artifact and will
be automatically shown in merge requests, pipeline view and provide data for security be automatically shown in merge requests, pipeline view and provide data for security
dashboards. dashboards.
### `artifacts:reports:performance` **(PREMIUM)** #### `artifacts:reports:performance` **(PREMIUM)**
> - Introduced in GitLab 11.5. > - Introduced in GitLab 11.5.
> - Requires GitLab Runner 11.5 and above. > - Requires GitLab Runner 11.5 and above.
...@@ -390,7 +241,7 @@ as artifacts. ...@@ -390,7 +241,7 @@ as artifacts.
The collected Performance report will be uploaded to GitLab as an artifact and will The collected Performance report will be uploaded to GitLab as an artifact and will
be automatically shown in merge requests. It's not available for download through the web interface. be automatically shown in merge requests. It's not available for download through the web interface.
### `artifacts:reports:metrics` **(PREMIUM)** #### `artifacts:reports:metrics` **(PREMIUM)**
> Introduced in GitLab 11.10. > Introduced in GitLab 11.10.
...@@ -400,6 +251,155 @@ as artifacts. ...@@ -400,6 +251,155 @@ as artifacts.
The collected Metrics report will be uploaded to GitLab as an artifact and will The collected Metrics report will be uploaded to GitLab as an artifact and will
be automatically shown in merge requests. It's not available for download through the web interface. be automatically shown in merge requests. It's not available for download through the web interface.
## Browsing artifacts
> - From GitLab 9.2, PDFs, images, videos, and other formats can be previewed directly in the job artifacts browser without the need to download them.
> - Introduced in [GitLab 10.1](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/14399), HTML files in a public project can be previewed directly in a new tab without the need to download them when [GitLab Pages](../../administration/pages/index.md) is enabled. The same applies for textual formats (currently supported extensions: `.txt`, `.json`, and `.log`).
> - Introduced in [GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16675), artifacts in private projects can be previewed when [GitLab Pages access control](../../administration/pages/index.md#access-control) is enabled.
After a job finishes, if you visit the job's specific page, there are three
buttons. You can download the artifacts archive or browse its contents, whereas
the **Keep** button appears only if you've set an [expiry date](../yaml/README.md#artifactsexpire_in) to the
artifacts in case you changed your mind and want to keep them.
![Job artifacts browser button](img/job_artifacts_browser_button.png)
The archive browser shows the name and the actual file size of each file in the
archive. If your artifacts contained directories, then you're also able to
browse inside them.
Below you can see what browsing looks like. In this case we have browsed inside
the archive and at this point there is one directory, a couple files, and
one HTML file that you can view directly online when
[GitLab Pages](../../administration/pages/index.md) is enabled (opens in a new tab).
![Job artifacts browser](img/job_artifacts_browser.png)
## Downloading artifacts
If you need to download the whole archive, there are buttons in various places
in the GitLab UI to do this:
1. While on the pipelines page, you can see the download icon for each job's
artifacts archive in the right corner:
![Job artifacts in Pipelines page](img/job_artifacts_pipelines_page.png)
1. While on the **Jobs** page, you can see the download icon for each job's
artifacts archive in the right corner:
![Job artifacts in Builds page](img/job_artifacts_builds_page.png)
1. While inside a specific job, you're presented with a download button
along with the one that browses the archive:
![Job artifacts browser button](img/job_artifacts_browser_button.png)
1. And finally, when browsing an archive you can see the download button at
the top right corner:
![Job artifacts browser](img/job_artifacts_browser.png)
## Downloading the latest artifacts
It's possible to download the latest artifacts of a job via a well known URL
so you can use it for scripting purposes.
NOTE: **Note:**
The latest artifacts are created by jobs in the **most recent** successful pipeline
for the specific ref. If you run two types of pipelines for the same ref, the latest
artifact will be determined by timing. For example, if a branch pipeline created
by merging a merge request runs at the same time as a scheduled pipeline, the
latest artifact will be from the pipeline that completed most recently.
Artifacts for other pipelines can be accessed with direct access to them.
The structure of the URL to download the whole artifacts archive is the following:
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/download?job=<job_name>
```
To download a single file from the artifacts use the following URL:
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/raw/<path_to_file>?job=<job_name>
```
For example, to download the latest artifacts of the job named `coverage` of
the `master` branch of the `gitlab` project that belongs to the `gitlab-org`
namespace, the URL would be:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/download?job=coverage
```
To download the file `coverage/index.html` from the same
artifacts use the following URL:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/raw/coverage/index.html?job=coverage
```
There is also a URL to browse the latest job artifacts:
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/browse?job=<job_name>
```
For example:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/browse?job=coverage
```
There is also a URL to specific files, including HTML files that
are shown in [GitLab Pages](../../administration/pages/index.md):
```plaintext
https://example.com/<namespace>/<project>/-/jobs/artifacts/<ref>/file/<path>?job=<job_name>
```
For example, when a job `coverage` creates the artifact `htmlcov/index.html`,
you can access it at:
```plaintext
https://gitlab.com/gitlab-org/gitlab/-/jobs/artifacts/master/file/htmlcov/index.html?job=coverage
```
The latest builds are also exposed in the UI in various places. Specifically,
look for the download button in:
- The main project's page
- The branches page
- The tags page
If the latest job has failed to upload the artifacts, you can see that
information in the UI.
![Latest artifacts button](img/job_latest_artifacts_browser.png)
## Erasing artifacts
DANGER: **Warning:**
This is a destructive action that leads to data loss. Use with caution.
You can erase a single job via the UI, which will also remove the job's
artifacts and trace, if you are:
- The owner of the job.
- A [Maintainer](../../user/permissions.md#gitlab-cicd-permissions) of the project.
To erase a job:
1. Navigate to a job's page.
1. Click the trash icon at the top right of the job's trace.
1. Confirm the deletion.
## Retrieve artifacts of private projects when using GitLab CI
In order to retrieve a job artifact of a different project, you might need to use a private token in order to [authenticate and download](../../api/jobs.md#get-job-artifacts) the artifacts.
<!-- ## Troubleshooting <!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues Include any troubleshooting steps that you can foresee. If you know beforehand what issues
......
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
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7