A developer can commit code to a version control projects (VCP) system, such as GitHub and GitLab. The CI server can either poll the repository for changes or the CI server can be configured to trigger a software build via a WebHook. We will look at this later with Jenkins, Travis, and Circle CI. The CI server will then get the latest software revision from the VCP system and can then execute a build script that integrates the software system. The CI server should generate feedback that emails build results upon a build failure to specified project members. The CI server will continuously poll for changes or will respond from a configured WebHook.
CI process steps in a nutshell
Get Hands-On Continuous Integration and Delivery now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
