In this short demo we look at how Rigor can be used as a performance gate for your Jenkins CI pipeline. 

In our earlier blog, we looked at an overview of adding both code-quality and performance gates to a Jenkins CI pipeline. Here we walk through a live example of a Jenkins build job which has been marked as an ‘unstable’ build because of a performance issue detected by Rigor.

We then view the Rigor diagnostics right inside the Jenkins console. We can see that we have added a new resource which doesn’t have any caching headers set (for example an Expires header) and therefore the static resource won’t be cached by a user’s browser meaning it will need to check each time with the server to see if it has been modified causing unnecessary roundtrips and degrading performance of the page. In this case we can have Jenkins mark the build as unstable and stop it progressing to production.

Clicking the Rigor link in Jenkins takes us into the Rigor Optimisation portal where we can see more details about the problem and how it might be resolved with example for Apache, Nginx and IIS as well as links to other relevant resources on the web.

Rigor not only detects the problem, by checking each build against its 300+ set of best practice rules, but it also walks you through the steps needed to resolve the problem, providing examples of the changes required. Having understood the root cause of the problem, we can now fix the code and commit the change to trigger a new Jenkins build which will hopefully pass this time round.

If you’d like to learn more about Rigor we’d love to show you a longer demo or help you get started with a free trial so please get in touch.  You may also find the white-paper below of further assistance.