At Rigor, business teams and developers often ask us, “How often should we run reports to look for performance optimizations?” or “How can I integrate optimization into our existing workflow?”
From talking with teams who’ve found success, we’ve learned that performance optimization is almost never a one time project where you find all the optimizations available, fix them, and call it a day. Websites are being updated often, sometimes even several times each day. And when those updates happen, it’s ideal to treat performance defects like any other bugs that could be introduced to your website or web app. While you could scan for those bugs periodically – for example, once per day – it often makes more sense to scan for performance defects after releasing recent changes or – even better – before those changes go live into production.
One of the core concepts of Continuous Integration is that builds should be both automated and self-testing. Automations and rules should be put in place to prevent bugs and regressions from releasing into the wild. But what if you could automatically test for performance optimizations alongside your existing tests as part of your build?
To make this possible, we’ve put together a brand new Rigor Optimization plugin for Jenkins and we’re pleased to share that with you today.
Here’s how it works
If you use Jenkins for your continuous integration builds, this new plugin makes it easy to test your website performance as a discrete step in your Jenkins build process.
With the plugin, you can launch one or more Rigor Optimization performance tests to analyze your newly built website, optionally failing the Jenkins build if specific performance metrics are not met.
In addition, the plugin will automatically tag all tests and snapshots in your Rigor Optimization account with details about the Jenkins build project, build number, and details about build pass/fail status.
For full details about how to install and configure the Rigor Optimization plugin for Jenkins, check out this post How to Run Optimization Tests from a Jenkins Build on Rigor’s Knowledge Base.
When you treat performance defects as bugs and automate performance optimization as part of your workflow, it makes it much easier to manage performance issues over time. Instead of manually kicking off tests or sorting through a whole number of issues that could have popped up since the last time you tested, you can isolate only the new issues related to your recent build. And if you’re aggressive about failing builds that include performance defects you’ll ultimately offer better, more reliable user experiences for the visitors to your website or web app.
Ready to integrate Rigor Optimization into your Jenkins builds? Download the plugin to connect your existing account, or contact us today to book a trial kickoff so you can try this for yourself.
E-commerce revenue continues to grow,as consumers turn away from shopping in brick-and-mortar stores to shopping online. However, many businesses are not prepared for this growth because they do not fully understand the market and how to invest in...Read More
Because of the multifarious nature of web clients today, it’s important to consider the usage statistics when designing, implementing, and managing your site. However, misconceptions often arise when determining what browsers to design for an...Read More
Google Webmaster Tools is a web service that allows webmasters to view the status of their sites as seen by Google and the Googlebot crawlers. In addition to indexing your site structure and content, the Googlebot crawlers also record data on perform...Read More
Web designers and developers are always looking for ways to speed up their page load times. Yahoo has an excellent article written on the best practices for speeding up your page. How do you know if implementing one of their suggested practices will...Read More