-
Notifications
You must be signed in to change notification settings - Fork 6
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
publish 'use' images #69
Conversation
f279c15
to
d31559a
Compare
d31559a
to
ccd7f21
Compare
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.
I admit I don't fully grok yet how this works. Some preliminary comments and questions.
- name: Push proposal "use" images | ||
uses: docker/bake-action@v4 |
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.
I fail to see anywhere how a use image is prefixed with pr-NN-
before pushing.
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.
This isn't meant to push tags for "use" images out of PR builds. It does for review but once the PR is approved I'll change it to only push from the default branch. That sidesteps the issue of distinguishing use images by branch origin.
Well that answers my question. If we could figure out prefixing, it might be nice to avoid overriding, at least for the case where we manually trigger a workflow.
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.
Agree it "might be nice" . I don't think we need it to deliver #25. Let's tackle if a need presents itself.
ccd7f21
to
bd72b61
Compare
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.
Looks good. Just a few questions, but when you're satisfied with your answers, feel free to merge.
4f26603
to
2d033f9
Compare
2d033f9
to
a0b92e4
Compare
a0b92e4
to
9285e9b
Compare
closes: #25
Publishes "use" images so that consumers can rely on a certain state of state of the chain. They're published as tags matching the target, like
use-upgrade-9
. I experimented with having separate images names such as a3p-use-upgrade8 but we agreed it's better to just use tags. They're all visible at https://ghcr.io/agoric/agoric-3-proposals.This isn't meant to push tags for "use" images out of PR builds. It does for review but once the PR is approved I'll change it to only push from the default branch. That sidesteps the issue of distinguishing use images by branch origin.
This PR has some other cleanup and refactoring along the way. I recommend reviewing by commit.