Closed Bug 1373647 Opened 3 years ago Closed 3 years ago

Releasetasks changes to support multiple signoffs

Categories

(Release Engineering :: Release Automation: Other, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(3 files)

... just to track some patches that are not in bug 1347212
Keywords: leave-open
Attached file PR for releasetask
Attachment #8878515 - Flags: review?(bhearsum)
Priority: -- → P1
Attachment #8878515 - Flags: review?(bhearsum) → review+
Comment on attachment 8878511 [details]
Bug 1373647 - Set release ETA for RC builds published to beta  a=release DONTBUILD

https://reviewboard.mozilla.org/r/149864/#review154524

::: testing/mozharness/scripts/release/publish_balrog.py:118
(Diff revision 2)
> +            # RC releases going to the beta channel have no ETA set for the
> +            # RC-to-beta push. The corresponding task is scheduled after we
> +            # resolve the push-to-beta human decision task, so we can schedule
> +            # it ASAP plus some additional 30m to avoid retry() to fail.
> +            sheduled_at = datetime.utcnow() + timedelta(minutes=30)
> +            cmd.extend(["--schedule-at", sheduled_at.isoformat()])

Typo here: sheduled_at should be scheduled_at. r=me with that fixed :).
Attachment #8878511 - Flags: review?(bhearsum) → review+
Comment on attachment 8878508 [details]
Bug 1373647 - Add release_eta

https://reviewboard.mozilla.org/r/149860/#review154542
Attachment #8878508 - Flags: review?(bhearsum) → review+
Pushed by raliiev@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/dd8408bfab61
Set release ETA for RC builds published to beta r=bhearsum a=release DONTBUILD
Comment on attachment 8878515 [details] [review]
PR for releasetask

deployed
Attachment #8878515 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
You need to log in before you can comment on or make changes to this bug.