Reviewing Common CI/CD Patterns
Discuss various CI/CD patterns.
We'll cover the following...
As with any engineering discipline, we can generally find patterns that help implement a specific strategy or outcome. This is also true when we’re dealing with CI/CD pipelines. Branching strategies for our repository can be loosely or tightly coupled to the pattern we decide to go with but are not in themselves CI/CD patterns.
As we’re using Git as our source control management system, the notion is that we’ll generally be developing in a branch, pushing those changes remotely, and, ultimately, creating a pull request to merge our code into a branch suitable for building a deployable artifact.
However, there are some patterns that, when automated, will give us an advantage, especially if multiple environments or artifacts are used.
Environment-based
Using an environment-based approach to software deployment is typical of most development life cycles. Two patterns are commonly leveraged to facilitate multi-environment deployments:
The first ...