summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
diff options
context:
space:
mode:
authorTim Beale <timbeale@catalyst.net.nz>2019-02-14 11:20:16 +1300
committerAndrew Bartlett <abartlet@samba.org>2019-02-14 02:18:30 +0100
commit7c1ae35b7fb519107bdea0ae85a211325747af95 (patch)
treec940154814e6f8df3c5732878d0457c7f5f2c529 /.gitlab-ci.yml
parent2381febcfafae30f3e65d7b11e823b92e3cd5ee3 (diff)
downloadsamba-7c1ae35b7fb519107bdea0ae85a211325747af95.tar.gz
.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 <timbeale@catalyst.net.nz> Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Diffstat (limited to '.gitlab-ci.yml')
-rw-r--r--.gitlab-ci.yml3
1 files changed, 3 insertions, 0 deletions
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: