It seems another task is put before the creation of
workspace directory causing:
'No such file or directoty: /home/zuul/workspace'
Change-Id: I4741f9bcd8709aaa3b26f28f3c427cd07e99c1a7
After migration to zuulv3 we found that timeout set in the job
is not applied to grenade runs.
This patch export BUILD_TIMEOUT directly from job.
Change-Id: I7a297af4461cf25227f1cff281e84e728baf90d3
This should be a no-op for single-node jobs, but for multi-node jobs it
should keep them from trying to copy logs from all of their nodes,
which they are not designed to do.
Change-Id: Ibcf158f1b8082fbffeb48fa48c6592c87e056d01
This isn't really a thing in v3, but structurally it's a thing we
need to provide to v2 jobs so they don't get confused.
Change-Id: Icb528444f44f18ca29e02154513b9facefd04c89
This is the result of having run the zuul migration tool.
Depends-On: I72687a56285a3d733a9adeaf3dc037a1ac95efd3
Change-Id: Ib511da75908e152e72fdf0d7b496f4fa98f9c223
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
