oliverdavies.uk/content/node.b48769b5-0c48-4bee-a008-6a760db421de.yml

uuid:
  - value: b48769b5-0c48-4bee-a008-6a760db421de
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: 'What are CI and CD?'
created:
  - value: '2025-02-17T00: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/02/17/ci-cd
    langcode: en
body:
  - value: |
      <p>Whilst discussing <a href="/daily/2025/02/14/drupalisms">de-jargoning Drupal and Drupalisms</a> with Emma Horrell and Luke McCormick, I started thinking about pieces of jargon I come across regularly.</p>

      <p>Common ones are CI and CD.</p>

      <p>CI (or continuous integration) is not about whether you have a CI pipeline and use a tool like Jenkins, GitHub Actions or GitLab CI (despite how some of these tools are named).</p>

      <p>Continuous integration is how often code is integrated together.</p>

      <p>If it's been more than a day since you last merged your code into your mainline branch, you're not doing continuous integration.</p>

      <p>The less often you merge code, the more likely it is there will be conflicts or incompatibilities with other code that's been worked on - whether it's someone else's code, or code that you're writing in a different branch for a different task.</p>

      <p>CD stands for is continuous deployment or continuous delivery.</p>

      <p>When is the last time you deployed changes to production?</p>

      <p>If it's been more than a day, you're not doing continuous deployment.</p>

      <p>I've worked on teams and projects when it's been months between production releases.</p>

      <p>I much prefer releasing small, iterative and continuous improvements to production instead of doing large and risky deployments.</p>

      <p>Developers get their changes released sooner, end users get fixes and new features sooner, and it's easier to identify and resolve issues when releases are smaller and more frequent.</p>

      <p>How about you?</p>

      <p>Are you doing CI or CD?</p>

      <p>What other Drupal or techy jargon terms do you see regularly?</p>

              
    format: full_html
    processed: |
      <p>Whilst discussing <a href="/daily/2025/02/14/drupalisms">de-jargoning Drupal and Drupalisms</a> with Emma Horrell and Luke McCormick, I started thinking about pieces of jargon I come across regularly.</p>

      <p>Common ones are CI and CD.</p>

      <p>CI (or continuous integration) is not about whether you have a CI pipeline and use a tool like Jenkins, GitHub Actions or GitLab CI (despite how some of these tools are named).</p>

      <p>Continuous integration is how often code is integrated together.</p>

      <p>If it's been more than a day since you last merged your code into your mainline branch, you're not doing continuous integration.</p>

      <p>The less often you merge code, the more likely it is there will be conflicts or incompatibilities with other code that's been worked on - whether it's someone else's code, or code that you're writing in a different branch for a different task.</p>

      <p>CD stands for is continuous deployment or continuous delivery.</p>

      <p>When is the last time you deployed changes to production?</p>

      <p>If it's been more than a day, you're not doing continuous deployment.</p>

      <p>I've worked on teams and projects when it's been months between production releases.</p>

      <p>I much prefer releasing small, iterative and continuous improvements to production instead of doing large and risky deployments.</p>

      <p>Developers get their changes released sooner, end users get fixes and new features sooner, and it's easier to identify and resolve issues when releases are smaller and more frequent.</p>

      <p>How about you?</p>

      <p>Are you doing CI or CD?</p>

      <p>What other Drupal or techy jargon terms do you see regularly?</p>

              
    summary: null
field_daily_email_cta: {  }