automate merging for staging releases

RESOLVED FIXED

Status

RESOLVED FIXED
a year ago
a year ago

People

(Reporter: kmoir, Assigned: kmoir)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

50 bytes, text/x-github-pull-request
mtabara
: feedback+
Details | Review | Splinter Review
(Assignee)

Description

a year ago
There are several manual steps to merge code for staging releases.  We should see automate this so that is this is more automated

https://github.com/mozilla/releasewarrior/blob/master/how-tos/setup-staging-release.md
(Assignee)

Updated

a year ago
Blocks: 1398909
No longer blocks: 1397762
(Assignee)

Updated

a year ago
Assignee: nobody → kmoir
(Assignee)

Updated

a year ago
Depends on: 1401572
(Assignee)

Updated

a year ago
Depends on: 1401576
(Assignee)

Updated

a year ago
No longer depends on: 1401572, 1401576
(Assignee)

Comment 1

a year ago
Looking at the merge scripts this morning, it seems like it would be beneficial to have a dedicated machine for staging releases, like we do for the merge day scripts, perhaps the same machine.

https://bugzilla.mozilla.org/show_bug.cgi?id=1400015#c3
(Assignee)

Comment 2

a year ago
Created attachment 8917146 [details] [review]
pull request
(Assignee)

Updated

a year ago
Attachment #8917146 - Flags: feedback?(mtabara)
Comment on attachment 8917146 [details] [review]
pull request

Made my comments in the PR.
Attachment #8917146 - Flags: feedback?(mtabara) → feedback+
(Assignee)

Comment 4

a year ago
I'm going to close this bug but mark 1400015 (optimize merge day environment as blocking 1398909 (staging releases tracking bug) to address the issues in comment #1 above
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.