-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Investigate feasibility of ephemeral build systems for non-Linux platforms #3264
Comments
Note: The job-restrictions plugin which we will plan to install as part of adoptium/infrastructure#2108 (comment) should allow us to get some level of isolation (Not ephemeral, but blocking non-build jobs from running on certain systems) |
We should initially look at prioritising the primary platforms. Noting that Linux/s390x mentioned in the description is now building in a container, but the image is not being regular refreshed or stored off-machine at present:
|
Update:
The other two platforms are not currently being progressed. |
MacOS builds are being moved to orka3 under adoptium/infrastructure#2536 and will be tested heavily with the regular runs that will occur over the weekend. |
adoptium/infrastructure#3286 is part of this |
Feasibility has now been understood - windows will hopefully be ready shortly with the pipelines PR to allow docker containers, and AIX and Solaris can have separate issues created in the backlog pending someone with enough interest to achieve those levels on those platforms. |
Part of SLSA level 3 and SSDF PO5.1. Part of this should be to avoid any possible interference from non-build processes to the systems used for building.
There are other technologies which could be used for this to mimic our use of dynamically created Docker containers which we use on Linux (s390x TBC), for example Solaris Zones, AIX WPARs etc.
The text was updated successfully, but these errors were encountered: