-
Notifications
You must be signed in to change notification settings - Fork 0
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
Actually push everywhere, build manifests #5
Conversation
subprocess.run( | ||
[ | ||
"docker", | ||
"manifest", | ||
"create", | ||
major_manifest_name, | ||
f"{gcr_image}-arm64", | ||
f"{gcr_image}-amd64", | ||
] | ||
) | ||
subprocess.run( | ||
[ | ||
"docker", | ||
"manifest", | ||
"create", | ||
minor_manifest_name, | ||
f"{gcr_image}-arm64", | ||
f"{gcr_image}-amd64", | ||
] | ||
) | ||
# the more specific annotation of the first manifest seems to carry through to the others | ||
subprocess.run(["docker", "manifest", "push", gcr_image]) | ||
subprocess.run(["docker", "manifest", "push", major_manifest_name]) | ||
subprocess.run(["docker", "manifest", "push", minor_manifest_name]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you need to check the returncode
on these subprocesses?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"need" is a bit of a loaded term. No, since it's the last thing it'll try to do and the output will be in the same place I'd put it if it were to fail.
Co-authored-by: Chris Jones <[email protected]>
TODO:
I ran this and confirmed local changes up to the point I could. I did run equivalent steps for a single manifest to do some testing of that process. Haven't run a full testing that actually pushes yet.