Closed Bug 1612191 Opened 6 months ago Closed 5 months ago

Make it easy to bump browsertime version/URL

Categories

(Testing :: Performance, enhancement, P1)

Version 3
enhancement

Tracking

(firefox75 fixed)

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: nalexander, Assigned: sparky)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

While capturing documentation for the "bump browsertime version pin" flow, I thought I would automate a small part of it to avoid having *nix and Windows specific documentation sections.

Priority: -- → P2

I couldn't find an exact version for the introduction of the flag, but
it appears to be at least NPM v3. We recently started to install and
require at least NPM v6.13.4 in tree.

Assignee: nobody → nalexander
Status: NEW → ASSIGNED

Might as well automate what we can automate. I considered making the
"update package.json" logic part of setup_helper.py, so that it can be
used more broadly, but it's not clear it would be used with the
general push towards vendoring into the tree as part of mach vendor.

Depends on D63370

Greg: I forgot I started on this work but maybe we want it. Commandeer these if you want them? Otherwise, unset the review flags? (I left them up so you'd loop Mark Banner in on the discussion.) Mark, this could pave the way to this type of bumping more generally.

Comment above, Greg ^

Flags: needinfo?(gmierz2)

Thanks :nalexander! I'll commandeer them and continue from where you left off.

Flags: needinfo?(gmierz2)
Assignee: nalexander → gmierz2
Priority: P2 → P1
Pushed by gmierz2@outlook.com:
https://hg.mozilla.org/integration/autoland/rev/f05648a37233
Pre: Use NPM's --scripts-prepend-node-path rather than setting PATH. r=Standard8
https://hg.mozilla.org/integration/autoland/rev/ee8364efc64c
Implement `mach browsertime --update-upstream-url $URL` for bumping version. r=Standard8,tarek
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
Blocks: 1642964
You need to log in before you can comment on or make changes to this bug.