A homepage change can look fine in one person's browser and still break when someone else tries it. Continuous integration, or CI, brings changes together frequently and runs repeatable checks against specific revisions.
Continuous Integration · Lesson 1
Continuous Integration
Learn how continuous integration checks small changes before they enter a shared branch.
Connecting a Change to a Check
A revision identifies the version of the files being checked. When a proposed change modifies index.html, CI can run a check against that version and report whether it meets an expectation. For this site, a check might look for the required heading. The team can use the result while deciding whether to merge.
A check passed on Monday. A new commit changes the page on Tuesday. What does the old pass establish?
Reading a Failed Check
Suppose a check says the expected heading is missing. This gives the author a narrow place to investigate. Read the expectation and the result before changing the page. Sometimes the author made a mistake. Sometimes the intended behavior changed and the check needs a corresponding edit.
What should you inspect first when the heading check fails?
Distinguishing Checks and Delivery
A pipeline can check files, build an output, and hand that output to a later deployment. A build prepares something downstream steps can use, such as a directory of ready-to-serve files. A deployment installs or starts a version in an environment. Your first CI workflow will check a page before it goes anywhere.
Tests passed and a site archive was produced. What evidence would show visitors can use that version?
Lesson complete
You finished Continuous Integration
You can now explain where CI fits in a change's path.
Associate a check with a specific revision.
Use a failed check to identify the first question to investigate.
Distinguish checking, building, and deploying.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account