oliverdavies.uk/content/node.dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545.yml

68 lines
2.6 KiB
YAML

uuid:
- value: dac9bd2c-23e1-4ee7-a32b-7b1a1ff47545
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:02+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: "Who's Travis?"
created:
- value: '2025-01-23T00:00:00+00:00'
changed:
- value: '2025-05-11T09:00:02+00:00'
promote:
- value: false
sticky:
- value: false
default_langcode:
- value: true
revision_translation_affected:
- value: true
path:
- alias: /daily/2025/01/23/travis
langcode: en
body:
- value: |
<p>I remember seeing a talk or listening to a podcast during which they mentioned Travis, as in the CI pipeline tool, and some of the things they were using it for.</p>
<p>They also said that their client thought Travis was a person on their team.</p>
<p>In some ways, having a CI pipeline performing automated checks and tests is like having another team member.</p>
<p>Instead of waiting for a person to manually check code styles, run tests and spot potential bugs, why not automate them and run them in the CI pipeline every time code changes are pushed?</p>
<p>You'll get results sooner than waiting for a person do check the code by hand and, arguably, more consistent results.</p>
<p>Then, if you do peer code reviews, you know the basics are already done and the reviewer can focus on other things.</p>
format: full_html
processed: |
<p>I remember seeing a talk or listening to a podcast during which they mentioned Travis, as in the CI pipeline tool, and some of the things they were using it for.</p>
<p>They also said that their client thought Travis was a person on their team.</p>
<p>In some ways, having a CI pipeline performing automated checks and tests is like having another team member.</p>
<p>Instead of waiting for a person to manually check code styles, run tests and spot potential bugs, why not automate them and run them in the CI pipeline every time code changes are pushed?</p>
<p>You'll get results sooner than waiting for a person do check the code by hand and, arguably, more consistent results.</p>
<p>Then, if you do peer code reviews, you know the basics are already done and the reviewer can focus on other things.</p>
summary: null
field_daily_email_cta: { }