cdf6e976c0c03b8cc8cf4c91d8fd17e4b9f8c502: Bug 1235097 - Add support for overriding the site root
Ed Morley <emorley@mozilla.com> - Tue, 09 Feb 2016 11:42:53 +0000 - rev 303
Push 260 by emorley@mozilla.com at Tue, 09 Feb 2016 11:43:13 +0000
Bug 1235097 - Add support for overriding the site root On brasstacks, `web.ctx.home` is incorrect (see bug 1235097 comment 23), which means that the URL used by mohawk to verify the authenticated request hashes differs from that used to generate the hash. This new preference allows the site root to be overriden with the correct value, using `orangefactor_local.conf`. On brasstacks this needs to be: `custom_site_root = https://brasstacks.mozilla.com/orangefactor` This cannot be set in orangefactor.conf directly since otherwise requests would fail when testing the server locally using woo_server.py.
2e22e266428eaf727e28df001e9bb82a03baa410: Bug 1235097 - Re-add accidentally removed import
Ed Morley <emorley@mozilla.com> - Mon, 08 Feb 2016 17:34:07 +0000 - rev 302
Push 259 by emorley@mozilla.com at Mon, 08 Feb 2016 17:34:14 +0000
Bug 1235097 - Re-add accidentally removed import
f120e0d57c084243f026299e798bddb1074081e2: Bug 1235097 - Set up logging to help debug auth issues
Ed Morley <emorley@mozilla.com> - Mon, 08 Feb 2016 17:23:46 +0000 - rev 301
Push 258 by emorley@mozilla.com at Mon, 08 Feb 2016 17:26:05 +0000
Bug 1235097 - Set up logging to help debug auth issues
f50d897a9638e61c70aaa47d2ea5b62ff61c48ba: Bug 1235097 - Add an API endpoint that allows submitting to Elasticsearch
Ed Morley <emorley@mozilla.com> - Mon, 08 Feb 2016 10:46:22 +0000 - rev 300
Push 257 by emorley@mozilla.com at Mon, 08 Feb 2016 13:51:01 +0000
Bug 1235097 - Add an API endpoint that allows submitting to Elasticsearch Elasticsearch isn't publicly accessible, so once Treeherder moves to Heroku, we need a way for it to be able to still post new failure classifications to it. As such, this adds an API endpoint (`/api/saveclassification`) that forwards the body of POSTs to the endpoint, to Elasticsearch. Authentication is implemented using the Hawk authentication scheme: https://mohawk.readthedocs.org/en/latest/usage.html#receiving-a-request The POST to Elasticsearch is roughly a port of this Treeherder code: https://github.com/mozilla/treeherder/blob/9c80f8b8850a09a35e6d64066d7f29de124fa9ba/treeherder/etl/classification_mirroring.py#L65-L76 For web.py docs (which aren't great unfortunately), see http://webpy.org/ Once this lands, the Treeherder submission code linked above will be adjusted to instead POST to this new OrangeFactor API.
effe61195b1d224f0a75426e44687e2ddab3ae74: Bug 1240669 - Update requests to v2.9.1 and add requests[security] packages
Ed Morley <emorley@mozilla.com> - Tue, 19 Jan 2016 16:02:19 +0000 - rev 299
Push 256 by emorley@mozilla.com at Tue, 19 Jan 2016 16:02:39 +0000
Bug 1240669 - Update requests to v2.9.1 and add requests[security] packages Since brasstacks is running Python 2.6, and for anything older than 2.7.9, we need the additional ssl packages for improved security.
b16494043881b9dcc137ab7eec884437f3db4ce1: Bug 1240669 - Make woo_commenter.py output a message when the job is complete
Ed Morley <emorley@mozilla.com> - Tue, 19 Jan 2016 16:01:18 +0000 - rev 298
Push 256 by emorley@mozilla.com at Tue, 19 Jan 2016 16:02:39 +0000
Bug 1240669 - Make woo_commenter.py output a message when the job is complete To make it easier to tell from the logs whether it failed halfway through.
b4cb0125a0f6fc8d1483214245685bf55a00c914: Bug 1239195 - Add b2g-emu-x86-kk to UI platforms filter
Ed Morley <emorley@mozilla.com> - Tue, 19 Jan 2016 15:59:09 +0000 - rev 297
Push 256 by emorley@mozilla.com at Tue, 19 Jan 2016 16:02:39 +0000
Bug 1239195 - Add b2g-emu-x86-kk to UI platforms filter
6573ddfb695c1b5f0ca617c8095a11b3993c913c: Bug 1234457 - Remove references to auto-tools mailing list
William Lachance <wlachance@mozilla.com> - Tue, 22 Dec 2015 16:28:33 -0500 - rev 296
Push 255 by wlachance@mozilla.com at Tue, 22 Dec 2015 21:28:57 +0000
Bug 1234457 - Remove references to auto-tools mailing list
53d63e91c028ab1754d24bebdb872b2ae9c7ff67: Bug 1228069 - Validate startday and endday params to avoid XSS
Ed Morley <emorley@mozilla.com> - Thu, 26 Nov 2015 18:22:22 +0000 - rev 295
Push 254 by emorley@mozilla.com at Thu, 03 Dec 2015 17:34:33 +0000
Bug 1228069 - Validate startday and endday params to avoid XSS Eugh when can we EOL OrangeFactor already :-/
fa035a8d208eba9cb8a6bb8362f9eb11c22cd873: Bug 1212712 - Use HTTPS when referring to the production OrangeFactor URL
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Wed, 07 Oct 2015 21:48:00 +0100 - rev 294
Push 253 by emorley@mozilla.com at Fri, 09 Oct 2015 09:42:52 +0000
Bug 1212712 - Use HTTPS when referring to the production OrangeFactor URL
d54b7925c8c5df42e0537534ff8bb9ab811c7da5: Bug 1179821 - Set executable bit on woo_commenter.py
Ed Morley <emorley@mozilla.com> - Tue, 29 Sep 2015 00:02:13 +0100 - rev 293
Push 252 by emorley@mozilla.com at Mon, 28 Sep 2015 23:02:38 +0000
Bug 1179821 - Set executable bit on woo_commenter.py
48efd7034a4a3ab4829fda924728265ce27678d1: Bug 1179821 - Add a script that can post daily/weekly failure stats to bugs
Ed Morley <emorley@mozilla.com> - Mon, 28 Sep 2015 18:02:29 +0100 - rev 292
Push 251 by emorley@mozilla.com at Mon, 28 Sep 2015 22:42:20 +0000
Bug 1179821 - Add a script that can post daily/weekly failure stats to bugs This adds a script that will post either a daily or weekly failure summary to bugs whose total number of failures exceeded a threshold. For daily summaries, the threshold (at least for now) is 15 failures in the prior day, and for weekly summaries 5 failures in the prior week. The timeout for each bug comment submission is 30 seconds, and each comment submission will be retried up to 3 times. If that was still unsuccessful, the error will be output to the log, but the script will continue with the remaining bugs, to avoid an issue with one (eg the bug not existing or being a security bug) from taking down the whole script. To run in daily mode (the default): ./woo_commenter.py --test Weekly mode: ./woo_commenter.py --test --weekly Remove --test to actually comment on the bugs, rather than printing to stdout. Note: Even in --test mode, you will still need an API key specified in woo_cron.conf. This has intentionally not been worked around, so that --test can be used to validate as much of the production config after deployment as possible (apart from actually posting the bug comments). Example comment content: """ 7 automation job failures were associated with this bug in the last 7 days. Repository breakdown: * mozilla-central: 7 Platform breakdown: * osx-10-9: 3 * osx-10-10: 3 * osx-10-6: 1 For more details, see: http://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1206134&startday=2015-09-18&endday=2015-09-24&tree=all """
d7b7371a533f4834a2520bd25a919819c09f4b90: Bug 1179821 - Add support to TopBugs for overriding the choice of tree
Ed Morley <emorley@mozilla.com> - Fri, 25 Sep 2015 18:35:00 +0100 - rev 291
Push 251 by emorley@mozilla.com at Mon, 28 Sep 2015 22:42:20 +0000
Bug 1179821 - Add support to TopBugs for overriding the choice of tree The default remains 'trunk', but it can now be overridden. This will allow the bug commenter to run stats_by_bug() against trees='all' rather than just trunk.
838132d34cc5e1fac0c89773f6344f1ec5eaa509: Bug 1179821 - Add a method to woo_client.py that summarises failures by bug
Ed Morley <emorley@mozilla.com> - Fri, 25 Sep 2015 18:35:00 +0100 - rev 290
Push 251 by emorley@mozilla.com at Mon, 28 Sep 2015 22:42:20 +0000
Bug 1179821 - Add a method to woo_client.py that summarises failures by bug It returns the per-repository, per-platform and total failure counts for each bug that was seen in the current time window.
017b63e86565aff9e47eaad67da8c555aa1eece2: Bug 1179821 - Rename woo_mailer.conf to woo_cron.conf
Ed Morley <emorley@mozilla.com> - Fri, 25 Sep 2015 18:35:00 +0100 - rev 289
Push 251 by emorley@mozilla.com at Mon, 28 Sep 2015 22:42:20 +0000
Bug 1179821 - Rename woo_mailer.conf to woo_cron.conf Since both woo_mailer.py and the new bug commenter script will be using it, so the old name is no longer accurate. I'll rename the hg-ignored file on brasstacks when this is deployed.
240b6ebdf94d465c6597f910a815573e542ef990: Bug 1179821 - Break out the woo_mailer.py TopBugs class to woo_client.py
Ed Morley <emorley@mozilla.com> - Fri, 25 Sep 2015 18:35:00 +0100 - rev 288
Push 251 by emorley@mozilla.com at Mon, 28 Sep 2015 22:42:20 +0000
Bug 1179821 - Break out the woo_mailer.py TopBugs class to woo_client.py Since we'll want to use it for the bug commenter too.
e54d3fc6809a00b4ab2f881c0bd0fade0bb23c83: Bug 1195786 - Add extra debugging info in case this bug occurs again
Ed Morley <emorley@mozilla.com> - Tue, 22 Sep 2015 17:02:51 +0100 - rev 287
Push 250 by emorley@mozilla.com at Tue, 22 Sep 2015 16:03:10 +0000
Bug 1195786 - Add extra debugging info in case this bug occurs again The response from /api/bybug will be dumped to the log, which will make it easier to repro.
b58df1eb842b7be3c4b77277e0d2b7082734eb30: Bug 1195786 - Return HTTP 400 not 500 if no bugs passed to /api/bugdetails
Ed Morley <emorley@mozilla.com> - Tue, 22 Sep 2015 16:58:04 +0100 - rev 286
Push 250 by emorley@mozilla.com at Tue, 22 Sep 2015 16:03:10 +0000
Bug 1195786 - Return HTTP 400 not 500 if no bugs passed to /api/bugdetails This now returns HTTP 400 rather than 500: http://brasstacks.mozilla.com/orangefactor/api/bugdetails?bugid=
b582aa8a40e8073198776061398a8270c346a6dc: Bug 1195786 - Fix exception in woo_mailer.py and improve log formatting
Ed Morley <emorley@mozilla.com> - Tue, 22 Sep 2015 15:22:57 +0100 - rev 285
Push 249 by emorley@mozilla.com at Tue, 22 Sep 2015 14:24:06 +0000
Bug 1195786 - Fix exception in woo_mailer.py and improve log formatting Fixes: Traceback (most recent call last): File "woo_mailer.py", line 297, in <module> main() File "woo_mailer.py", line 210, in main top = tb.top_bugs()[:10] File "woo_mailer.py", line 71, in top_bugs jdata = self.get_bybug() File "woo_mailer.py", line 111, in get_bybug return self.get_bugdata('/bybug?tree=trunk&startday=%s&endday=%s' % (self.startday, self.endday)) File "woo_mailer.py", line 102, in get_bugdata print 'Getting bug data...' % url_path TypeError: not all arguments converted during string formatting
f7a627bcb6d6a7c61f9763f13b5db96935edec55: Bug 1180073 - Display the job start time in the UI, rather than just the date
Ed Morley <emorley@mozilla.com> - Thu, 10 Sep 2015 16:06:48 +0100 - rev 284
Push 248 by emorley@mozilla.com at Mon, 14 Sep 2015 10:17:05 +0000
Bug 1180073 - Display the job start time in the UI, rather than just the date Previously for each failure instance shown on the "single bug detail page", only the job submit *date* was shown, and not also the time. The UI now uses "starttime" to be able to display the time as well. However this is the job *start* time, rather than when the job was scheduled. As such, this is missing on any jobs that were classified whilst they were still in the pending state (though these are pretty rare, from inspection of the raw ES data). Ideally we'd re-work the data submission from Treeherder entirely, but it's neither worth the effort, nor going to see immediate benefits (since we'd still be missing fields/times for old data in ES). We're using the JS moments library, since date handling in JS is awful. See: http://momentjs.com/docs/#/parsing/unix-timestamp/ http://momentjs.com/docs/#/parsing/utc/ http://momentjs.com/docs/#/displaying/format/
(0) -300 -100 -50 -20 +20 +50 tip