Deployments with your CI pipeline
You have a CI pipeline in your project.
Every time you push a commit, the CI pipeline runs and performs its checks.
It runs the automated tests and verifies they pass, statically analyses the code to identify any issues and validates the code follows the correct coding style and standards.
Everything passes.
What next?
If the pipeline passes, your change is deployable.
So, why not extend the pipeline to deploy the change once the checks pass?
If the checks don't pass, don't deploy.
It could be as simple as pushing the code to an S3 bucket, a separate Git branch or repository for managing deployments, or creating an artifact like a Docker image.
Instead of waiting for someone to do this manually, remove a step and automate it within the pipeline.
The sooner it's deployed, the sooner it provides value for your application's users.
- Oliver
