Closed Bug 1648602 Opened 4 years ago Closed 3 years ago

support lifecycle rules in ci-config

Categories

(Taskcluster :: Operations and Service Requests, enhancement)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bstack, Assigned: bstack)

Details

Attachments

(4 files)

As it says on the tin.

Assignee: nobody → bstack
Status: NEW → ASSIGNED

Not sure if this is the best way to go about it or what else I should do!

Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/ci/ci-admin/rev/725e7504edd7
Allow configuring lifecycle rules for workerpools r=tomprince
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/ci/ci-configuration/rev/40b3c40ac64a
Set shorter reregistration timeout for workers r=tomprince

It turns out that most of our workers are on legacy docker-worker images, which have not been updated to
support registration, so I don't think we to limit the worker life-time this way.

Flags: needinfo?(bstack)

MANUAL PUSH: bypassing broken lando restrictions

Backout by mozilla@hocat.ca:
https://hg.mozilla.org/ci/ci-configuration/rev/d64633cbcd67
Backed out changeset 40b3c40ac64a for workers not supporting registration.

So we saw some workers that lived long enough to be terminated due to not reregistering?

Flags: needinfo?(bstack)

Yep. In particular infra/build-decision has a single worker that doesn't end up ever being idle for >15m, so does not shutdown. I noticed because worker-manger still showed it as running, and didn't start a worker, when it hit credential timeout.

Otherwise, ci-admin will think that the value always needs changing.

Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/ci/ci-configuration/rev/7419afc30827
Set default lifecycle to taskcluster default; r=Callek

I think this is done :)

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: