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.

Sign up for GitHub

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

Jump to bottom

Publish a latest tag for docker image #685

Open
XAMPPRocky opened this issue Jan 18, 2023 · 4 comments
Open

Publish a latest tag for docker image #685

XAMPPRocky opened this issue Jan 18, 2023 · 4 comments
Labels
area/user-experience Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc kind/feature New feature or request priority/low Issues that don't need to be addressed in the near term.

Comments

@XAMPPRocky
Copy link
Collaborator

XAMPPRocky commented Jan 18, 2023 •
edited
Loading

It would be nice if there was a latest tag to make trying out the docker image easier, it would make it nice for pulling in new versions for development testing where I'm just trying the latest rather than needing a specific version.
@XAMPPRocky XAMPPRocky added kind/feature New feature or request area/user-experience Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc labels Jan 18, 2023
@markmandel
Copy link
Contributor

Do want :latest for the PR'd version, the last commit, or what we publish as a release version?

@XAMPPRocky
Copy link
Collaborator Author

I think we want latest to be the latest release to match the expected convention, I wouldn't also be opposed to having a dev (main? dev-main?) tag for latest main image, that would also be nice for testing versions.

@markmandel
Copy link
Contributor

I'll be honest - for production releases, I'm reticent to have a latest, just because it's such an anti-pattern for production systems.

For development, we could definitely do a latest for main (off the ci repository), we'd just need to build it each time, which is easy enough to do.

@XAMPPRocky XAMPPRocky added the priority/low Issues that don't need to be addressed in the near term. label Jan 25, 2023
@markmandel
Copy link
Contributor

Note from community meeting: Let's build a us-docker.pkg.dev/quilkin/ci/quilkin:latest that will be build of main, and overwrite on each merge of a PR / commit to main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/user-experience Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc kind/feature New feature or request priority/low Issues that don't need to be addressed in the near term.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@markmandel @XAMPPRocky