daily-email: add 2023-06-27
A CI pipeline is like an additional team member
This commit is contained in:
parent
606e0235bf
commit
a4376e578d
20
src/content/daily-email/2023-06-27.md
Normal file
20
src/content/daily-email/2023-06-27.md
Normal file
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
title: >
|
||||
A CI pipeline is like an additional team member
|
||||
pubDate: 2023-06-27
|
||||
permalink: >
|
||||
archive/2023/06/27/ci-pipeline-additional-team-member
|
||||
tags:
|
||||
- continuous-integration
|
||||
- pipelines
|
||||
---
|
||||
|
||||
Imagine having a team member who tests each feature before every deployment, reviews the code to ensure its style is consistent, runs quality checks like linting and static analysis, and checks for insecure dependencies.
|
||||
|
||||
If those checks all pass, they automatically deploy the changes and make them live or update a pre-production environment.
|
||||
|
||||
## Here's the thing
|
||||
|
||||
A CI pipeline can do that. Automatically. For every commit and change to your codebase.
|
||||
|
||||
Having a CI pipeline is like having an additional team member and one who's always ready and waiting for someone to push a change to test.
|
Loading…
Reference in a new issue