Hello all, It is now less hard to run mozharness locally by appending --cfg developer_config.py to production commands.
Appending the config will activate a developer mode which does the following: * Remove hard coded paths for binaries * Substitute internal URLs to point to externally reachable URLs * Add Http authentication to reach private files * It also enforces the use of --test-url and --installer-url You can read more about it in here: http://armenzg.blogspot.ca/2014/09/run-tbpl-jobs-locally-with-http.html This allowed me to not have to request a Releng loaner to reproduce a job run on tbpl. I know that this is not the holy grail but it helps to ease the pain. What would people want to see in the long term to make mozharness easier for you? I've considered writing a mach command to which we can pass a URL to a log and does all the thinking for us. Another project that I believe would be useful is to allow a developer to point mozharness at local binaries. I know it is possible but I have not documented it since I have not tested it. There's also the project of making mach deal with mozharness the same way that we have mach support for talos (which is using mozharness in the back). regards, Armen _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
