What gates are essential in a continuous integration pipeline?

• A. Manual builds with fixed schedule; gates include manual review only.
• B. Automatic building and testing on commits; essential gates include compilation, unit tests, static analysis, and test coverage checks.
• C. Random testing after deployment; gates include live monitoring only.
• D. Building only on release, with no tests.

Answer: (B)

In a continuous integration pipeline, changes should be checked automatically on every commit, so the system can give fast, reliable feedback. The essential gates are automated steps that run as soon as code is pushed to the repository, preventing faulty changes from progressing.

First, compilation ensures the code builds successfully, catching syntax errors or missing dependencies early before any tests run. Next, unit tests verify small parts of the code behave as intended, giving quick confirmation that individual components work in isolation. Static analysis runs tools that examine the code for quality issues, potential bugs, and security vulnerabilities without executing the program, helping catch problems that tests alone might miss. Finally, test coverage checks assess how much of the codebase is covered by tests and often highlight untested areas, encouraging stronger test suites.

These gates provide rapid, automated feedback and help prevent regressions from entering the main codebase, which is the primary purpose of CI. Alternatives that rely on manual steps, testing only after deployment, or building without tests miss the continuous, early verification that CI is designed to deliver.