-
-
Notifications
You must be signed in to change notification settings - Fork 314
Naming Convention for Test Builds in Jenkins
Shelley Lambert edited this page May 12, 2020
·
5 revisions
We use the following naming convention for test jobs in Jenkins:
Test_version_impl_testLevel.testGroup_arch_os_heapVariant
Examples:
- Test_openjdk11_hs_sanity.openjdk_ppc64_aix
- Test_openjdk8_j9_extended.system_x86-64_mac_xl
- Test_openjdk11_j9_sanity.functional_x86-64_windows
- Test_openjdk11_hs_special.external_x86-64_linux
Where each part of the name, can vary with the following values:
Test_<version>_<impl>_<testLevel>
.<testGroup>_<arch>_<os>_<heapVariant>
<version>
- openjdk8
- openjdk11
- openjdk14
<impl>
- hs (hotspot)
- j9 (openj9)
- corretto (corretto)
<testLevel>
- sanity
- extended
- special
<testGroup>
- openjdk
- system
- external
- functional
- perf
- jck
<arch>
- x86-64
- x86-32
- s390x
- ppc64le
- ppc64
- aarch64
- aarch32
<os>
- linux
- mac
- windows
- aix
- solaris
<heapVariant>
(optional)
- xl (for openj9 large heap builds)