Move all files to sculpin/
This commit is contained in:
parent
c5d71803a5
commit
0f61b4e9ee
1514 changed files with 0 additions and 0 deletions
32
sculpin/source/_posts/2023-08-22.md
Normal file
32
sculpin/source/_posts/2023-08-22.md
Normal file
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
title: >
|
||||
Deployments with your CI pipeline
|
||||
pubDate: 2023-08-22
|
||||
permalink: >-
|
||||
daily/2023/08/22/deployments-with-your-ci-pipeline
|
||||
tags:
|
||||
- continuous-integration
|
||||
- pipelines
|
||||
---
|
||||
|
||||
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.
|
Loading…
Add table
Add a link
Reference in a new issue