Skip to content

Latest commit

 

History

History
46 lines (29 loc) · 1.92 KB

Yaml_Subcommand.rst

File metadata and controls

46 lines (29 loc) · 1.92 KB
Raw

YAML Subcommand (_buildtest yaml --help)

.. program-output:: cat scripts/Yaml_Subcommand/help.txt

Rebuilding Yaml Configuration (_buildtest yaml --rebuild)

The option --rebuild or -r allows buildtest to rebuild the yaml file for binarytest (command.yaml) in the event the file exist. When the file exist, buildtest will generally return immediately and do nothing.

(buildtest-0.5.0) [siddis14@adwnode1 buildtest-framework]$ _buildtest yaml --software GCCcore/6.4.0
File already exist: /home/siddis14/github/buildtest-configs/buildtest/ebapps/gcccore/6.4.0/command.yaml

With --rebuild option buildtest will attempt to create another binary test file (command.yaml) with date time-stamp added at end of file. The format for the new file is command_HH_MM_SS_MM_YYYY.yaml where HH:MM:SS represent hour, minute, second and MM:YYYY represent month and year.

See example below

(buildtest-0.5.0) [siddis14@adwnode1 buildtest-framework]$ _buildtest yaml --software GCCcore/6.4.0 -r
Please check YAML file  /home/siddis14/github/buildtest-configs/buildtest/ebapps/gcccore/6.4.0/command_10_57_17_10_2018.yaml  and fix test accordingly

Overwriting Yaml Configuration (_buildtest yaml --overwrite)

Similar to --rebuild the --overwrite or short option -o is used to overwrite the binary file command.yaml

(buildtest-0.5.0) [siddis14@adwnode1 buildtest-framework]$ _buildtest yaml --software GCCcore/6.4.0 -o
Overwriting content of yaml file: /home/siddis14/github/buildtest-configs/buildtest/ebapps/gcccore/6.4.0/command.yaml

Both --rebuild and --overwrite option works with --software, --package, --all-software, --all-package.