Stop using in-house linux machines for build and try

RESOLVED FIXED

Status

task
RESOLVED FIXED
4 years ago
a year ago

People

(Reporter: coop, Assigned: coop)

Tracking

Details

Attachments

(2 attachments, 1 obsolete attachment)

As part of pushing more into the cloud, we should stop running linux build and try jobs on in-house machines. Having a single, AWS-based platform will make management easier.

We preferentially run release builds on in-house hardware right now, but in conversation with catlee, we will use AWS slaves if no in-house machines are available.
Let's use spot instances for all release builders?
Attachment #8531605 - Flags: review?(bhearsum)
(Assignee)

Updated

4 years ago
Attachment #8531605 - Flags: review?(bhearsum) → review+
Can we go ahead and stop using them completely and decomm them, since we're now not using them for releases, which were the only reason we kept them around? After 5 hazard builds in a row on mozilla-beta on hp slaves died by exceeding their maxtime, I disabled all of them, but only one of the two I ran on ix slaves managed to finish, so now I disabled all of them, too.
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0035
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0024
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0016
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0008
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0010
(Assignee)

Updated

4 years ago
Depends on: b-linux64-ix-0002
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0027
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0025
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0029
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0033
(Assignee)

Updated

4 years ago
Depends on: b-linux64-hp-0012
(Assignee)

Updated

4 years ago
Depends on: b-linux64-ix-0007
Attachment #8557950 - Flags: review?(bugspam.Callek)
Comment on attachment 8557950 [details] [diff] [review]
remove old hp/ix slave types from buildbot-configs

Review of attachment 8557950 [details] [diff] [review]:
-----------------------------------------------------------------

Should be noted, that we're switching Thunderbird jobs from in-house physical machines to EC2. Which could in theory cause is more cost. Its absolutely the right choice when we don't have anymore inhouse stuff to run them on though. :-)


We should also fix the following to account for this patch while we're at it:
http://mxr.mozilla.org/build/source/buildbot-configs/mozilla2-staging/config.py
http://mxr.mozilla.org/build/source/buildbot-configs/mozilla/BuildSlaves.py.template#15  (and puppet for this as a followup)

(neither need a review for buildbot-configs imho, so consider this comment your rubber stamp)

::: mozilla/thunderbird_production_config.py
@@ +3,5 @@
>  from localconfig import \
>      GLOBAL_VARS, MAC_LION_MINIS, \
> +    LINUX64_EC2, \
> +    WIN32_IXS, WIN64_IXS, \
> +    WIN64_IXS, \

while here, can you strip one of the "WIN64_IXS" defs?
Attachment #8557950 - Flags: review?(bugspam.Callek) → review+
remove unused windows slave definitions too
Attachment #8557950 - Attachment is obsolete: true
Attachment #8557990 - Flags: review?(bugspam.Callek)
Comment on attachment 8557990 [details] [diff] [review]
remove old hp/ix slave types from buildbot-configs

Review of attachment 8557990 [details] [diff] [review]:
-----------------------------------------------------------------

for bug history, the mozilla2-staging dir is actually not in repo, despite mxr saying it is.
Attachment #8557990 - Flags: review?(bugspam.Callek) → review+
Attachment #8557990 - Flags: checked-in+
(Assignee)

Updated

4 years ago
Assignee: nobody → coop
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.