On 26/03/14 09:06 AM, Andrew Halberstadt wrote:
On 26/03/14 12:19 AM, Gregory Szorc wrote:
Andrew: I'm curious if you or anyone else has given any consideration
into making it dead simple to change the config so only a subset of
tests will be active. e.g. I'd like to save automation resources and
filter my browser chrome jobs to tests under toolkit/mozapps/extensions.
This is now possible but requires modifying N config files under
testing/config/mozharness. Could we get that down to 1 or added to Try
syntax somehow?
Releng (and I tend to agree with them) is very opposed to having one
config affect multiple platforms (or at least multiple buildapps). Over
time it tends to lead to messy and hard to follow configs. It also makes
it harder in the case that you *do* only want to change a single platform.
Another more practical reason for not doing this is that often different
platforms have vastly different command lines (e.g b2g vs firefox vs
fennec are all different). I can't really think of an intuitive way that
lets us share common command lines while having different sets of
configs for the uncommon ones. IMO editing N configs isn't that big of a
deal.. but if you really wanted to on a project branch or something, I
suppose you could create a "global" config and have the platform
specific ones import it. If this scheme was sane and easy to understand,
I could possibly be convinced to land it on m-c.
Andrew
To follow up, I wouldn't be opposed to having an empty global config
that is just there to make pushing to try easier but is not used on
production branches.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
