Closed Bug 775250 Opened 10 years ago Closed 10 years ago

symlink buildbot master Makefile into its own buildbot-configs directory

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: rail)

Details

Attachments

(2 files)

Currently, the Makefile that each Buildbot master has (eg, /builds/buildbot/build1/Makefile) is a static copy that never gets updated after the master is initially set-up. It gets copied in from /builds/buildbot/buildbot-configs/Makefile.master.

As part of master set-up we should symlink that to buildbot-configs/Makefile.master rather than leaving it as a static old copy forever.

Rail even volunteered to fix this!
Attachment #643555 - Flags: review?(bhearsum)
Attachment #643556 - Flags: review?(bhearsum)
Attachment #643556 - Flags: review?(bhearsum) → review+
Attachment #643555 - Flags: review?(bhearsum) → review+
Comment on attachment 643555 [details] [diff] [review]
fabric action to fix existing ones

http://hg.mozilla.org/build/tools/rev/00a21e19f87d
Attachment #643555 - Flags: checked-in+
I ran the following to fix existing links:

for role in build scheduler tests try; do
  python manage_masters.py -f production-masters.json -R $role -j8 fix_makefile_symlink
done
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.