Sheriffing/How To/Mobile Trees: Difference between revisions

extend communication channels and differences to desktop repositories
(add how to classify)
(extend communication channels and differences to desktop repositories)
Line 3: Line 3:
** Description: A collection of Android libraries to build browsers or browser-like applications.
** Description: A collection of Android libraries to build browsers or browser-like applications.
** Repository: [https://github.com/mozilla-mobile/android-components android-components] on GitHub
** Repository: [https://github.com/mozilla-mobile/android-components android-components] on GitHub
** Escalation channel: #android-components on Slack
** Escalation channel: [https://chat.mozilla.org/#/room/#android-components:mozilla.org android-components] (Matrix)
* [https://treeherder.mozilla.org/#/jobs?repo=fenix&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable fenix]
* [https://treeherder.mozilla.org/#/jobs?repo=fenix&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable fenix]
** Description: Android browser "Firefox Preview" - codename "Fenix"
** Description: Android browser "Firefox Preview" - codename "Fenix"
Line 11: Line 11:
** Description: browser based on android-components intended to test those. It's not a product for end users.
** Description: browser based on android-components intended to test those. It's not a product for end users.
** Repository: [https://github.com/mozilla-mobile/reference-browser reference-browser] on GitHub
** Repository: [https://github.com/mozilla-mobile/reference-browser reference-browser] on GitHub
** Escalation channel: #android-components on Slack
** Escalation channel: [https://chat.mozilla.org/#/room/!nzmqfSxszBNCPTXRYz:mozilla.org reference-browser] (Matrix)
 
Other communication channels:
* [https://chat.mozilla.org/#/room/#mobile-test-eng:mozilla.org mobile-test-eng] (Matrix): questions about issues with test tasks and tests
* #releaseduty-mobile (Slack): For problems with release tasks like cron, decision or signing tasks
* [https://chat.mozilla.org/#/room/#perftest:mozilla.org perftest]: For issues with performance tasks like Raptor


===Differences to autoland and mozilla-central===
===Differences to autoland and mozilla-central===
* If a task shall run once more, this must be done from "Custom Actions" > "rerun"
* If a task shall run once more, this must be done from "Custom Actions" > "rerun".
* Code sheriffs don't perform backouts or close trees but escalate to developers/teams to get issues fixed.
* Failures are tracked in multiple tools
* Failures are tracked in multiple tools
** Raptor failures in Bugzilla's [https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Raptor Testing :: Raptor] component
** Raptor failures in Bugzilla's [https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Raptor Testing :: Raptor] component
Line 20: Line 26:
** Non-Raptor test failures shall be reported into the Github repository mentioned above.
** Non-Raptor test failures shall be reported into the Github repository mentioned above.
** Test results are often stored externally and not in the log.
** Test results are often stored externally and not in the log.
*** In these cases, Treeherder cannot provide failure suggestions.


===Accessing the test results===
===Accessing the test results===
Confirmed users
604

edits