-
-
Notifications
You must be signed in to change notification settings - Fork 314
Naming Convention for Test Builds in Jenkins
Shelley Lambert edited this page Sep 11, 2018
·
5 revisions
To loosely mirror the compile jobs in Jenkins, we will use the following naming convention:
version_impl_jobtype_arch_os
Examples:
- openjdk8_hs_systemtest_ppc64_aix
- openjdk9_j9_openjdktest_x86-64_linux
- openjdk10_hs_openjdktest_x86-64_linux
- openjdk8_hs_externaltest_extended_x86-64_linux
Where each part of the name, can vary with the following values:
version
- openjdk8
- openjdk10
- openjdk11
impl
- hs (hotspot)
- j9 (openj9)
- sap (sap)
jobtype
- openjdktest
- systemtest
- externaltest
- externaltest_extended
- perftest
- jcktest
arch
- x86-64
- s390x
- ppc64le
- ppc64
- aarch64
- aarch32
os
- linux
- macos
- windows
- aix
- solaris
- docker (need more detail here)