1408204 - Honor client.py repository defaults in automation.

Status: RESOLVED FIXED

(Thunderbird :: Build Config, defect)

Description

[Tom Prince [:tomprince]]

client.py tries to guess the remote mozilla repository to update from based on where an existing repository was already cloned from. This makes sense when it is being run locally. But when run on buildbot (on try-comm-central for example), the configuration in client.py should honored, rather than whatever repository happened to have been cloned there last.

Comment 1

[Tom Prince [:tomprince]]

Attachment: Bug 1408204: Always use MOZILLA_REPO from client.py in automation.

Review commit: https://reviewboard.mozilla.org/r/188938/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/188938/

Comment 2

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

Comment on attachment 8918044 [details]
Bug 1408204: Always use MOZILLA_REPO from client.py in automation.

https://reviewboard.mozilla.org/r/188938/#review194410

Stealing the review here since Joshua is usually quite busy, r=philipp

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/4dd3dca99031
Always use MOZILLA_REPO from client.py in automation; r=Fallen DONTBUILD CLOSED TREE

Comment 4

[Tom Prince [:tomprince]]

This would be useful to backport to comm-beta and comm-esr52, to make it easier to run try builds against them.

Comment 5

[Jorg K (CEST = GMT+2)]

Comment on attachment 8918044 [details]
Bug 1408204: Always use MOZILLA_REPO from client.py in automation.

Sure. The simple way is to request uplift against the patch or review request and I'll take care of it.

Comment 6

[Jorg K (CEST = GMT+2)]

Comment on attachment 8918044 [details]
Bug 1408204: Always use MOZILLA_REPO from client.py in automation.

Without a target, no query ever found this bug :-(