68 lines
2.6 KiB
YAML
68 lines
2.6 KiB
YAML
uuid:
|
|
- value: 65ad8d2c-a07d-4dbb-896d-0a3a66c0fe65
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'Running automated checks in a CI pipeline'
|
|
created:
|
|
- value: '2024-07-07T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/07/07/running-automated-checks-in-a-ci-pipeline
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<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>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>As well as <a href="http://default/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>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|