The point of continuous integration is to automate builds and tests, and bring efficiency and quality to the pipeline. However, things do sometimes go wrong with the faster pace of development and more frequent updates that accompany a continuous integration process. When major incidents or something goes wrong occur, there’s a lot of panic. That’s where incident […]

| In Ideas, Innovation

As a developer, I’m a huge fan of continuous integration. For the uninitiated, continuous integration is a software engineering practice in which code changes are tested as soon as they are committed. This enables early problem detection. It also provides immediate feedback on code quality, allowing for issues to be identified and fixed immediately. Often […]

| In Operations Performance, Reliability

Continuous integration (CI) is a software development practice where members frequently merge their work to decrease problems and conflicts. Each push is supported by an automated build (and test) to detect errors. By checking in with one another frequently, teams can develop software more quickly and reliably. In essence, CI its about verifying the quality […]

| In Reliability

At PagerDuty, all of our computing infrastructure is automated using Chef. We push out features and changes to our Chef codebase very frequently – often multiple times a day – and this makes it crucial that we test our Chef code before we deploy it to our production environment. As we have learned, failures can […]