Integration
Once the code is committed to the repository, the next phase, continuous integration, will automatically start. This is done by configuring a CI pipeline. This phase will build the source code with a repository snapshot and generate deployable artifacts. Different organizations use different events to kick-start the build. A CI start event may be on every developer commit or may be based on a time window, such as daily, weekly, and more.
The CI workflow is the key aspect of this phase. Continuous integration tools, such as Jenkins, Bamboo, and more, play the central role of orchestrating the build pipeline. The tool will be configured with a workflow of activities to be invoked. The workflow automatically executes the configured ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access