Just an FYI – I copied this info to the wiki: https://wiki.mozilla.org/Mobile/Fennec/Testing/Understanding_treeherder#Automatic_tasks - Mike
On Mon, May 9, 2016 at 9:44 AM, Michael Comella <michael.l.come...@gmail.com > wrote: > Hey Android devs. > > There are a few tasks on treeherder that run automatically when files > change that can affect the task results [1]. One side effect of allowing > tasks to run automatically is that you can't get them to run without > changing the files, *even if you explicitly include the task.* This is > unexpected behavior to me and I don't know if it will ever change. If you > need to force one of these tasks to run on try, you can change a file you'd > expect to have to change in order to run the task and delete the commit > after you push (e.g. to get checkstyle to run, you can change a Java by > adding valid code, e.g. `int i = 4`; to any method). > > Specifying the files that cause tasks to run is a manual process (e.g. > [2]) and can go wrong, so please let me know if one of these tasks does not > run when you'd expect it to and we can update the script. > > As a front-end dev, I think the only task you'll need to regularly specify > now is robocop. > > Also, I renamed "android-api-15-frontend" to "android-test" [3], which is > the unit test job, and it runs automatically. It's name is correlated with > the local command: `./mach gradle test` > - Mike (:mcomella) > > [1]: android-lint, android-checkstyle, android-test, > android-api-15-gradle-dependencies > > [2]: > https://dxr.mozilla.org/mozilla-central/rev/e5a10bc7dac4ee2453d8319165c1f6578203eac7/testing/taskcluster/tasks/branches/base_jobs.yml#430 > [3]: https://bugzilla.mozilla.org/show_bug.cgi?id=1260874 >
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
