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

Update README.md #63

Closed
wants to merge 5 commits into from
Closed

Update README.md #63

wants to merge 5 commits into from

Conversation

wainersm
Copy link
Owner

No description provided.

wainersm and others added 5 commits November 15, 2023 14:09
The podvm_builder, podvm_binaries, and podvm workflows were converted to
`workflow_call` so that they can be re-used.

Before, on release time, `podvm_builder` were first triggered on a `release` event
then the others followed upon finish of the previous. With this change,
the `podvm_publish` workflow was created to be the entry point for
the `release` event (or manual dispatch), so the (now) callable `podvm_builder`,
`podvm_binaries`, and `podvm` are directly called.

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Added the `registry` parameter to the builder/binaries/podvm workflows
to allow publish the images in an arbitrary registry. Also added login
handler if the registry is `ghcr.io`.

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Currently the podvm images are tagged with the versions.yaml hash. This
will allow one use an arbitrary tag by exporting the PODVM_TAG variable.

The podvm_builder, podvm_binaries and podvm workflows changed to get the
`image_tag` input (non-required).

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Until now the `e2e_on_pull` workflow was using built podvm images, where
the qcow2 files are extracted and uploaded as artifacts which are picked
up by downstream jobs (e.g. `e2e_libvirt`). This changed the workflow to
leverage the new `podvm_builder`, `podvm_binaries` and `podvm` workflows
so that the podvm images are built from the pull request code, pushed to
ghcr.io and the downstream jobs should extract the qcow2 file
themselves.

Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
@wainersm wainersm force-pushed the main branch 2 times, most recently from 77c4430 to 3e831ce Compare November 21, 2023 20:28
@wainersm wainersm closed this Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant