sxa
commented
4 days ago Options:
- Attempt to rebuild the new LTS agent ourselves such that it will run on JDK11.
- Attempt to build a JDK17 on Solaris 10 (There are patches to make it work with gcc but I struggled last time I tried to use them)
- Attempt to build a JDK17 on Solaris 11 and switch to that (also with GCC as most Solaris support was removed in JDK15), while building against a Solaris 10 sysroot.
- Same as the point above, but run a Solaris 10 zone under Solaris 11, similar to what we do with docker on Linux (Would also potentially allow us to satisfy https://github.com/adoptium/temurin-build/issues/3264#issuecomment-1688123318). This would require a bit of 'roll your own' since I doubt there's a docker plugin that can make this easy...
- Running a non-Solaris JDK17 using qemu on Solaris
- Running some proxy machine to run the jenkins agent and pass commands to the remote machine (likely hard because of the amount of shell invocations in our jenkins pipelines)
- Run a second jenkins server running an older version which can communicate with the Solaris node.
Anything else?
Notes:
- All of the "build JDK17" choices would likely force us into building each JDK up from 11 to get there.
- We could probably survive with a 'zero' implementation instead of one with a full JIT if required. I suspect that may be all we could get on SPARC ...
steelhead31
See: #3741
A solution will need to be investigated and implemented for running Jenkins agents on Solaris with Java 17.
Since JDK 17 is not supported on solaris, this will need additional work.
Specifically these 4 agents..
Whatever solution is found, will likely also need to be applied to the TCK solaris nodes.