-
Type:
Improvement
-
Status: Waiting for user
-
Priority:
Major
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Jenkins
-
Labels:None
-
Project:Shiro
Hi infra team,
as a follow-up to https://issues.apache.org/jira/browse/INFRA-20709, I would love to use OpenJDK-OpenJ9 and OpenJDK-Hotspot VMs from Adoptium (Adoptopenjdk.net).
They are widely used, eg OpenJ9 is the successor of IBM J9, which is used by all IBM Websphere customers and now an eclipse project. It has major differences from any hotspot vm, like different memory layout, garbage collectors and command line options.
In shiro I found out optional aliases of crypto algorithms were missing. Ie Projects from the ASF may not be portable or may use discouraged aliases if not tested on non-hotspot JVMs.
I would therefore like to see those JVMs (at least OpenJ9) in Jenkins.
Currently, we must use other tools like Travis CI for this.
as a follow-up to https://issues.apache.org/jira/browse/INFRA-20709, I would love to use OpenJDK-OpenJ9 and OpenJDK-Hotspot VMs from Adoptium (Adoptopenjdk.net).
They are widely used, eg OpenJ9 is the successor of IBM J9, which is used by all IBM Websphere customers and now an eclipse project. It has major differences from any hotspot vm, like different memory layout, garbage collectors and command line options.
In shiro I found out optional aliases of crypto algorithms were missing. Ie Projects from the ASF may not be portable or may use discouraged aliases if not tested on non-hotspot JVMs.
I would therefore like to see those JVMs (at least OpenJ9) in Jenkins.
Currently, we must use other tools like Travis CI for this.