Cmake Configuration¶
This will help to generate native build tool that uses platform independent configuration
files to generate native build tool files. You can execute inside build directory.
Build examples¶
Customize the Build Process¶
You can use the following build options to customize the build process:
- PLATFORM: Specify the platform names. See
platformsfor the list of platforms. - REGISTRY: Must end with forward slash (
/). Specify the privacy docker registry URL. If specified, all built images will be pushed to given docker registry. - REGISTRY_AUTH: Specify the registry authentication method. The only supported value is
docker, which uses the docker configuration file. - RELEASE: Must begin with colon (
:). Specify the release version. All built images will be tagged with it. Defaults to:latest - BACKEND: Specify the validation backend:
docker,kubernetes, orterraform. - TERRAFORM_OPTIONS: Specify the
terraformoptions. - TERRAFORM_SUT: Specify the target System Under Test (SUT) list.
- TIMEOUT: Specify the validation timeout, which contains the execution timeout and docker pull timeout. Default to 28800,300 seconds.
- BENCHMARK: Specify a workload pattern. Workloads not matching the pattern will be disabled. The workload pattern is in the format of
<workload-path>/<workload-sub-target>, where<workload-path>is the workload path relative to the project root, and<workload-sub-target>is any sub-component defined in the workload. For example, some workload defines multiple versions thus have multiple builds and testcase targets. - SPOT_INSTANCE: If specified, overwrite the
spot_instancevariable in the Cloud configuration files.
cmake -DBENCHMARK=workload/SpecCpu-2017 .. # all build targets of SpecCpu-2017
cmake -DBENCHMARK=workload/SpecCpu-2017/speccpu_2017_v119_gcc13_ubuntu24 .. # specific build target of SpecCpu-2017
Command Make Targets¶
- bom: Print out the BOM list of each workload.
- clean: Purge the
logs.