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

Process for pushing container images to gcr.io/agones-images #917

Closed
roberthbailey opened this issue Jul 17, 2019 · 1 comment
Closed

Process for pushing container images to gcr.io/agones-images #917

roberthbailey opened this issue Jul 17, 2019 · 1 comment
Labels
area/build-tools Development tooling. I.e. pretty much everything in the `build` directory. area/meta Organisational matters. e.g. Governance, release cycles, etc. area/tests Unit tests, e2e tests, anything to make sure things don't break duplicate Duplicate ticket kind/design Proposal discussing new features / fixes and how they should be implemented kind/feature New features for Agones

Comments

@roberthbailey
Copy link
Member

As discussed in #894 (comment) (and the comment following) we should create a more formal process for updating the container images in the agones-images project, especially those used in the e2e testing and examples.

@roberthbailey roberthbailey added kind/feature New features for Agones area/build-tools Development tooling. I.e. pretty much everything in the `build` directory. area/meta Organisational matters. e.g. Governance, release cycles, etc. area/tests Unit tests, e2e tests, anything to make sure things don't break kind/design Proposal discussing new features / fixes and how they should be implemented labels Jul 17, 2019
@markmandel markmandel added the duplicate Duplicate ticket label Jul 28, 2022
@markmandel
Copy link
Member

This is now duplicated by #2358

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-tools Development tooling. I.e. pretty much everything in the `build` directory. area/meta Organisational matters. e.g. Governance, release cycles, etc. area/tests Unit tests, e2e tests, anything to make sure things don't break duplicate Duplicate ticket kind/design Proposal discussing new features / fixes and how they should be implemented kind/feature New features for Agones
Projects
None yet
Development

No branches or pull requests

2 participants