Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Artifact base name should be configurable or should take stage name into consideration #48

Open
aniket7824 opened this issue Dec 29, 2020 · 0 comments

Comments

@aniket7824
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant