RFC 0056: Improving RelEng Deployment Velocity & Confidence

[bhearsum]

rendered

[ahal]

This is great, no notes!

Though I do have an adjacent thought. It would be neat if we could codify this in mozilla-releng/reps. E.g, have a separate template for "services" vs "packages".

I suspect most services will be different enough from one another that most of the things mentioned in this RFC will not be possible to make turnkey.. But perhaps there are some mozcloud config files, or taskcluster tasks that would generally be needed across any service we maintain.

This shouldn't be high priority because we basically never create new services these days, but on the other hand, mozilla-releng/reps now has the ability to update existing projects based on the template (ish)..

[bhearsum]

This is great, no notes!

Though I do have an adjacent thought. It would be neat if we could codify this in mozilla-releng/reps. E.g, have a separate template for "services" vs "packages".

This seems like a smart idea (although I wonder how it works out in a case like balrog, where we have a mini monorepo containing two services (balrog and agent and a package (client).

I suspect most services will be different enough from one another that most of the things mentioned in this RFC will not be possible to make turnkey.. But perhaps there are some mozcloud config files, or taskcluster tasks that would generally be needed across any service we maintain.

Most of the relevant MozCloud stuff lives in other repositories, but at the very least I guess we have a couple of GitHub actions that this could cover. (And IIRC, some of the Taskcluster IaC might come from the Taskcluster repo, so maybe there's a model for doing more?).

Taskcluster tasks could obviously be covered by this, of course.

[jcristau]

I like this, thank you!