1262002 - Consider adding `push-to-try` to mach mercurial-setup

Status: RESOLVED WORKSFORME

(Developer Services :: Mercurial: mozext, defect)

Description

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

According to Margaret, it's not set up automatically:
  https://mail.mozilla.org/pipermail/mobile-firefox-dev/2016-April/001934.html

And that surprised me!

Greg, any thoughts?

Comment 1

[Gregory Szorc [:gps]]

`mach try` should be used for Try pushes. It works with Mercurial and Git.

Unfortunately, it uses `hg push-to-try` under the hood. We should definitely prompt to add `hg push-to-try` to `mach mercurial-setup`. Or, we should have `mach try` try to find and load the push-to-try extension from a version-control-tools clone. I like the latter because it automagically works in cases where people have run `mach mercurial-setup`.

Comment 2

[Chris Manchester (limited bugmail, email directly)]

This is already a part of |./mach mercurial-setup| if you have mercurial 3.3 or above (only because that was the lowest version I had to test against).

I only wrote hg push-to-try for mach try, so it's a little odd to see it being used directly. By the way, |./mach try| has --save and --load flags that manage aliases, and a few other bells and whistles you might be interested in.

Comment 3

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Sounds like this is working as expected then.

Nice on `--save` & co. fwiw, I wrote a wrapper [1] so my team doesn't have to remember try syntax anymore (it runs all the useful Android tests). It'd be cool if we could somehow roll that functionality into `mach try` (e.g. globally available presets), but it sounds like a lot of work for little pay-off. :)

[1]: https://github.com/mcomella/push-to-try-android

Comment 4

[Gregory Szorc [:gps]]

mach config files just landed today. Seems like `mach try` could benefit from that ;)

Expect an announcement once the patches have merged to central.