EngineeringProductivity/Projects/Treeherder/Current TBPL Feature List: Difference between revisions

Jump to navigation Jump to search
Next rev
(Initial version)
 
(Next rev)
Line 1: Line 1:
*Current Features*
==Menus==
==Menus==
===Help menu===
===Help menu===
Line 42: Line 40:
** Commit message
** Commit message
* Checkboxes for using talos-compare
* Checkboxes for using talos-compare
* Link to m-cMerge (on hover). Ideally would host m-cMerge on mozilla property (or even in TBPL)  
* Link to m-cMerge (on hover). Ideally would host m-cMerge on a Mozilla property (or even in TBPL).
* Link to BuildAPI (on hover). BuildAPI requires LDAP.
* Link to BuildAPI (on hover). BuildAPI requires LDAP.
* Cancel all pending/running jobs on push (on hover)
* Cancel all pending/running jobs on push (on hover)
Line 48: Line 46:
* Build/Test results:
* Build/Test results:
** Each OS/type of build on own row. Not every push may build everything (or at all)
** Each OS/type of build on own row. Not every push may build everything (or at all)
** Currently matches builtbot "buildername" against a tangled mess of regex in the UI to determine which jobs belong on which row, what letter represents which job type & which job types should be grouped in parenthesis).  
** Currently matches buildbot "buildername" against a tangled mess of regex in the UI to determine which jobs belong on which row, what letter represents which job type & which job types should be grouped in parenthesis).  
** Jobs can be pending (light grey), running (dark grey) or completed (colour depends on result).
** Jobs can be pending (light grey), running (dark grey) or completed (colour depends on result).
** Completed job results map to the standard buildbot result states (success, warnings, failure, exception, retry) [note soon to be 'cancelled' too, once buildbot updated from upstream]).
** Completed job results map to the standard buildbot result states (success, warnings, failure, exception, retry) [note soon to be 'cancelled' too, once buildbot updated from upstream]).
Line 82: Line 80:
==Leak analyser==
==Leak analyser==
* Linked from the annotated summary for leaks
* Linked from the annotated summary for leaks
* **TODO**
* Uses the ++DOMWINDOW/--DOMWINDOW and TEST-START etc entries in the log to work out during which test the leak occurred. Only semi-reliable.


==Reftest analyser==
==Reftest analyser==
Line 117: Line 115:
* If "hidden" jobs (ie hidden in buildername admin) should be shown (*no UI for this currently, devs have to remember parameter)
* If "hidden" jobs (ie hidden in buildername admin) should be shown (*no UI for this currently, devs have to remember parameter)
* Pusher name filter
* Pusher name filter
* Embed mode * **TODO**
* Embed mode (hides menu bar - for use by the Bugzilla Tweaks Firefox addon, which displays people's TryServer results inline in their bug).


==Misc==
==Misc==
* Page title contains number of unstarred failing jobs, therefore when there are new failures that need investigating/starring, the tab title changes and thus turns the pinned tab blue.
* Page title contains number of unstarred failing jobs, therefore when there are new failures that need investigating/starring, the tab title changes and thus turns the pinned tab blue.
canmove, Confirmed users
1,126

edits

Navigation menu