<p>As well as <a href="/daily/2024/07/03/committing-ci-artifacts">committing build artifacts</a>, another common use for CI pipelines is for running automated checks.</p>
<p>This could include code linting, static analysis, automated tests, checking for security vulnerabilities, and more.</p>
<p>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.</p>
<p>If all the checks pass, a commit can be promoted and released.</p>
<p>If not, the commit should not be deployed and it should be fixed.</p>
<p>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.</p>
<p>As well as <a href="/daily/2024/07/03/committing-ci-artifacts">committing build artifacts</a>, another common use for CI pipelines is for running automated checks.</p>
<p>This could include code linting, static analysis, automated tests, checking for security vulnerabilities, and more.</p>
<p>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.</p>
<p>If all the checks pass, a commit can be promoted and released.</p>
<p>If not, the commit should not be deployed and it should be fixed.</p>
<p>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.</p>