Dear Rob,
Thank you for looking into this.
Nowadays, |mach ...| command seems to be used for everything, and
without the standalone TryChooser web page, it is hard to figure out what
strings I need to pass to comm try server for some specific build request.
So having a better integration of
|../mach| command with C-C is definitely nice.
(As I mentioned suggested |mach try {chooser|fuzzy}| invokes |mach try|
directly which is not desirable at this moment for C-C patch contributors.)
Since C-C is now a subdirectory ./comm under M-C, I think we need to
refer to it as |../mach| to invoke it inside ./comm directory.
A bit complicated, but I use it to build C-C tree locally. At least, local
build works with |../mach|.
Thank you again.
Chiaki
PS: I wish a simple web page or even a simple standalone command for
obtaining the trychooser string will be very handy until C-C can work with
|mach try|.
Or does it work? I see a couple of submissions in treeherder where I do not
see explicit passing of TryChooser string. Hmm...
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=c4f1d2a2e2acb8c2acaf6996fdc9947613b4a9c1
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=df8844eb9048ebd2e3e28a27f1deb39062d5fb7d
Aha, these are only meant for documentation change and no passing of
trychooser string is necessary? But then why the shippable opt build is
performed is beyond me. Maybe in the absence of trychooser string, such
build is the default action? (We need some documentation somewhere about this.)
On 2019/08/30 6:01, Rob Lemley wrote:
> "mach try" doesn't work with comm-* repos. I'm not sure why. I can take
> a look again and see if I can figure it out.
>
> -Rob
>
> On 8/29/19 3:19 PM, ISHIKAWA,chiaki wrote:
>> (Hmm... I don't see the post I created about 15 minutes ago or so.)
>>
>> Just a quick note: I am submitting jobs for TB TryServer and
>> the manner I submit the job is directly invoking
>> |hg push| currently.
>>
>> I am not sure if |mach try {chooser|fuzzy}| can be used nicely.
>>
>> Excerpt from my local script to submit a comm-central tryserver job.
>>
>> # The aforementioned tools may not play all that nicely with
>> mercurial queues. If you use mq, you can still push to try manually.
>> First build your try syntax with the TryChooser web page. Then run:
>> # $ hg qref --message "try: <your-computed-syntax-here>"
>> # $ hg push -f try
>>
>> hg push -f ssh://hg.mozilla.org/try-comm-central
>>
>>
>> So in a sense, I needed a separate tool that simply prints the
>> required string for trychooser.
>>
>> I checked and found that
>> |mach try chooser| and |mach try fuzzy| seems to
>> invoke |mach| command automatically upon completion, which is
>> unfortunately not desirable in my case.
>>
>> I wonder if I can issue |../mach try {chooser|fuzzy}| under ./comm
>> directory. (C-C is now a subdirectory).
>> I am adding dev-apps-thunderbird mailing list in CC: field.
>>
>> Chiaki
>>
>>
>> On 2019/08/30 2:13, Barret Rennie wrote:
>>> (resending since I didn't cc the list)
>>>
>>> Hi
>>>
>>> From my understanding, the releng-hosted try chooser pages were
>>> deprecated for a long time and have been retired since they were out
>>> of date for the available jobs.
>>>
>>> You will want to use `mach try chooser` (which brings up a webpage)
>>> or `mach try fuzzy` (which uses a terminal fuzzy finder) to select jobs.
>>>
>>> For example you can run:
>>>
>>> mach try fuzzy -q "'build"
>>>
>>> to run all build tasks, or
>>>
>>> mach try fuzzy -q "'build-linux64"
>>>
>>> to only build Linux 64 versions.
>>>
>>> For full details for mach try fuzzy syntax, check out
>>> https://github.com/junegunn/fzf which is what it uses under the hood.
>>>
>>> Hope this helps,
>>> Barret
>>>
>>> On Thu., Aug. 29, 2019, 13:07 ISHIKAWA,chiaki, <ishik...@yk.rim.or.jp
>>> <mailto:ishik...@yk.rim.or.jp>> wrote:
>>>
>>> Hi,
>>>
>>> There is something wrong with the way the (updated?) documents for
>>> TryServer, specifically links to TryChooser.
>>> I can't find the relevant page(s).
>>>
>>> I start with TryServer page:
>>>
>>> https://wiki.mozilla.org/ReleaseEngineering/TryServer
>>>
>>> I want to access TryChooser document (to figure out how I can only
>>> compile and no test on the tryserver).
>>>
>>> There are a few "Build:TryChooser" phrase with the underlying URL.
>>> *HOWEVER*, they all link back to the current document in the
>>> second step.
>>> I click on "Build:TryChooser" and end up with the following page.
>>>
>>>
>>> https://wiki.mozilla.org/index.php?title=ReleaseEngineering/TryChooser&redirect=no
>>>
>>> You see it links back to the original TrySever page I started
>>> with in
>>> the first place.
>>>
>>> I look further for TryChooser in the original page.
>>>
>>> Then I find the link in the "See Also" section.
>>>
>>> https://mozilla-releng.net/trychooser/
>>>
>>> However, this link is broken.
>>> When I click on the page, I get "Page Not Found" response.
>>>
>>> Hmm...
>>>
>>> TIA
>>>
>>> Chiaki
>>>
>>>
>>> _______________________________________________
>>> dev-builds mailing list
>>> dev-builds@lists.mozilla.org <mailto:dev-builds@lists.mozilla.org>
>>> https://lists.mozilla.org/listinfo/dev-builds
>>>
>>
>> _______________________________________________
>> dev-apps-thunderbird mailing list
>> dev-apps-thunderb...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
>
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
