-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Running automated checks in a CI pipeline
- Loading branch information
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
title: Running automated checks in a CI pipeline | ||
date: 2024-07-07 | ||
permalink: daily/2024/07/07/running-automated-checks-in-a-ci-pipeline | ||
tags: | ||
- software-development | ||
- automated-testing | ||
cta: ~ | ||
snippet: | | ||
What checks do you run in your CI pipeline? | ||
--- | ||
|
||
As well as [committing build artifacts][0], another common use for CI pipelines is for running automated checks. | ||
|
||
This could include code linting, static analysis, automated tests, checking for security vulnerabilities, and more. | ||
|
||
Instead of relying on Developers running these checks manually, running them automatically in a CI pipeline ensures they're run regularly and that each commit is deployable. | ||
|
||
If all the checks pass, a commit can be promoted and released. | ||
|
||
If not, the commit should not be deployed and it should be fixed. | ||
|
||
This makes a CI pipeline and automated checks vital to ensure the quality of your software, to identify regressions, and to avoid promoting and releasing broken code. | ||
|
||
[0]: {{site.url}}/daily/2024/07/03/committing-ci-artifacts |