Migrate content to YAML

content/node.41b8a70d-5df8-45f5-956a-c30b2f3e06de.yml

@@ -0,0 +1,65 @@
+uuid:
+  - value: 41b8a70d-5df8-45f5-956a-c30b2f3e06de
+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:51+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: |
+      Agnostic CI pipelines with run files
+created:
+  - value: '2022-11-17T00:00:00+00:00'
+changed:
+  - value: '2025-05-11T09:00:51+00:00'
+promote:
+  - value: false
+sticky:
+  - value: false
+default_langcode:
+  - value: true
+revision_translation_affected:
+  - value: true
+path:
+  - alias: /daily/2022/11/17/agnostic-ci-pipelines-with-run-files
+    langcode: en
+body:
+  - value: |
+      <p>As I work on various projects, I use several different CI tools, such as GitHub Actions, Bitbucket Pipelines, and GitLab CI, as well as hosting providers that have build and deploy steps.</p>
+
+      <p>Some only run continuous integration checks, like automated tests and static analysis, some build and push Docker images, and some use Ansible and Ansistrano to deploy the changes to production.</p>
+
+      <p>Each tool has its configuration file with different settings and formats.</p>
+
+      <p>Rather than being too tightly coupled to a particular tool, I like to keep things as agnostic as possible and <a href="/daily/2022/08/15/using-run-file-simplify-project-tasks">use a run file</a> with separate <code>ci:build</code> and <code>ci:deploy</code> tasks.</p>
+
+      <p>This means that all the logic is within the run file rather than the CI tool-specific configuration file, so the file is shorter and cleaner; I can make changes to the CI tasks locally and quickly test changes and iterate, and also, as the logic is within the run file, I can easily switch to a different CI tool if needed without making changes to the tasks themselves.</p>
+
+              
+    format: full_html
+    processed: |
+      <p>As I work on various projects, I use several different CI tools, such as GitHub Actions, Bitbucket Pipelines, and GitLab CI, as well as hosting providers that have build and deploy steps.</p>
+
+      <p>Some only run continuous integration checks, like automated tests and static analysis, some build and push Docker images, and some use Ansible and Ansistrano to deploy the changes to production.</p>
+
+      <p>Each tool has its configuration file with different settings and formats.</p>
+
+      <p>Rather than being too tightly coupled to a particular tool, I like to keep things as agnostic as possible and <a href="http://default/daily/2022/08/15/using-run-file-simplify-project-tasks">use a run file</a> with separate <code>ci:build</code> and <code>ci:deploy</code> tasks.</p>
+
+      <p>This means that all the logic is within the run file rather than the CI tool-specific configuration file, so the file is shorter and cleaner; I can make changes to the CI tasks locally and quickly test changes and iterate, and also, as the logic is within the run file, I can easily switch to a different CI tool if needed without making changes to the tasks themselves.</p>
+
+              
+    summary: null
+field_daily_email_cta: {  }