1666321 - [mergeduty] leftovers to full automation

Status: RESOLVED DUPLICATE of bug 1782086

(Release Engineering :: General, enhancement)

Description

[Mihai Tabara [:mtabara]⌚️GMT]

Mergeduty has traditionally been a very manual process. Nowadays the bulk of it has been moved to automation. Still, there are things that linger that could benefit of automation:

1. nightly bump in shipit

Potentially waiting on nightly automation to be added in Shipit. Then add a github behavior in githubscript to handle this task.

2. wiki version bumping

There was a script somewhere flying around, we should look into ways to integrate that.

3. merge steps being driven by shipit

Ideally we should move all the buttons in Ship-it so that it can be coordinate from there and follow the status bar.

4. beta closing and opening automatically

API for treestatus here?

5. automatically enabling/disabling automatic betas?

If we move everything in Ship-it, it'd be a simple button.

6. wnp

This might change soon, there's plans to switch to a different model.

7. email status notifications

get for free (matrix at least) if conducted by shipit

8. l10n bump

RelMan wants to be able to trigger this manually. Aki suggested l10n bumper could be part of the merge day behavior, without DONTBUILD and with CLOSED TREE. Currently triggerd by a hook (can be done by shipit).

9. bulk AC into a single promotion graph

Right now all AC tasks (dry runs or not) are run cross branches. That leaves room for error. Since the payload controls the outcome, we could centralize all of them in a single repo (central?) or schedule all these tasks within a single graph so that it's automated.

10. Button to trigger mergeduty for RelMan in Ship-it

Comment 1

[Johan Lorenzo [:jlorenzo]]

Thanks for filing this bug Mihai! I have some context about one of the points you mentioned.

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #0)

2. wiki version bumping

There was a script somewhere flying around, we should look into ways to integrate that.

Tracked at bug 1414278.

Comment 2

[Aki Sasaki (not active)]

Attachment: [treescript] allow for l10n-bump during central-to-beta

Comment 3

[Aki Sasaki (not active)]

Attachment: Bug 1666321 - run l10n-bump as part of central-to-beta merge day. r=#releng-reviewers

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/5c8ec6c704b2
run l10n-bump as part of central-to-beta merge day. r=releng-reviewers,bhearsum DONTBUILD

Comment 5

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/5c8ec6c704b2

Comment 6

[Mihai Tabara [:mtabara]⌚️GMT]

Ahal pointed out an interesting idea earlier today:

re: It doesn’t get automatically updated because it would need to know when a new nightly was available, not just when the version had been updated in-tree.

couldn't we have a cron task that checks the TC index for them?