Open
Bug 1868468
Opened 2 years ago
Updated 6 months ago
Uplift automation is developer intensive for uplifts of the same patch to multiple branches at the same time
Categories
(Conduit :: General, defect, P3)
Conduit
General
Tracking
(Not tracked)
NEW
People
(Reporter: standard8, Unassigned)
References
(Blocks 1 open bug)
Details
The new automation looks to be developer intensive for uplifts of the same patch to multiple branches.
Current Bugzilla workflow:
- If no bitrot is needed: go to Bugzilla, enter attachment view, select multiple uplift requests and fill in the form a maximum of twice (once for beta/release, the other for ESR).
- If bitrot is needed: upload new patch & fill in attachment view.
- Typically I've only ever needed one different patch per bug.
New workflow:
- Regardless of if bitrot exists:
- Run
moz-phab upliftthree times. - Do this three times: Go to phabricator page, select the request uplift, fill in form.
- Run
Whilst I realise this is not a frequent action, I can see it being repetitive work intensive especially to have to go into phab multiple times and fill in forms on different pages (especially when dealing with incidents).
Comment 1•1 year ago
|
||
This is a pain point we are aware of with the new workflow. I have plans to add the ability to submit uplift for multiple branches at once via Lando, and we will also add this capability to moz-phab.
Severity: -- → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•