From 7c1ae35b7fb519107bdea0ae85a211325747af95 Mon Sep 17 00:00:00 2001 From: Tim Beale Date: Thu, 14 Feb 2019 11:20:16 +1300 Subject: .gitlab-ci.yml: Include the actual command used by gitlab Someone who finds gitlab mysterious will have no idea what $CI_JOB_NAME should be, if they wanted to reproduce the autobuild job manually. It should be trivial to include the actual command being run in the logs. Signed-off-by: Tim Beale Reviewed-by: Andrew Bartlett --- .gitlab-ci.yml | 3 +++ 1 file changed, 3 insertions(+) (limited to '.gitlab-ci.yml') diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 37ca0549d81..b39f7864257 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -40,6 +40,9 @@ variables: - runner_system_failure - stuck_or_timeout_failure script: + # gitlab predefines CI_JOB_NAME for each job. The gitlab job usually matches the + # autobuild name, which means we can define a default template that runs most autobuild jobs + - echo "Running cmd script/autobuild.py $CI_JOB_NAME --verbose --nocleanup --keeplogs --tail --testbase /tmp/samba-testbase" - script/autobuild.py $CI_JOB_NAME --verbose --nocleanup --keeplogs --tail --testbase /tmp/samba-testbase others: -- cgit v1.2.1