Closed Bug 1128620 Opened 11 years ago Closed 11 years ago

cloud-tools update on slaveapi failing

Categories

(Release Engineering :: General, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Unassigned)

References

Details

Attachments

(1 file)

This is probably just a simple puppet change, but: (prod)[cltbld@slaveapi1.srv.releng.scl3.mozilla.com prod]$ tail /var/spool/mail/cltbld X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/home/cltbld> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=cltbld> X-Cron-Env: <USER=cltbld> Message-Id: <20150120155501.857606073B@slaveapi1.srv.releng.scl3.mozilla.com> Date: Tue, 20 Jan 2015 07:55:01 -0800 (PST) /bin/sh: git: command not found was regressed by: Bug 1105430 I'm not certain if we need to force re-clone cloud tools on slaveapi or not though.
I made the mistake of manually updating this today and broke all the things because of: https://bugzilla.mozilla.org/show_bug.cgi?id=1020512#c30 for what it's worth wrt git not being in the path: (dev)[cltbld@slaveapi-dev1.srv.releng.scl3.mozilla.com aws]$ which git /usr/local/bin/git looks like we need to add '/usr/local' to PATH: X-Cron-Env: <PATH=/usr/bin:/bin>
Blocks: 1020512
Cron tasks really shouldn't be relying on PATH, but should specify the fully-qualified pathname of the executable.
Attachment #8581428 - Flags: review?(coop) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: