canmove, Confirmed users
1,126
edits
Sheriffing/Job Visibility Policy: Difference between revisions
Jump to navigation
Jump to search
m
→The future: Add missing parens
m (→8) Must avoid patterns known to cause non deterministic failures: Fix whitespace) |
m (→The future: Add missing parens) |
||
| Line 79: | Line 79: | ||
* Planned improvements to our tooling will likely mean that some of these requirements can be relaxed in the future, as well as making it easier for maintainers of non-default-view job types to track their success/failure without having to monitor TBPL continuously. | * Planned improvements to our tooling will likely mean that some of these requirements can be relaxed in the future, as well as making it easier for maintainers of non-default-view job types to track their success/failure without having to monitor TBPL continuously. | ||
* The successor to TBPL ([[Auto-tools/Projects/TBPL2]]) will support: | * The successor to TBPL ([[Auto-tools/Projects/TBPL2]]) will support: | ||
** Multiple dashboards/views for different use cases/teams (giving us more flexibility than just "default | ** Multiple dashboards/views for different use cases/teams (giving us more flexibility than just "default view" or "&showall=1"). | ||
** Opt-in notifications (email, IRC, dashboard, ...?) of failures for desired job types (see proposal in {{bug|851061}}). | ** Opt-in notifications (email, IRC, dashboard, ...?) of failures for desired job types (see proposal in {{bug|851061}}). | ||
* [[Auto-tools/Projects/Bisect_in_the_cloud]] will allow sheriffs to more easily narrow regression ranges for job types that do not run on every push, making it more viable to accept them into certain views/dashboards. | * [[Auto-tools/Projects/Bisect_in_the_cloud]] will allow sheriffs to more easily narrow regression ranges for job types that do not run on every push, making it more viable to accept them into certain views/dashboards. | ||