canmove, Confirmed users
1,126
edits
Auto-tools/Projects/OrangeFactor: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Projects/OrangeFactor (view source)
Revision as of 13:39, 23 October 2014
, 23 October 2014Update bug links after component move & rename "War on Orange" + "Orange Factor" to "OrangeFactor"
m (Edmorley moved page Auto-tools/Projects/WarOnOrange to Auto-tools/Projects/OrangeFactor: Renaming to the actual name of the webapp) |
(Update bug links after component move & rename "War on Orange" + "Orange Factor" to "OrangeFactor") |
||
| Line 1: | Line 1: | ||
== Status == | == Status == | ||
The [http://brasstacks.mozilla.com/orangefactor/ | The [http://brasstacks.mozilla.com/orangefactor/ OrangeFactor] web app provides a variety of ways to view data on buildbot orange failures. File bugs under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Tree+Management&component=OrangeFactor Tree Management::OrangeFactor]. | ||
We were taking [[Auto-tools/Projects/ | We were taking [[Auto-tools/Projects/OrangeFactor/Meetings|minutes of meetings]] early on in the project, but since then we are tracking features and bugs in [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&component=OrangeFactor&product=Tree+Management Bugzilla]. | ||
For an overview, see [http://people.mozilla.com/~mcote/war-on-orange/war-on-orange-paper-testistanbul.pdf this paper] and the accompanying [http://people.mozilla.com/~mcote/war-on-orange/war-on-orange-testistanbul-slides-presentation.pdf slides], prepared for the TestIstanbul 2012 conference. | For an overview, see [http://people.mozilla.com/~mcote/war-on-orange/war-on-orange-paper-testistanbul.pdf this paper] and the accompanying [http://people.mozilla.com/~mcote/war-on-orange/war-on-orange-testistanbul-slides-presentation.pdf slides], prepared for the TestIstanbul 2012 conference. | ||
| Line 19: | Line 19: | ||
== History == | == History == | ||
These projects are deprecated and replaced by the new War on Orange/ | These projects are deprecated and replaced by the new War on Orange/OrangeFactor application. | ||
'''Topfails''' | '''Topfails''' | ||
| Line 33: | Line 33: | ||
source: http://github.com/jmaher/Orange-Factor | source: http://github.com/jmaher/Orange-Factor | ||
[[Auto-tools/Projects/ | [[Auto-tools/Projects/OrangeFactor/InstallationInstructions|Installation instructions]] | ||
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&component= | [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&component=OrangeFactor&product=Tree+Management bugs] | ||
== Architecture == | == Architecture == | ||
| Line 55: | Line 55: | ||
=== Development & Deployment === | === Development & Deployment === | ||
The | The OrangeFactor web app can be run locally. See the instructions at: | ||
https://hg.mozilla.org/automation/orangefactor/file/tip/README.txt | https://hg.mozilla.org/automation/orangefactor/file/tip/README.txt | ||
| Line 71: | Line 71: | ||
* identify interesting patterns in failures; some failures may occur more frequently on certain OS's, build types, architectures, or other factors; by providing views which can track oranges across a range of factors, we might be able to provide developers with data that would help them reproduce failures or give them insight into their cause | * identify interesting patterns in failures; some failures may occur more frequently on certain OS's, build types, architectures, or other factors; by providing views which can track oranges across a range of factors, we might be able to provide developers with data that would help them reproduce failures or give them insight into their cause | ||
* identify overall trends in orange occurrences, already part of [http://jmaher.couchone.com/orange_factor/_design/woo/orange.html Orange Factor]; this can help track the 'orangeness' of a product over time, and can help measure the helpfulness of orange-fixing activities | * identify overall trends in orange occurrences, already part of the [http://jmaher.couchone.com/orange_factor/_design/woo/orange.html legacy Orange Factor app]; this can help track the 'orangeness' of a product over time, and can help measure the helpfulness of orange-fixing activities | ||
== Dashboard Views == | == Dashboard Views == | ||
A list of dashboard views that may be interesting. We're currently using | A list of dashboard views that may be interesting. We're currently using OrangeFactor as a platform to experiment with views. | ||
* {{done|display}} of overall orange factor over time | * {{done|display}} of overall orange factor over time | ||
| Line 89: | Line 89: | ||
The amount of information yielded from the parsed logs is vast. The raw data will be noisy and the trends will not be easily discerned. So statistical analysis should be used to manipulate the data and seek insight into trends. | The amount of information yielded from the parsed logs is vast. The raw data will be noisy and the trends will not be easily discerned. So statistical analysis should be used to manipulate the data and seek insight into trends. | ||
[[Auto-tools/Projects/ | [[Auto-tools/Projects/OrangeFactor/Statistics|War On Orange Statistics]] | ||
== How Tinderbox Stores Its Data == | == How Tinderbox Stores Its Data == | ||
| Line 125: | Line 125: | ||
== ElasticSearch Queries == | == ElasticSearch Queries == | ||
The log metadata is all stored in ElasticSearch, see the [[Auto-tools/Projects/ | The log metadata is all stored in ElasticSearch, see the [[Auto-tools/Projects/OrangeFactor/ElasticSearch|ElasticSearch]] page for details on querying this database. | ||
== Attacking Oranges == | == Attacking Oranges == | ||