Skip to content
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

EPIC: Investigate Solution For Running Jenkins Agent On Solaris with Java 17 #3742

Open
steelhead31 opened this issue Sep 24, 2024 · 3 comments

Comments

@steelhead31
Copy link
Contributor

steelhead31 commented Sep 24, 2024

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..

  • build-siteox-solaris10u11-sparcv9-1
  • test-siteox-solaris10u11-sparcv9-1
  • build-azure-solaris10-x64-1
  • test-azure-solaris10-x64-1

Whatever solution is found, will likely also need to be applied to the TCK solaris nodes.

@sxa
Copy link
Member

sxa commented Sep 25, 2024

Options:

  1. Attempt to rebuild the new LTS agent ourselves such that it will run on JDK11.
  2. 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)
  3. 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 (subject to that being feasible in JDK8).
  4. 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 Investigate feasibility of ephemeral build systems for non-Linux platforms temurin-build#3264 (comment)). This would require a bit of 'roll your own' since I doubt there's a docker plugin that can make this easy...
  5. Running a non-Solaris JDK17 using qemu on Solaris
  6. 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)
  7. 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 ...

@sxa
Copy link
Member

sxa commented Sep 25, 2024

IMHO Options 1 or 3 would be the cleanest ones if we can make them work.

@steelhead31
Copy link
Contributor Author

  1. A quick test of the tribblix Solaris 11 / JDK17 proved it was incompatible with Solaris 10
  2. Reached out and confirmed that there is 100% no Solaris 10 / JDK17 package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

2 participants