412347 - Support building from an alternate revision/branch/tag in a mercurial based try server build

Status: RESOLVED FIXED

(Release Engineering :: General, enhancement, P5)

Description

[Dave Townsend [:mossop]]

When you do a try server build from a mercurial repository I presume it builds from the tip of the repository. This is inconvenient to me, I keep multiple named branches in my repository, one for each main bug I am working on. It would be able to useful to tell the try server to build from a given branch.

This should just be as simple as adding a new string entry field to the form and then if filled in, after pulling issuing a |hg update -C <value>|. Value can be a node hash, tag or branch (might be worth noting that people may get expected results if they use their local revision number here).

Comment 1

[[e-mail] (:bhearsum)]

Moving try server bugs to the new component.

Comment 2

[[e-mail] (:bhearsum)]

Mass change of target milestone.

Comment 3

[Karl Tomlinson (:karlt)]

This would be very useful for perf regression hunting like bug 450401.

The form already contains a Branch/Tag field, but it does not appear to have any effect.

Comment 4

[Benjamin Smedberg]

Are you sure it doesn't work? I've tried and it WFM in the past...

Comment 5

[[e-mail] (:bhearsum)]

Looks like this is still true

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I just requested a build of http://hg.mozilla.org/releases/mozilla-1.9.1/ from the FIREFOX_3_1b3_RELEASE tag, and I got one of the tip of the repo instead.  So this still doesn't work.

Comment 8

[Chris Cooper [:coop] (he/him)]

Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.

Comment 9

[Aki Sasaki (not active)]

Is push-to-try an acceptable enough workaround to close this bug (now that cvs based builds are gone)?

Comment 10

[Aki Sasaki (not active)]

(i guess this bug specifically states mercurial-based, so ignore the above parentheteses)

Comment 11

[Karl Tomlinson (:karlt)]

AFAIK, now that we only have push-to-try (no patch upload), the tip pushed will be on the appropriate branch and so the appropriate revision will be built.
So I assume this bug can be closed.

Comment 12

[Aki Sasaki (not active)]

Awesome.
Not sure which of the resolutions to use; this one seems fine.

Comment 13

[Randell Jesup [:jesup] (needinfo me)]

This does appear to work correctly now; changing resolution to fixed