ci

29 stories and discussions about ci, aggregated from every source we track.

1.

We cut PR wait time and running costs by rethinking CI as a system, from the infrastructure underneath it to how work gets scheduled and tests get parallelized.

312 points•julian_digital•2 months ago•399 comments•
2.

:see_no_evil: Volkswagen detects when your tests are being run in a CI server, and makes them pass. - auchenberg/volkswagen

32 points•juliethefoxcoon•6 months ago•2 comments
4.

A practical guide to canceling outdated runs, caching dependencies, reducing duplicate work, and getting faster feedback from GitHub Actions.

10 points•johnnylemonny•about 2 months ago•4 comments
5.

<p>With the latest release of Gitea, an experimental CI/CD feature was added. The above blog post details the technical details, including the various components including the open protocol to allow other CI systems to have the same integration.</p> <p>Disclaimer: While I am not the author of the post, I am involved in the Gitea project and am employed to work on Gitea</p>

10 points•techknowlogick•over 3 years ago•0 comments
6.

WarpBuild is a drop in replacement for Github runners that are 2x faster and 50% cheaper. Get light speed builds and light weight bills in 30 seconds.

9 points•handfuloflight•about 2 months ago•0 comments•
7.

Scaling Scheduling past 10 Million Daily Jobs

8 points•aayushshah15•2 months ago•0 comments•
8.

We wrote six ordinary Postgres migrations: a new column, a unique index, a reporting index, a wider...

7 points•devopsdaily•about 2 months ago•0 comments
9.

On GitHub Actions' standard macOS runner, a Firefox for iOS build takes over 12 minutes and on Avrea with a warm cache it takes just under 2 minutes. Mastodon, built with Tuist, goes from 4 minutes 30 seconds to 12…

5 points•leolannenmaki•about 2 months ago•2 comments•
10.

Every backend developer knows the classic trade-off when writing tests: Unit tests with mocks are...

5 points•mindinu•about 2 months ago•0 comments
11.

Auto-compile OpenAPI specs into Go MCP servers & multiplex official tools behind 1 unified gateway for Cursor & Claude. Free Hobby tier. Get started.

5 points•shashtag•2 months ago•0 comments•
13.

There are no LLM calls in my compliance decision path, and CI blocks adding any. Why an audit trail can't say a model decided, and where the optional ML sits.

4 points•ythouma•about 2 months ago•1 comment•
14.

Blue-green Docker deployment from one config file, over ssh. No engine, no agent, no dependencies. - JVKdouk/RedKite

3 points•jvck10•about 2 months ago•0 comments•
15.

The output of coding agents is growing too fast for CI to keep up. Traditional platforms are imploding and there is demand for something new.

3 points•shykes•about 2 months ago•0 comments•
16.

Light, fluffy, and always free - The AWS Local Emulator alternative - floci-io/floci

3 points•timeoperator•2 months ago•0 comments•
17.

An Agentic Build & CI System. Contribute to vscarpenter/AgentMachinist development by creating an account on GitHub.

2 points•vscarpenter•about 2 months ago•0 comments•
18.

Run formatting and validation, linting, tests, security scans, and documentation checks locally and in CI for Terraform and OpenTofu.

2 points•mooreds•about 2 months ago•0 comments•
19.

Learn how to test Python applications using Requests without hand-crafting mock responses with Betamax.

2 points•sigmavirus24•almost 11 years ago•0 comments
20.

Stateless CI runners made builds clean, and then made us write caching logic into every workflow. Warm microVM snapshots give you a disposable runner that already remembers everything.

1 points•ypeter•about 2 months ago•1 comment•
21.

A comprehensive batch of lint rules for Go, shared across all your repos. - wangjohn/levenshtein

1 points•johnjwang•about 2 months ago•0 comments•
22.

Fifteen AI review bots on one repository is not fifteen times the insight — it is a governance problem. How one open-source project keeps machine reviewers advisory, deterministic gates blocking, and PR code out of the trust boundary.

1 points•qnbs•about 2 months ago•2 comments
23.
1 points•alternateman•about 2 months ago•0 comments•
24.

The output of coding agents is growing too fast for CI to keep up. Traditional platforms are imploding and there is demand for something new.

1 points•levlaz•about 2 months ago•0 comments•
25.

I added a dependency to a test helper and forgot to declare it in the dev extra. Locally it was...

1 points•juanauriti•2 months ago•3 comments
26.

If your CI system starts every job with git clone --depth=1 from git.kernel.org, then you're probably going to get banned. Sorry, not sor...

1 points•garo-pro•2 months ago•0 comments•
27.

Legacy CI/CD platforms haven’t caught up to the realities of the agentic dev cycle. We give you the tools to leverage your newfound velocity.

1 points•handfuloflight•2 months ago•0 comments•
28.

The Day Our Deployment Pipeline Deployed the Wrong Version to Production We had 47 green checkmarks....

1 points•sandeep_chagalakonda_6e60•2 months ago•0 comments
29.

The output of coding agents is growing too fast for CI to keep up. Traditional platforms are imploding and there is demand for something new.

0 points•levlaz•about 2 months ago•0 comments

Related topics