Add new and update CI build/test triggers
The build and tests run for all the base + modifier configs in CI should benefit to get maximum coverage towards testing Cassini's distro.
We barely test Cassini base image and since we are short on platforms on the farm, we need to optimize the pipelines to build and test if there are any specific changes affecting MR.
Nightly and Weekly runs should only be enabled for specific base + modifier config dependent on platforms
These are the following changes:
-
Add new builds for the platforms.
-
cassini/<platform>
:- Builds for
cassini
base config - Configured to run sanity tests (ACS if available)
- Builds for
-
cassini/security/<platform>
:- Builds for
cassini
base andsecurity
modifier config - Configured to run only sanity tests
- Builds for
-
cassini-dev/<platform>
:- Builds for
cassini-dev
base config - No tests configured to run
- Builds for
-
-
Remove
cassini/tests/<platform>
build config- The
cassini/tests/<platform>
is equivalent tocassini-dev/tests/<platform>
- The
-
Remove
cassini/security/tests/<platform>
build config- The
cassini/security/tests/<platform>
is equivalent tocassini-dev/security/tests/<platform>
- The
-
Modify
cassini-dev/tests/<platform>
build image trigger to onlyptest
-
Modify
cassini-dev/security/tests/<platform>
build image trigger
Please note: some config will be built for scheduled runs for testing purposes (nightly or weekly), these are:
cassini/<platform>
cassini/security/<platform>
cassini-dev/tests/<platform>
-
cassini-dev/security/tests/<platform>
- This build will not be done for corstone1000 mps3