Confirmed users
753
edits
Outreachy: Difference between revisions
Jump to navigation
Jump to search
Added Treeherder
(→Outreachy Program Cohort: Round 15 (December 2017 - March 2018): added project) |
(Added Treeherder) |
||
| Line 93: | Line 93: | ||
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/history history] - interaction with the users browser history | *[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/history history] - interaction with the users browser history | ||
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/omnibox omnibox] - shortcuts in the browser address bar | *[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/omnibox omnibox] - shortcuts in the browser address bar | ||
=== Treeherder === | |||
Mentor: Ed Morley and Cameron Dawson | |||
IRC: emorley or camd | |||
Overview: | |||
Treeherder is the web application for visualising continuous integration tasks used to build and test Firefox. Treeherder processes a lot of data everyday to be able to visualise this data.It's used by Firefox devs to check whether their new code works, by release managers to decide whether to include a new feature in the next version of Firefox. | |||
Inside this data we have a number of failures that occur and are intermittent making it difficult to track and reproduce: “When a developer tests out code, they want to know: | |||
Did my code cause any regressions?” Currently this can be difficult to figure out. | |||
We need to start building up metrics on these to help engineering teams know which intermittent failures are important and which are not. | |||
You will be working on one of the following: | |||
* Visualising intermittents and their regularity | |||
** Create a frontend to visual historical trends of failures with creative ways to browser and compare. This will be used by developers and sheriffs who are trying to fix these failures. | |||
** building a user interface inside of Treeherder for annotating/matching failures | |||
** Create a backend for storing unique identifiers for failures which will be referenced by an auto classification engine, the frontend for annotating, and the historical view for finding trends | |||
* Build out auto-classification tooling to be able to handle more types of intermittent failure types. | |||
** Create an engine that will automatically match failures and annotate them properly | |||
building a user interface inside of Treeherder for annotating/matching failures | |||
You will need to know a little bit of the following and learn the rest as you go: | |||
* Python | |||
* JavaScript (For using React or AngularJS) | |||
* HTML/CSS | |||
==Outreachy Program Cohort: Round 14 (May 30 -Aug 30, 2017)== | ==Outreachy Program Cohort: Round 14 (May 30 -Aug 30, 2017)== | ||