Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow artifact naming for reference #8244

Open
treyhyde opened this issue Dec 15, 2022 · 0 comments
Open

Allow artifact naming for reference #8244

treyhyde opened this issue Dec 15, 2022 · 0 comments
Labels
kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@treyhyde
Copy link

Artifacts are named via their repository name which is potentially long, dotted, backslashed, underscored, and non-unique.
It would be desirable to name: these artifacts for reference purposes. In theory this would also allow me to build multiple images in the same repository and differ them in the app based on tag strategy.

Our use case is we run continuous experiments for the same project with say... differing settings or build parameters. It is the same code base and branch and thus multiple artifacts in one docker repo. We're forced to create a new repo for every experiment with skaffold where it would be easier to have a tag template such as EXPERIMENT_NAME+GIT_HASH or something similar.

@ericzzzzzzz ericzzzzzzz added kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment. labels Dec 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Development

No branches or pull requests

2 participants