100 lines
No EOL
5.4 KiB
JSON
100 lines
No EOL
5.4 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "a392788f-8156-488e-8f09-723db507a630"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-21T01:21:19+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-04-21T01:21:19+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": "\n <p>Whilst discussing <a href=\"https:\/\/www.oliverdavies.uk\/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>\n\n<p>Common ones are CI and CD.<\/p>\n\n<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>\n\n<p>Continuous integration is how often code is integrated together.<\/p>\n\n<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>\n\n<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>\n\n<p>CD stands for is continuous deployment or continuous delivery.<\/p>\n\n<p>When is the last time you deployed changes to production?<\/p>\n\n<p>If it's been more than a day, you're not doing continuous deployment.<\/p>\n\n<p>I've worked on teams and projects when it's been months between production releases.<\/p>\n\n<p>I much prefer releasing small, iterative and continuous improvements to production instead of doing large and risky deployments.<\/p>\n\n<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>\n\n<p>How about you?<\/p>\n\n<p>Are you doing CI or CD?<\/p>\n\n<p>What other Drupal or techy jargon terms do you see regularly?<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Whilst discussing <a href=\"https:\/\/www.oliverdavies.uk\/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>\n\n<p>Common ones are CI and CD.<\/p>\n\n<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>\n\n<p>Continuous integration is how often code is integrated together.<\/p>\n\n<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>\n\n<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>\n\n<p>CD stands for is continuous deployment or continuous delivery.<\/p>\n\n<p>When is the last time you deployed changes to production?<\/p>\n\n<p>If it's been more than a day, you're not doing continuous deployment.<\/p>\n\n<p>I've worked on teams and projects when it's been months between production releases.<\/p>\n\n<p>I much prefer releasing small, iterative and continuous improvements to production instead of doing large and risky deployments.<\/p>\n\n<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>\n\n<p>How about you?<\/p>\n\n<p>Are you doing CI or CD?<\/p>\n\n<p>What other Drupal or techy jargon terms do you see regularly?<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-21T01:21:19+00:00",
|
|
"guid": null,
|
|
"hash": "431bef314ddeb1827fe0a9654609412d",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |