NO-JIRA: refactor(.github/workflows): use JSON-based platform runner mapping and add README for runners, then add IBM runners #2774
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The IBM runners are containers, not VMs, so I can't do these partitioning operations. And there isn't a separate volume for /mnt (or any other directory) anyways, so there is no point to it.
This is easy to make conditional, no big deal.
This is a significant problem; so far we used Homebrew to get latest (recent) Podman.
For sure it would be strange to maintain multiple ways of getting podman, so if we proceed with IBM runners, then Homebrew for Linux is most likely out.
The trouble with switching to OS version of Podman is that the config files assume currently Homebrew, so I'd need to change the configs.
How Has This Been Tested?
Let's see if the IBM runners will activate on a PR; if not
In fact they do activate for PRs, so that's good!
Self checklist (all need to be checked):
make test(gmakeon macOS) before asking for reviewDockerfile.konfluxfiles should be done inodh/notebooksand automatically synced torhds/notebooks. For Konflux-specific changes, modifyDockerfile.konfluxfiles directly inrhds/notebooksas these require special attention in the downstream repository and flow to the upcoming RHOAI release.Merge criteria: