OpenSearch/.ci/matrix-runtime-javas.yml

# This file is used as part of a matrix build in Jenkins where the
# values below are included as an axis of the matrix.

# This axis of the build matrix represents the versions of Java on
# which Elasticsearch will be tested.  Valid Java versions are 'java'
# or 'openjdk' followed by the major release number.

ES_RUNTIME_JAVA:
  - java8
  - java8fips
  - java11
  - openjdk12
  - zulu8
  - zulu11
Java versions for ci (#29320) * Add test matrix axis files for periodic java testing * Add properties file defining java versions to use * We have no openjdk8 * Remove openjdk Oracle Java and OpenJDK basically only differ in license, so we don't need to test both. 2018-04-02 14:24:25 -04:00			`# This file is used as part of a matrix build in Jenkins where the`
			`# values below are included as an axis of the matrix.`

			`# This axis of the build matrix represents the versions of Java on`
			`# which Elasticsearch will be tested. Valid Java versions are 'java'`
			`# or 'openjdk' followed by the major release number.`

			`ES_RUNTIME_JAVA:`
			`- java8`
Enable FIPS JVM in CI (#32330) Now that #31666 and #31989 are merged we can run our tests in fips JVM. This commits enables us to run tests on a Java 8 JVM using BouncyCastleFIPS as a security Provider. 2018-07-25 08:48:19 +03:00			`- java8fips`
Add JDK11 support and enable in CI (#31644) * Upgrade bouncycastle Required to fix `bcprov-jdk15on-1.55.jar; invalid manifest format ` on jdk 11 * Downgrade bouncycastle to avoid invalid manifest * Add checksum for new jars * Update tika permissions for jdk 11 * Mute test failing on jdk 11 * Add JDK11 to CI * Thread#stop(Throwable) was removed http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-June/053536.html * Disable failing tests #31456 * Temprorarily disable doc tests To see if there are other failures on JDK11 * Only blacklist specific doc tests * Disable only failing tests in ingest attachment plugin * Mute failing HDFS tests #31498 * Mute failing lang-painless tests #31500 * Fix backwards compatability builds Fix JAVA version to 10 for ES 6.3 * Add 6.x to bwx -> java10 * Prefix out and err from buildBwcVersion for readability ``` > Task :distribution:bwc:next-bugfix-snapshot:buildBwcVersion [bwc] :buildSrc:compileJava [bwc] WARNING: An illegal reflective access operation has occurred [bwc] WARNING: Illegal reflective access by org.codehaus.groovy.reflection.CachedClass (file:/home/alpar/.gradle/wrapper/dists/gradle-4.5-all/cg9lyzfg3iwv6fa00os9gcgj4/gradle-4.5/lib/groovy-all-2.4.12.jar) to method java.lang.Object.finalize() [bwc] WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.reflection.CachedClass [bwc] WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations [bwc] WARNING: All illegal access operations will be denied in a future release [bwc] :buildSrc:compileGroovy [bwc] :buildSrc:writeVersionProperties [bwc] :buildSrc:processResources [bwc] :buildSrc:classes [bwc] :buildSrc:jar ``` * Also set RUNTIME_JAVA_HOME for bwcBuild So that we can make sure it's not too new for the build to understand. * Align bouncycastle dependency * fix painles array tets closes #31500 * Update jar checksums * Keep 8/10 runtime/compile untill consensus builds on 11 * Only skip failing tests if running on Java 11 * Failures are dependent of compile java version not runtime * Condition doc test exceptions on compiler java version as well * Disable hdfs tests based on runtime java * Set runtime java to minimum supported for bwc * PR review * Add comment with ticket for forbidden apis 2018-07-05 03:24:01 +00:00			`- java11`
Add JDK 12 to CI rotation (#36915) Now that JDK 12 has entered rampdown phase one, it is time for us to add JDK 12 to the CI rotation. This commit adds matrix parameters such that we try to build with JDK 12, and we test running on JDK 12. 2018-12-20 20:47:56 -05:00			`- openjdk12`
Try running CI against Zulu (#36391) This commit adds Zulu to the CI rotation. This commit only means that we are going to try running CI against Zulu, it does not carry any implications of support in the past, now, or in the future. 2018-12-11 10:48:14 -05:00			`- zulu8`
			`- zulu11`