On Mon, Nov 23, 2020 at 09:42:44AM +0800, Li Ping wrote:
add a document for introducing the define_files field.
Signed-off-by: Li Ping 15396232681@163.com
doc/job/define_files.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/job/define_files.md
diff --git a/doc/job/define_files.md b/doc/job/define_files.md new file mode 100644 index 0000000..dec74f1 --- /dev/null +++ b/doc/job/define_files.md @@ -0,0 +1,16 @@ +# define_files
+Meaning: +- We use lkp-tests as client for compass-ci. There are many testcases in lkp-tests. most testcases contain the following files:
- distro/depends/$testcase
- distro/depends/$testcase-dev
- pkg/$testcase/PKGBUILD
- stats/$testcase
- tests/$testcase
- jobs/$testcase.yaml
+- When user add new testcase files to lkp-tests or change existing testcase files in lkp-tests, these change files that related with test program would be added to define_files field. +- The define_files field do not need to be specified by user in the $testcase.yaml. It can be generated automatically by the scheduler when user submit with the option '-a'. User can confirm the define_files field in the job.yaml under result_root.
The scheduler can't automatically generate the field, submit action does this in lkp-test.
Thanks, Xueliang
+Usage example: +- % submit -a $testcase.yaml testbox=vm-2p8g--$USER os=openeuler os_arch=aarch64 os_version=20.03
+- % cat /srv/result/$testcase/vm-2p8g--$USER/$date/$job_id/job.yaml
2.23.0