Commit b2b473dd authored by Jonston Chan's avatar Jonston Chan Committed by Marcel Amirault

Docs: update CI artifacts expiry docs to include "keep latest artifacts" note

parent bfba1efa
...@@ -37,9 +37,9 @@ can't link to files outside it. ...@@ -37,9 +37,9 @@ can't link to files outside it.
- Define artifacts per job. - Define artifacts per job.
- Subsequent jobs in later stages of the same pipeline can use artifacts. - Subsequent jobs in later stages of the same pipeline can use artifacts.
- Different projects cannot share artifacts. - Different projects cannot share artifacts.
- Artifacts expire after 30 days by default. You can define a custom [expiration time](../yaml/index.md#artifactsexpire_in).
Artifacts expire after 30 days unless you define an [expiration time](../yaml/index.md#artifactsexpire_in). - The latest artifacts do not expire if [keep latest artifacts](../pipelines/job_artifacts.md#keep-artifacts-from-most-recent-successful-jobs) is enabled.
Use [dependencies](../yaml/index.md#dependencies) to control which jobs fetch the artifacts. - Use [dependencies](../yaml/index.md#dependencies) to control which jobs fetch the artifacts.
## Good caching practices ## Good caching practices
......
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