80 lines
3.1 KiB
YAML
80 lines
3.1 KiB
YAML
uuid:
|
|
- value: 274408ed-379c-4eaf-914d-7f5599f513d3
|
|
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:01+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: 'Your CI pipeline is your gatekeeper'
|
|
created:
|
|
- value: '2025-01-30T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:01+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2025/01/30/gatekeeper
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>How do you know if a commit to your codebase is deployable?</p>
|
|
|
|
<p>What gives you confidence if a change will work once it's released?</p>
|
|
|
|
<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.</p>
|
|
|
|
<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.</p>
|
|
|
|
<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.</p>
|
|
|
|
<p>This can include running automated tests, linting code and running static analysis and anything else you need.</p>
|
|
|
|
<p>This is what determines if the change is deployable.</p>
|
|
|
|
<p>If your CI pipeline passes, the commit is good can be deployed.</p>
|
|
|
|
<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href="/daily/2023/06/28/theres-no-value-in-a-broken-ci-pipeline">there's no value in a broken CI pipeline</a>.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>How do you know if a commit to your codebase is deployable?</p>
|
|
|
|
<p>What gives you confidence if a change will work once it's released?</p>
|
|
|
|
<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.</p>
|
|
|
|
<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.</p>
|
|
|
|
<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.</p>
|
|
|
|
<p>This can include running automated tests, linting code and running static analysis and anything else you need.</p>
|
|
|
|
<p>This is what determines if the change is deployable.</p>
|
|
|
|
<p>If your CI pipeline passes, the commit is good can be deployed.</p>
|
|
|
|
<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href="http://default/daily/2023/06/28/theres-no-value-in-a-broken-ci-pipeline">there's no value in a broken CI pipeline</a>.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|