You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of us recently met to try to figure out steps forward for adding multi-arch builds to our pipeline. One of the steps was to try to run the pipline, but using VMs (not containers spun up via kubernetes) as the workers for our builds for architectures where we can't get an openshift cluster.
Let's investigate this option and perhaps enumerate the amount of work that needs to be done in order to make it achievable. For this POC we don't even need multi-arch hardware as the same level of abstraction should apply cleanly for x86_64, but we did agree to get an aarch64 VM from Fedora Infra for the POC, so we can use that too. I'll look at acquiring one from Fedora infra.
The text was updated successfully, but these errors were encountered:
dustymabe
changed the title
multi-arch: POC running FCOS pipeline with VMs as jenkins workers (i.e. not kubernetes)
multi-arch: POC running FCOS pipeline with VMs as jenkins workers
Jun 16, 2020
@dustymabe Just to let you know when you come back, I got 2 VMs for POWER as well to use in the CI. It is in a public networking, no issues with vpns and such 😎
Some of us recently met to try to figure out steps forward for adding multi-arch builds to our pipeline. One of the steps was to try to run the pipline, but using VMs (not containers spun up via kubernetes) as the workers for our builds for architectures where we can't get an openshift cluster.
Let's investigate this option and perhaps enumerate the amount of work that needs to be done in order to make it achievable. For this POC we don't even need multi-arch hardware as the same level of abstraction should apply cleanly for x86_64, but we did agree to get an aarch64 VM from Fedora Infra for the POC, so we can use that too. I'll look at acquiring one from Fedora infra.
The text was updated successfully, but these errors were encountered: