Hi!

(Replies to dev.tree-management please)

The A-Team's Treeherder project [1] has completed its next milestone: The sheriff team [2] is now using it to monitor repository code health instead of TBPL [3].

A massive thanks to all of the developers [4] who have worked hard [5] to get us to this point - but in particular mdoglio, camd, jeads & jfrench.

What this means for you:

* TBPL will remain operational for approx the next quarter (until papercuts and non-sheriff use-cases are fixed), so don't worry if you would prefer not to switch immediately. * Treeherder "failure classifications" (previously "star" comments) are one-way mirrored to TBPL, so TBPL users will still benefit from the sheriffs' classifications. * If you maintain a tool that uses TBPL's API, you will need to transition it to Treeherder's API - please file a bug blocking bug 1054977 asap so it is on our radar. * If you own non-buildbot jobs that report to treeherder - they are not automatically being sheriffed, since each will need to be assessed against the job visibility policy first [6] (which will likely need revising to reflect the non-buildbot world).

Useful links:

* Example treeherder page:
https://treeherder.mozilla.org/ui/#/jobs?repo=mozilla-inbound
* File a bug:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Tree+Management&component=Treeherder
* Source/docs, roadmap, bug tables & good first bugs:
https://wiki.mozilla.org/Auto-tools/Projects/Treeherder

Best wishes,

Ed

[1] https://wiki.mozilla.org/Auto-tools/Projects/Treeherder
[2] https://wiki.mozilla.org/Sheriffing
[3] https://tbpl.mozilla.org
[4] https://github.com/mozilla/treeherder-service/graphs/contributors
    https://github.com/mozilla/treeherder-ui/graphs/contributors
[5] https://bugzilla.mozilla.org/showdependencytree.cgi?id=1030636&hide_resolved=0
[6] https://wiki.mozilla.org/Sheriffing/Job_Visibility_Policy
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to