Adding performance and code quality gates to Jenkins CI
Recently we recorded a short video (2 mins 58s) to demonstrate how you can enhance your Continuous Integration (CI) pipeline by added additional gates to stop slow or erroneous code reaching production.
These days businesses must build faster, more reliable applications, and deliver them faster than ever before in order to stay ahead of the competition. However, the challenge of moving fast is far from simple. Businesses need to balance the speed and agility of innovation while at the same time maintaining quality, reliability and performance.
Many companies are already using CI processes to move faster and become more agile. For some organisations this might be simply automating builds and unit testing. But in the video we talk about 2 concepts which we believe should be key parts of your CI process.
- Continuous Reliability - The practice of having code quality verification gates as part
of your CI pipeline
- Continuous Performance - The practice of having performance verification gates as
part of your CI pipeline
If you would like to read more about code quality gates or performance gates and how they can be added to your CI pipeline, whether you are using Jenkins or another CI tool, then why not download our white paper below. If you have any questions, or would like to chat, we would love to hear from you, and you can contact us here or live chat now.