
On Tue, Dec 08, 2020 at 04:35:26PM +0800, Zhang Yu wrote:
Add a document for introducing the result_root
Signed-off-by: Zhang Yu <2134782174@qq.com> --- doc/job/result_root.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/job/result_root.md
diff --git a/doc/job/result_root.md b/doc/job/result_root.md new file mode 100644 index 0000000..827e40e --- /dev/null +++ b/doc/job/result_root.md @@ -0,0 +1,9 @@ +# result_root + +Meaning: +- The result_root field specifies the path for storing the result +- if this field is not specified,
If specified, I'd suppose it take no effect and be overwrite by the scheduler.
the default value is: '''/result/#{suite}/#{submit_date}/ + #{tbox_group}/#{rootfs}", "#{pp_params}", "#{id}"'''
+- we can specify the value of result_root in the job.yaml file, here is an example: + '''result_root: /srv/result/iperf'''
That looks risky. Thanks, Fengguang