WTF is Continuous Integration?
Continuous integration was coined as an extreme programming practice, but is used more loosely today.
Continuous integration was originally coined as an extreme programming practice, which states that code should be merged into the primary codebase every few hours.
It tends to be used a little more loosely today to reflect a DevOps practice of automating the process of integrating code into the main codebase.
This automation often includes checks to ensure the code can be safely merged. This includes programmatic tests, like unit tests or acceptance tests. But checks go far beyond running tests. Here are a few more examples:
- Formatting code
- Generating files automatically (e.g. a sitemap)
- Identifying potential curse words in the code
- Testing the performance of a front end applcation
- Validating SEO values
The primary goal is to ensure that the code is ready to be merged into the main branch of the code, and to be consumed by other developers working on the project.
Keep Reading
Using Node.js to Check for Broken Links
A tutorial that walks through the process of writing a Node.js script to recursively test for broken links on a website.
When to Check for Broken Links
Explore various methods for checking for broken links and what to consider when applying the approaches to your site.
Creating Parity Between CI and Jamstack Deployment Process
You can get to production faster by separating CI and build/deployment process. But there’s risk in it. Here are two approaches to help with the decision.