100 lines
No EOL
3.7 KiB
JSON
100 lines
No EOL
3.7 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "263f6051-340b-4a14-9c0e-028654d4be75"
|
|
}
|
|
],
|
|
"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:50+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?\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2023-08-21T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-21T01:21:50+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": null
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>The main part of my CI pipeline tasks are running the automated tests, coding standards checks and static analysis.<\/p>\n\n<p>But which of these are the most valuable?<\/p>\n\n<p>I used to run the coding standards check first as it was the quickest, followed by static analysis and the automated tests.<\/p>\n\n<p>If a task were going to fail, it would fail quickly.<\/p>\n\n<p>But is that the objective of the CI pipeline?<\/p>\n\n<p>Whilst it needs to be quick, the main reason to run these is to ensure things work as expected.<\/p>\n\n<p>Recently, I changed my pipelines to run the tests first, as these verify the code's behaviour.<\/p>\n\n<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>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>The main part of my CI pipeline tasks are running the automated tests, coding standards checks and static analysis.<\/p>\n\n<p>But which of these are the most valuable?<\/p>\n\n<p>I used to run the coding standards check first as it was the quickest, followed by static analysis and the automated tests.<\/p>\n\n<p>If a task were going to fail, it would fail quickly.<\/p>\n\n<p>But is that the objective of the CI pipeline?<\/p>\n\n<p>Whilst it needs to be quick, the main reason to run these is to ensure things work as expected.<\/p>\n\n<p>Recently, I changed my pipelines to run the tests first, as these verify the code's behaviour.<\/p>\n\n<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>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-21T01:21:50+00:00",
|
|
"guid": null,
|
|
"hash": "40970926a00c3a7ef56c821881cbbc63",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |