100 lines
No EOL
4.2 KiB
JSON
100 lines
No EOL
4.2 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "274408ed-379c-4eaf-914d-7f5599f513d3"
|
|
}
|
|
],
|
|
"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:01+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": "Your CI pipeline is your gatekeeper"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-01-30T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:01+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2025\/01\/30\/gatekeeper",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>How do you know if a commit to your codebase is deployable?<\/p>\n\n<p>What gives you confidence if a change will work once it's released?<\/p>\n\n<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.<\/p>\n\n<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.<\/p>\n\n<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.<\/p>\n\n<p>This can include running automated tests, linting code and running static analysis and anything else you need.<\/p>\n\n<p>This is what determines if the change is deployable.<\/p>\n\n<p>If your CI pipeline passes, the commit is good can be deployed.<\/p>\n\n<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2023\/06\/28\/theres-no-value-in-a-broken-ci-pipeline\">there's no value in a broken CI pipeline<\/a>.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>How do you know if a commit to your codebase is deployable?<\/p>\n\n<p>What gives you confidence if a change will work once it's released?<\/p>\n\n<p>This can be from manual testing but also automated testing and quality checks from tools such as static analysis and code linting.<\/p>\n\n<p>However, this relies on every Developer running them before pushing each change and for their development environments to be consistent and matching the target environment.<\/p>\n\n<p>This can be automated by using a CI pipeline - a series of checks that are run automatically for each code push.<\/p>\n\n<p>This can include running automated tests, linting code and running static analysis and anything else you need.<\/p>\n\n<p>This is what determines if the change is deployable.<\/p>\n\n<p>If your CI pipeline passes, the commit is good can be deployed.<\/p>\n\n<p>If it fails, the commit should not be deployed and you should get it passing again as quickly as possible as <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2023\/06\/28\/theres-no-value-in-a-broken-ci-pipeline\">there's no value in a broken CI pipeline<\/a>.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:33:45+00:00",
|
|
"guid": null,
|
|
"hash": "f0ce2f69b9db5c6cc971459f685e5a9c",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |