What is the principle of Continuous Integration?

• A. Integrate once per release
• B. Only integrate at the end of the project
• C. Ignore assets from the main branch
• D. Continuously integrate assets, leaving as little as possible to the systems team

Answer: (D)

Continuous Integration means teams regularly merge changes into a shared repository and automatically build and test the integrated code. The goal is to get fast feedback, catch integration issues early, and keep a reliable baseline that can be released at any time. Automation is central: builds, tests, and validations run automatically so the process doesn’t depend on manual steps from the systems team, reducing bottlenecks and handoffs. This is why describing continuous integration with automatic, ongoing integration and minimal manual intervention best captures the principle. The other options conflict with CI by delaying feedback, waiting until the end, ignoring the main branch, or relying on manual work from the systems team.