From a4376e578df158e20fbe31b5d03d833529bdcfa8 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Tue, 4 Jul 2023 00:47:30 +0100 Subject: [PATCH] daily-email: add 2023-06-27 A CI pipeline is like an additional team member --- src/content/daily-email/2023-06-27.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 src/content/daily-email/2023-06-27.md diff --git a/src/content/daily-email/2023-06-27.md b/src/content/daily-email/2023-06-27.md new file mode 100644 index 000000000..08b24001e --- /dev/null +++ b/src/content/daily-email/2023-06-27.md @@ -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.