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

[Integration] Request mizar update dev images only after CI test passed #595

Open
Sindica opened this issue Jan 19, 2022 · 0 comments
Open
Assignees
Labels
release-target-1.0.0 Release target 1.0.0 items

Comments

@Sindica
Copy link
Collaborator

Sindica commented Jan 19, 2022

What happened:
During the integration, Mizar dev images are used in both cross team integration test as well as internal development. There were multiple times that Mizar code changes were released too early into dev image and broke integration test, and often found those changes did not pass Mizar CI tests.

What you expected to happen:
Mizar code change should be tested internally first with a different image tag, also CI tests will be performed on this internal development tag. After CI tests pass, tag the image for cross integration test. Suggested tag:

alpha: for Mizar dev internal test
beta: for cross team integration test
gamma: pre release

How to reproduce it (as minimally and precisely as possible):
Currently arktos up with Mizar integration has Mizar operator stuck on ContainerCreating. mizar images were manually removed and retried, operator image could not be downloaded. Mizar latest change broke CI.

@vinaykul vinaykul self-assigned this Jan 22, 2022
@vinaykul vinaykul added the release-target-1.0.0 Release target 1.0.0 items label Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-target-1.0.0 Release target 1.0.0 items
Projects
None yet
Development

No branches or pull requests

2 participants