Closed Bug 1552503 Opened 5 months ago Closed 5 months ago

disable parallel gcp builds

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: grenade, Assigned: grenade)

References

Details

Attachments

(1 file)

we've learned what we needed to know from running parallel gcp builds. in order to reduce cost, disable running of parallel builds on gcp for m-c, m-i, autoland.

we're looking to reduce costs on infra. as parallel gcp builds have served their purpose of demonstrating they are possible and valid, we'd now like to disable them until a later date.

Assignee: relops → rthijssen
Status: NEW → ASSIGNED

Pushed by ccoroiu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9fc0f690af5a
disable parallel gcp builds on m-c, m-i, autoland r=wcosta

Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED

(In reply to Rob Thijssen [:grenade (EET)] from comment #1)

we're looking to reduce costs on infra. as parallel gcp builds have served their purpose of demonstrating they are possible and valid, we'd now like to disable them until a later date.

Correct me if I'm wrong, but I thought we had agreed in the meeting on Thursday to keep the builds running at tier 3 until August when compute-optimized hits GA?

I will admit that we have competing desires here between overall infra costs and GCP spend targets, but shutting these builds down completely makes it hard for interested parties (i.e. me) to iterate on instance type configs in the interim.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

We definitely did not want to keep the windows builds running; they're incredibly expensive atm and Travis gave me a clear number to stay below. Looking at the notes, Android PGO was on the list of things to keep working on, along with finishing sccache.

fwiw, it's still possible to run try builds on gcp with a try push similar to this:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=eba193c

eg:

hg clone https://hg.mozilla.org/mozilla-central
hg import https://hg.mozilla.org/try/raw-rev/eba193c --no-commit
# modify as required
hg commit -m "try: -b do -p android-aarch64,android-api-16,android-x86,android-x86_64,linux,linux-shippable,linux64,linux64-shippable,macosx64,macosx64-shippable,win32,win32-shippable,win64,win64-shippable -u none -t none"
hg push try -f

(In reply to Rob Thijssen [:grenade (EET)] from comment #6)

fwiw, it's still possible to run try builds on gcp with a try push similar to this:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=eba193c

Yes, I know we can still run stuff in try. I'm doing so right now, in fact.

However, I thought the plan was to explicitly not turn off running Linux builds to allow us to make some progress during downtime in other projects.

If Windows is expensive, that's fine. Let's turn them off for now, but please re-enable our Linux-based builds at tier 3.

Also, please see https://bugzilla.mozilla.org/show_bug.cgi?id=1551293#c6 and recognize the implications that might have for the migration schedule if performance is no longer an issue.

Regressions: 1552917

created bug 1552917 to track re-enabling linux, android & macosx

Status: REOPENED → RESOLVED
Closed: 5 months ago5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.