64 lines
2.6 KiB
YAML
64 lines
2.6 KiB
YAML
uuid:
|
|
- value: 467e5ad9-cca4-4700-8727-3356e81182aa
|
|
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:10+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: 'Committing CI artifacts'
|
|
created:
|
|
- value: '2024-07-03T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/07/03/committing-ci-artifacts
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>One of the main uses for <a href="/daily/2024/07/02/ci-not-ci-pipeline">a CI pipeline</a> is to build artifacts for your application, such as installing your dependencies using Composer or npm, or using build tools to perform tasks such as building your CSS and JavaScript assets.</p>
|
|
|
|
<p>Performing these tasks in a CI pipeline means the resulting files can be ignored from your code repository and not committed - making your commits smaller and easier to review, and less likely for you to encounter merge conflicts.</p>
|
|
|
|
<p>The alternative approach is to not use a CI pipline and to perform the tasks manually and commit them to your repository.</p>
|
|
|
|
<p>This introduces a separate set of challenges, but people like having the files in their repository and not worrying about failures in their pipeline.</p>
|
|
|
|
<p>Which do you prefer?</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>One of the main uses for <a href="http://default/daily/2024/07/02/ci-not-ci-pipeline">a CI pipeline</a> is to build artifacts for your application, such as installing your dependencies using Composer or npm, or using build tools to perform tasks such as building your CSS and JavaScript assets.</p>
|
|
|
|
<p>Performing these tasks in a CI pipeline means the resulting files can be ignored from your code repository and not committed - making your commits smaller and easier to review, and less likely for you to encounter merge conflicts.</p>
|
|
|
|
<p>The alternative approach is to not use a CI pipline and to perform the tasks manually and commit them to your repository.</p>
|
|
|
|
<p>This introduces a separate set of challenges, but people like having the files in their repository and not worrying about failures in their pipeline.</p>
|
|
|
|
<p>Which do you prefer?</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|