How to optimise your CICD pipeline with synthetic monitoring

Date: 5th June 2017
Author: Louise Arnold

Optimising your CICD cycle

CICD (continuous integration, continuous development) is becoming the de facto methodology for many web development teams. It employs an agile, ‘permanent beta’ approach to ensure that new iterations are available for introduction as soon as they’ve been developed and means that a site is subject to continuous improvement without any delays.

Many of our clients already take an agile approach to introducing new functionality, with code being written, integrated and tested in a cycle that’s as efficient as possible without taking unnecessary risks.

Getting it right before deployment

In practice, thousands of minor releases will be applied every month – most consisting of micro changes rather than significant operational updates. Many publishers use a fully automated process to test these units (UAT) but it’s also worth considering using synthetic monitoring during staging to improve the resilience of software releases when they go live.

SciVisum can monitor performance at any point in its release cycle. We can use SV-Monitor to run journeys in both staging and production environments. Some clients run duplicate journeys in both environments and then measure the impact of any changes by comparing the two sets of results. If a problem is flagged during staging/pre-production, a client can take the decision not to release until more refinements have been made.

Saving time and money

Monitoring in this way during staging is unique to SV-Monitor. It saves time and money in the long run by automatically highlighting any performance issues introduced as a result of development changes. This early identification enables the speedy resolution of any performance issues and saves larger, more expensive problems further along the process.

  • Compare duplicate journeys
  • Monitor during staging and production
  • Release or refine based on hard data

By using synthetic monitoring as part of your CICD pipeline, it’s possible to ensure that your development is as finely tuned as possible, resulting in high-quality integration and deployment of new releases. If you’d like to find out more about SciVisum’s agile approach to CICD via synthetic monitoring, please contact us for a demonstration.

Did you enjoy this post?

Join us today for more great news, tips and research directly into your mailbox.

Top