uuid:
  - value: 1bac9c8b-18bd-4f09-a8ae-867c43798762
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:34+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: |
      Which part of the CI pipeline has the most value?
created:
  - value: '2023-08-21T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:34+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2023/08/21/which-part-of-the-ci-pipeline-has-the-most-value
    langcode: en
body:
  - value: |
      <p>The main part of my CI pipeline tasks are running the automated tests, coding standards checks and static analysis.</p>

      <p>But which of these are the most valuable?</p>

      <p>I used to run the coding standards check first as it was the quickest, followed by static analysis and the automated tests.</p>

      <p>If a task were going to fail, it would fail quickly.</p>

      <p>But is that the objective of the CI pipeline?</p>

      <p>Whilst it needs to be quick, the main reason to run these is to ensure things work as expected.</p>

      <p>Recently, I changed my pipelines to run the tests first, as these verify the code's behaviour.</p>

      <p>I want to know if the code works but has a coding standard error that needs to be fixed rather than the pipeline failing on the error and not knowing whether the code works.</p>

              
    format: full_html
    processed: |
      <p>The main part of my CI pipeline tasks are running the automated tests, coding standards checks and static analysis.</p>

      <p>But which of these are the most valuable?</p>

      <p>I used to run the coding standards check first as it was the quickest, followed by static analysis and the automated tests.</p>

      <p>If a task were going to fail, it would fail quickly.</p>

      <p>But is that the objective of the CI pipeline?</p>

      <p>Whilst it needs to be quick, the main reason to run these is to ensure things work as expected.</p>

      <p>Recently, I changed my pipelines to run the tests first, as these verify the code's behaviour.</p>

      <p>I want to know if the code works but has a coding standard error that needs to be fixed rather than the pipeline failing on the error and not knowing whether the code works.</p>

              
    summary: null
field_daily_email_cta: {  }