Closed Bug 1781202 Opened 3 years ago Closed 3 years ago

unify migrations from `mach try release` with actual merge automation config

Categories

(Release Engineering :: General, task)

Product:
Release Engineering
Component:
General
Type:
task

Tracking

(firefox105 fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox105 --- fixed

People

(Reporter: jcristau, Assigned: jcristau)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Bug 1781202 - use the same configs for "mach try release" migrations as for actual merge automation
48 bytes, text/x-phabricator-request
Details | Review

mach try release has a set of possible "migrations" that are configured in testing/mozharness/configs/merge_day/, whereas automation uses the behaviors listed in the merge-automation section of taskcluster/ci/config.yml.
It should be possible to reduce the duplication.

See Also: → 1781218
Assignee: nobody → jcristau
Status: NEW → ASSIGNED
Pushed by jcristau@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/92a7b98fca95 use the same configs for "mach try release" migrations as for actual merge automation r=releng-reviewers,aki DONTBUILD

https://hg.mozilla.org/mozilla-central/rev/92a7b98fca95

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

Attachment

General

Creator:
Created:
Updated:
Size: