By requiring 'braggi', none of the ARM64 builds would start. It wouldn't be appropriate to give the arm64 builders a "braggi" label so I'm creating a new "gigantic" label that can apply to the braggi and arm64 builders.
There are no nodes in mita that have a 'gigantic' label so that guarantees builds won't run on OVH ephemeral nodes.
Signed-off-by: David Galloway <dgallowa@redhat.com>
DIST == AVAILABLE_DIST && ARCH == AVAILABLE_ARCH &&
(ARCH == "x86_64" || (ARCH == "arm64" && ["xenial", "centos7"].contains(DIST)))
axes:
- - axis:
- type: label-expression
- name: MACHINE_TYPE
- values:
- - braggi
- axis:
type: label-expression
name: MACHINE_SIZE
values:
- - huge
+ - gigantic
- axis:
type: label-expression
name: AVAILABLE_ARCH
DIST == AVAILABLE_DIST && ARCH == AVAILABLE_ARCH &&
(ARCH == "x86_64" || (ARCH == "arm64" && ["xenial", "centos7"].contains(DIST)))
axes:
- - axis:
- type: label-expression
- name: MACHINE_TYPE
- values:
- - braggi
- axis:
type: label-expression
name: MACHINE_SIZE
values:
- - huge
+ - gigantic
- axis:
type: label-expression
name: AVAILABLE_ARCH
DIST == AVAILABLE_DIST && ARCH == AVAILABLE_ARCH &&
(ARCH == "x86_64" || (ARCH == "arm64" && ["xenial", "centos7", "centos8"].contains(DIST)))
axes:
- - axis:
- type: label-expression
- name: MACHINE_TYPE
- values:
- - braggi
- axis:
type: label-expression
name: MACHINE_SIZE
values:
- - huge
+ - gigantic
- axis:
type: label-expression
name: AVAILABLE_ARCH