Last modified: 2014-02-20 13:16:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59137, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 57137 - Add a voting YSlow job to Jenkins
Add a voting YSlow job to Jenkins
Status: NEW
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: performance
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-11-16 12:05 UTC by Ori Livneh
Modified: 2014-02-20 13:16 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ori Livneh 2013-11-16 12:05:21 UTC 
YSlow is Yahoo!'s page performance tool. It runs under PhantomJS (see <http://yslow.org/phantomjs/>) for easy integration with Jenkins.

There should be a Jenkins job to run YSlow against a page and to -1 the change if the overall score drops relative to an established baseline.
Comment 1 Gabriel Wicke 2013-11-25 20:37:00 UTC 
+1. This should make front-end performance regressions visible before they become an issue in production.
Comment 2 Antoine "hashar" Musso (WMF) 2014-02-20 13:16:35 UTC 
Not sure how we can get a job running reliably / offering same performances.  Maybe a dedicated slave that would run only one job at a time.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links