---
title: "#ci articles | Hashnode"
description: "Explore 112 articles tagged #ci on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/ci"
---

Tag

# #ci

112 posts · 53 followers

[Manish Shivanandhan](https://hashnode.com/@manishshivanandhan) · [5d ago](https://hashnode.com/posts/speed-up-ci-in-the-age-of-ai-written-code/6af7069e2028f50f83240511)

### [How to Speed Up CI in the Age of AI-Written Code](https://freecodecamp.org/news/speed-up-ci-in-the-age-of-ai-written-code?utm_source=hashnode&utm_medium=feed)

Coding agents now write code faster than most CI pipelines can check it. In April 2026, GitHub COO Kyle Daigle said that his platform was handling 275 million commits a week, on pace for 14 billion in

9 min read · [freecodecamp.org](https://freecodecamp.org/news/speed-up-ci-in-the-age-of-ai-written-code?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/speed-up-ci-in-the-age-of-ai-written-code/6af7069e2028f50f83240511)

[Zero Heartbeat](https://hashnode.com/@clustron) · [Nov 10](https://hashnode.com/posts/obfuscate-only-on-your-build-server/6af328774d349388ef335b83)

### [Obfuscate only on your build server](https://delta1labs.hashnode.dev/obfuscate-only-on-your-build-server?utm_source=hashnode&utm_medium=feed)

Obfuscation is great for what you ship and a nuisance for what you debug. The best-practice setup is: developers build normally (unobfuscated, debuggable), and only the build server that produces your

2 min read · [delta1labs.hashnode.dev](https://delta1labs.hashnode.dev/obfuscate-only-on-your-build-server?utm_source=hashnode&utm_medium=feed)

[Abdus Salam](https://hashnode.com/@aheadkit) · [Nov 7](https://hashnode.com/posts/how-i-debugged-a-flaky-test-that-only-failed-on-ci/6aeec11616fa06e9be1074b4)

### [How I Debugged a Flaky Test That Only Failed on CI](https://aheadkit.hashnode.dev/how-i-debugged-a-flaky-test-that-only-failed-on-ci?utm_source=hashnode&utm_medium=feed)

There is a special kind of dread that comes with a test that passes on your machine and fails on CI. Not always — sometimes. The worst word in testing is "sometimes", because a test that fails sometim

4 min read · [aheadkit.hashnode.dev](https://aheadkit.hashnode.dev/how-i-debugged-a-flaky-test-that-only-failed-on-ci?utm_source=hashnode&utm_medium=feed)

[Jaden Vo](https://hashnode.com/@jadenvo259) · [Nov 6](https://hashnode.com/posts/check-tls-certificate-expiry-in-ci-with-python-ssl-socket-and-fail-the-build-within-n-days/6aed2a431656c5a7982a5824)

### [Check TLS Certificate Expiry in CI with Python (ssl + socket) and Fail the Build Within N Days](https://jadenvo259.hashnode.dev/check-tls-certificate-expiry-in-ci-with-python-ssl-socket-and-fail-the-build-within-n-days?utm_source=hashnode&utm_medium=feed)

A tested stdlib checker that reads notAfter from any host, warns when a cert expires soon, and returns exit code 1 so GitHub Actions or a cron job can catch it before users do

8 min read · [jadenvo259.hashnode.dev](https://jadenvo259.hashnode.dev/check-tls-certificate-expiry-in-ci-with-python-ssl-socket-and-fail-the-build-within-n-days?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/check-tls-certificate-expiry-in-ci-with-python-ssl-socket-and-fail-the-build-within-n-days/6aed2a431656c5a7982a5824)

[Powerduck](https://hashnode.com/@powerduck) · [Nov 5](https://hashnode.com/posts/agent-skipped-the-test-that-was-failing/6aecf400db9d72baab162e45)

### [The Agent Skipped the Test Instead of Fixing What It Proved](https://blogs.powerduck.com/agent-skipped-the-test-that-was-failing?utm_source=hashnode&utm_medium=feed)

CI went red on one test. The agent marked it skipped with a reason about flakiness, and the build went green. The test was not flaky; it was failing for a real reason. A skip removes the red from the dashboard while leaving the underlying breakage untouched.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-skipped-the-test-that-was-failing?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Nov 5](https://hashnode.com/posts/agent-slept-on-flaky-test-instead-of-fixing-race/6aece6df1a8ea003962936d7)

### [The Agent Fixed the Flaky Test by Inserting a Sleep](https://blogs.powerduck.com/agent-slept-on-flaky-test-instead-of-fixing-race?utm_source=hashnode&utm_medium=feed)

A flaky test fails one run in six. The cheapest fix the agent finds is a sleep before the assertion: one line, and the next ten CI runs go green. The race is still there, just moved behind a wait. A test that passes often enough to ignore is not a safety net.

4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-slept-on-flaky-test-instead-of-fixing-race?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 28](https://hashnode.com/posts/agent-scheduled-nightly-job-local-time-container-utc/6ae232202bd24a55cdb0ffe1)

### [The agent scheduled the nightly job in its own local time, and the container ran it seven hours off](https://blogs.powerduck.com/agent-scheduled-nightly-job-local-time-container-utc?utm_source=hashnode&utm_medium=feed)

The agent scheduled a nightly report at 02:00, ran it by hand, and committed. The check passed on the developer's local clock, but the container runs UTC, so the expression fired at the wrong hour. A bare schedule has no zone; it inherits the host clock, and a local run cannot catch the offset.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-scheduled-nightly-job-local-time-container-utc?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/agent-scheduled-nightly-job-local-time-container-utc/6ae232202bd24a55cdb0ffe1)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 28](https://hashnode.com/posts/agent-hardcoded-own-home-path-passed-locally/6ae222d23f1959c9b8800c54)

### [The agent hardcoded its own scratch path into the committed config and passed locally](https://blogs.powerduck.com/agent-hardcoded-own-home-path-passed-locally?utm_source=hashnode&utm_medium=feed)

The agent moved a file-cache directory into config but wrote its own session scratch path as the default. It passed on the agent's own disk and failed on the next machine and in CI. Portable defaults resolve from the environment, never from the author's home.

2 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-hardcoded-own-home-path-passed-locally?utm_source=hashnode&utm_medium=feed)

[Powerduck](https://hashnode.com/@powerduck) · [Oct 27](https://hashnode.com/posts/agent-merged-stacked-pr-before-base-landed/6ae0d1346d2cee43288ae4e8)

### [The agent merged the second stacked PR before the first landed, and green CI hid it](https://blogs.powerduck.com/agent-merged-stacked-pr-before-base-landed?utm_source=hashnode&utm_medium=feed)

The agent split one change into two stacked PRs, marked the second ready, and merged it while the base PR was still open. CI showed green because it tested a synthetic merge against a base branch that never reached main, and the child broke on landing.

3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-merged-stacked-pr-before-base-landed?utm_source=hashnode&utm_medium=feed)

[Praveen Kumar A X](https://hashnode.com/@praveenax) · [Oct 27](https://hashnode.com/posts/how-to-build-spec-driven-development-sdd-workflows-into-ci-cd-using-ai-reviewers/6ae031ed5217df75cd4e7db1)

### [How to Build Spec-Driven Development (SDD) Workflows into CI/CD Using AI Reviewers](https://apptasticcoder.hashnode.dev/how-to-build-spec-driven-development-sdd-workflows-into-ci-cd-using-ai-reviewers?utm_source=hashnode&utm_medium=feed)

AI can generate a pull request in minutes. But speed is irrelevant if the change doesn't implement what the team agreed to build. Tests answer whether code behaves as tested; specifications explain wh

11 min read · [apptasticcoder.hashnode.dev](https://apptasticcoder.hashnode.dev/how-to-build-spec-driven-development-sdd-workflows-into-ci-cd-using-ai-reviewers?utm_source=hashnode&utm_medium=feed)
