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
We previously had some issues building locally in RISC-V containers on real hardware (Slack thread) which were due to a build-up of defunct processes which has now been resolved with the merging of adoptium/ci-jenkins-pipelines#1067
This issue is to look at the feasibility of moving to using native RISC-V machines now that we have some hosted at Scaleway instead of the qemu-emulated build containers that we are currently using. Noting that moving to native machines would allow us to use --enable-sbom-strace on the RISC-V builds (Ref: adoptium/ci-jenkins-pipelines#1065)
We previously had some issues building locally in RISC-V containers on real hardware (Slack thread) which were due to a build-up of defunct processes which has now been resolved with the merging of adoptium/ci-jenkins-pipelines#1067
This issue is to look at the feasibility of moving to using native RISC-V machines now that we have some hosted at Scaleway instead of the qemu-emulated build containers that we are currently using. Noting that moving to native machines would allow us to use
--enable-sbom-strace
on the RISC-V builds (Ref: adoptium/ci-jenkins-pipelines#1065)The text was updated successfully, but these errors were encountered: