Bug 1247168 - Actually use workspace cache in decision task; r=dustin
The decision task configures a /home/worker/workspace cache. However,
the command we run in the container references a "workspace" relative
path. From logs in automation, it appears that PWD during execution
is "/" because "workspace" is being resolved to "/workspace." The
net result of this is we appear to be performing a VCS clone+checkout
on every single task.
This commit fixes the paths so our workspace cache is actually used.
MozReview-Commit-ID: Kj6REep5bSs
--- a/.taskcluster.yml
+++ b/.taskcluster.yml
@@ -84,18 +84,18 @@ tasks:
maxRunTime: 1800
command:
- /bin/bash
- -cx
- >
mkdir -p /home/worker/artifacts &&
- checkout-gecko workspace &&
- cd workspace/gecko &&
+ checkout-gecko /home/worker/workspace &&
+ cd /home/worker/workspace/gecko &&
ln -s /home/worker/artifacts artifacts &&
./mach taskgraph decision
--pushlog-id='{{pushlog_id}}'
--project='{{project}}'
--message='{{comment}}'
--owner='{{owner}}'
--level='{{level}}'
--base-repository='https://hg.mozilla.org/mozilla-central'
--- a/taskcluster/taskgraph/action.yml
+++ b/taskcluster/taskgraph/action.yml
@@ -49,18 +49,18 @@ payload:
# repository which is cached.
maxRunTime: 1800
command:
- /bin/bash
- -cx
- >
mkdir -p /home/worker/artifacts &&
- checkout-gecko workspace &&
- cd workspace/gecko &&
+ checkout-gecko /home/worker/workspace &&
+ cd /home/worker/workspace/gecko &&
ln -s /home/worker/artifacts artifacts &&
./mach taskgraph action-task
--decision-id='{{decision_task_id}}'
--task-labels='{{task_labels}}'
artifacts:
'public':
type: 'directory'