You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
I have a multi-stage Build pipeline. Each stage relies on node_modules. While generating the cache, it is producing multiple versions of the same artifact in Artifacts Feed. As these artifacts are nothing but node_modules, the older version of node_modules makes no sense and should be cleared with the Artifacts Feed retention policy. If the user can configure the artifact base name or the task takes stage name also into consideration while generating the artifact, retention policy with keeping only the latest (or last 2) version can be enforced easily.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a multi-stage Build pipeline. Each stage relies on node_modules. While generating the cache, it is producing multiple versions of the same artifact in Artifacts Feed. As these artifacts are nothing but node_modules, the older version of node_modules makes no sense and should be cleared with the Artifacts Feed retention policy. If the user can configure the artifact base name or the task takes stage name also into consideration while generating the artifact, retention policy with keeping only the latest (or last 2) version can be enforced easily.
The text was updated successfully, but these errors were encountered: