Use a tag to update "build-tools" repo on slaves

RESOLVED WONTFIX

Status

Release Engineering
General
P5
normal
RESOLVED WONTFIX
7 years ago
4 years ago

People

(Reporter: armenzg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Now, every time we image new machines out of the ref machine we have to make sure that the ref image has the latest "build-tools" on the machine through puppet or manually.

After "build-tools" is updated we have to ask IT to refresh the ref images.

Once the machine is cloned buildbot-tac.py is called to generate the buildbot.tac for that machine depending on the hostname.

If before calling buildbot-tac.py we ensured that "build-tools" is updated to a certain TAG we would not need to ask IT to refresh the images.

I suggest having two tags to help with this:
* BUILD_TOOLS_STAGING
* BUILD_TOOLS_PRODUCTION

I believe this would remove the dependency to block ourselves on IT or us forgetting to ask them to refresh the images. Now the problem would be reduce to us remembering to update the TAG! :)

catlee, bhearsum how does this plan sound like?
(Reporter)

Comment 1

7 years ago
Rephrasing the summary of the bug.
Summary: Tag tools repo every time we modify buildbot-tac.py → Use a tag to update "build-tools" repo on slaves
I think the long term solution to this is not having this logic slave side. P5'ing for now, because we don't know when that's going to happen.
Priority: -- → P5
Bug 615301 proposes to just get rid of the package entirely.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.