CI (continuous integration)
An automated pipeline that runs build, lint, and test jobs on every branch push or pull request, reporting a pass or fail status. In the PR workflow, a passing CI status is a required prerequisite for merge. (see Topic 13.2) and (see Topic 13.6).
Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in Foundations of Robotics and Physical AI.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
An automated pipeline that runs build, lint, and test jobs on every branch push or pull request, reporting a pass or fail status. In the PR workflow, a passing CI status is a required prerequisite for merge. (see Topic 13.2) and (see Topic 13.6).
The automated process that builds and tests code changes before they are allowed to merge, commonly the enforcement point for schema and data contract tests.
The practice of automatically building and testing every proposed code change against the shared repository on every push, before the change is allowed to merge. The word "continuous" means the pipeline runs on every change, not on a schedule.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- The schema change that broke the forecaster: blast-radius analysis downstream · Quality as Physics, Certified AI Data Governance Professional (CADGP)
- Git branching, pull requests, and code review on a team · Software Engineering and Team Workflow, Foundations of Robotics and Physical AI
- Tracking issues and integrating work without breaking the robot · Software Engineering and Team Workflow, Foundations of Robotics and Physical AI
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.