Open Bug 1797525 Opened 3 years ago Updated 6 months ago

ci-admin: check local repo for freshness before `ci-admin apply`

Categories

(Release Engineering :: Firefox-CI Administration, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: mozilla, Unassigned)

Details

Attachments

(1 file)

(I have WIP at https://phabricator.services.mozilla.com/D151654)

Currently, we can apply changes from ci-configuration using these steps. There is no check to make sure that our local clone is up to date. This can be a footgun, if we intend to apply the latest official state but our local clone is on an older or unlanded revision.

Let's verify that our clone's revision matches the latest commit in ci-configuration, unless we specify --force or some other flag to bypass that check. This both catches the footgun in the normal case, but allows for emergency fixes when needed.

Severity: -- → S3
QA Contact: michelle
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: