December 2024
Intermediate
5 pages
4m
English
Content preview from Fix Bugs in a Continuous Integration Pipeline
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Fix Bugs in a Continuous Integration Pipeline
Continuous integration is essential for keeping a healthy, efficient development process with frequent changes and updates. When a user reports a bug, you need to quickly fix it, while preserving the expected behavior for cases beyond the defect.
Fixing bugs in a pipeline without first reproducing them leads to incomplete solutions and potential regressions. This Shortcut walks you through the process of addressing bugs in production by reproducing them locally, writing a covering test, and merging the fix with test coverage.
Zero Tolerance on Old Bugs
In mission critical systems, customers will require you to handle the defects at once. This agreement is often governed by a service-level agreement. Users understand that defects are part of the fast development release. What users seldom accept is a release breaking cases that were already reported and fixed.
When you encounter a production bug, it’s not enough to apply a quick fix. You must ensure the bug never reappears. Failing to reproduce the bug and write a test that covers it risks the bug resurfacing later. A defect that returns lowers trust in your process and shows that your pipeline isn’t catching issues effectively.
Allowing bugs to go unfixed or improperly addressed creates a cycle of instability. Developers, users, and stakeholders lose confidence in the pipeline, leading to ignoring test results ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.