100 lines
No EOL
4.1 KiB
JSON
100 lines
No EOL
4.1 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "bcabc1ba-016b-48f6-9b16-6efdb038be9e"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-16T14:12:59+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": "Broken pipeline? Fix or revert it."
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-05-01T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:12:59+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/05\/01\/broken-pipeline-fix-or-revert-it",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>If you're doing trunk-based development where multiple people are committing and pushing work to the same branch, what do you do if you've pushed a commit that fails the checks and breaks the pipeline?<\/p>\n\n<p>This is a bad state and needs to be solved as soon as possible as it's causing a problem for everyone else.<\/p>\n\n<p>If the pipeline is failing, someone else could push a change and have it fail for a different reason, but wouldn't know.<\/p>\n\n<p>The responsibility is on the person who pushed the failing commit to resolve it and get the pipeline passing again as soon as possible.<\/p>\n\n<p>You break it, you bought it.<\/p>\n\n<p>Hopefully, the changes in the failing commit are small and it's something you can resolve quickly and push a fixed commit.<\/p>\n\n<p>If you can't fix it within a few minutes, revert the failing commit and try again.<\/p>\n\n<p>What if someone's pushed a failing commit and hasn't fixed it in a timely manner?<\/p>\n\n<p>Revert it for them, fix the pipeline and unblock the rest of the team.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>If you're doing trunk-based development where multiple people are committing and pushing work to the same branch, what do you do if you've pushed a commit that fails the checks and breaks the pipeline?<\/p>\n\n<p>This is a bad state and needs to be solved as soon as possible as it's causing a problem for everyone else.<\/p>\n\n<p>If the pipeline is failing, someone else could push a change and have it fail for a different reason, but wouldn't know.<\/p>\n\n<p>The responsibility is on the person who pushed the failing commit to resolve it and get the pipeline passing again as soon as possible.<\/p>\n\n<p>You break it, you bought it.<\/p>\n\n<p>Hopefully, the changes in the failing commit are small and it's something you can resolve quickly and push a fixed commit.<\/p>\n\n<p>If you can't fix it within a few minutes, revert the failing commit and try again.<\/p>\n\n<p>What if someone's pushed a failing commit and hasn't fixed it in a timely manner?<\/p>\n\n<p>Revert it for them, fix the pipeline and unblock the rest of the team.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:12:59+00:00",
|
|
"guid": null,
|
|
"hash": "59d38746fc261bf6e7575946a0fea245",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |