Dan Manges

1.9K posts

Dan Manges banner
Dan Manges

Dan Manges

@dan_manges

Building the next generation of CI/CD: @rwx_cloud. Previously built @RootInsurance (IPO) and @braintree ($800M acq)

Columbus, OH Katılım Şubat 2008
1.4K Takip Edilen1.9K Takipçiler
Dan Manges
Dan Manges@dan_manges·
@ryancarson @bernhardsson You should check out RWX. Run from a local CLI, results output from the CLI, automatic content-based caching, graph-based task model (deduplicates steps). Runs on normal container images but powered by a new container runtime. It’s the best CI/CD for agents.
English
0
0
0
8
Dan Manges retweetledi
Isaac Van Doren
Isaac Van Doren@isaacvando·
Thrilled to have Andrew Kelley, creator of @ziglang speaking at Software Should Work. Early bird ticket sales end at midnight!
Isaac Van Doren tweet media
English
1
2
11
1.5K
Richard Artoul
Richard Artoul@richardartoul·
just rebuilt our CI for the 4th time, much faster now next rebuild will probably be rewriting it around a proper queue for distributing work instead of the hacky modulo sharding everyone does
English
2
0
8
1.4K
Dan Manges retweetledi
RWX
RWX@rwx_cloud·
"RWX was built by engineers for engineers, and it shows in how fast and hands-off CI feels day to day." Learn how Tropic migrated from a bloated GitHub Actions workflow to RWX, cutting CI runtimes by 3x while accelerating the path from PR to deployment. rwx.com/customers/trop…
English
0
1
3
114
Dan Manges
Dan Manges@dan_manges·
@lukerramsden I’ve been building a new CI/CD platform for a while now. It’s CLI-driven so it works super well with agents. It’s also the only platform with automatic content-based caching. I’d be happy to hop on a call if you want to see it.
English
1
0
0
50
Luke Ramsden
Luke Ramsden@lukerramsden·
GitHub Actions has become so unreliable I’m genuinely considering building my own CI/CD system on top of GCP infra
English
1
0
3
313
Dan Manges
Dan Manges@dan_manges·
@alvinsng @FactoryAI if you really want to cook use RWX. agents can run without a git push and content-based caching means your agents will never be waiting longer than necessary
English
1
0
1
463
Alvin Sng
Alvin Sng@alvinsng·
At @FactoryAI, every PR triggers 40+ CI checks, all finishing in under 6 minutes. Our automated guardrails are so fast and comprehensive that you can "merge recklessly". This is agent-native development
GIF
English
45
27
628
129.2K
Dan Manges retweetledi
Astasia Myers
Astasia Myers@AstasiaMyers·
Hot take 🔥: AI coding tools are about to make CI a big bottleneck in software development. We saw it before: AI → more code → code review became critical Now: AI → more commits → CI pipelines are collapsing AI coding agents require a new CI system.
David Boskovic@dboskovic

We refactored our CI this week from 5 minutes to about 15 seconds on a single bare metal machine. We've been shipping so many PRs that CI time was becoming both a cost center and bottleneck. 1/10th the cost 1/10th the time 100x the PRs

English
12
4
34
9.8K
David Boskovic
David Boskovic@dboskovic·
@dan_manges Nice. Definitely recommend exploring ways to get zfs setups. That 10s cache copy becomes 200ms if you can do it. I’d be interested in being a customer if so.
English
1
0
1
31
Dan Manges
Dan Manges@dan_manges·
You can build your own CI (this is impressive) or you can use RWX
David Boskovic@dboskovic

coming right up but TLDR Cut out all setup overhead (prev 30s, now about 1s) - ovh amd epic turin box with 128 cores and 256gb ram (1k/mo) - golden image of main with all cache loaded - zfs for instant copy of golden image (this is magic) - git fetch all every second for local mirror - golden image of database so only last migration runs (as Postgres template) - turbo cache locally For actual suites - much higher sharding since now no overhead to each shard - use @bunjavascript tests where possible to avoid typescript compilation - incremental typechecking with local cache Bypassing GitHub actions in favor of custom check suites - a few seconds of queue time saved - no action minutes billed (we hit 36k minutes in 3 days) For preview apps - JiT full stack preview apps (not deployed on each commit) - 2-3s cold start on any commit sha to a fully deployed full stack preview app - zfs clone of golden firecracker vm and then check out latest commit etc

English
1
0
5
712
Dan Manges
Dan Manges@dan_manges·
@dboskovic We actually allow starting runs from the CLI without a git push. Content-based caching has the clone cached, the CLI sends up a patch, the rest of the cache pulls at 250 MB/sec. If you have 2 GB of dependencies you’re ready to go in 10 seconds, even with ephemeral compute
English
1
0
0
27
David Boskovic
David Boskovic@dboskovic·
@dan_manges Didn’t know about you guys. What’s the hard setup time to test suite ready (code checked out, caches loaded) for a new sha on RWX?
English
1
0
1
48
Dan Manges
Dan Manges@dan_manges·
@ankrgyl @aayush_shah15 I’ve been building a new CI platform from first principles. Automatic content based caching, graph based task execution, and agent-native interfaces (CLI and semantic outputs instead of git push and logs). I’d love to know what you think.
English
1
0
1
317
Ankur Goyal
Ankur Goyal@ankrgyl·
Back before github, cloud, and containers were a thing, at memsql, we built our own git & CI infrastructure for a 100+ person team that ran on a couple bare metal machines. Builds (super complex C++ codebase) finished in 5 minutes and CI ran in 20 minutes end-to-end. Why? Files cached locally, no startup time, and incremental builds. Today, with the modern kluge of actions, VMs, sandboxes, snapshots, and caches it feels impossible to achieve this type of performance. I wonder if the constant onslaught of infrastructure challenges and increased performance demanded by coding agents will teleport us back to first principles in developing CI infrastructure. I hope it does.
English
11
4
176
17.1K
Dan Manges
Dan Manges@dan_manges·
“if someone else is always upstream, you can’t really redesign workflows or build anything that defensible”
signüll@signulll

while they require more capital fully verticalized startups like this are super fascinating to me cuz in the ai era the two things that matter are owning the underlying context & deploying intelligence on top of it. most ai startups do the latter on someone else's platform because it's easier to sell, i.e. you don't have to ask customers to rip out the whole god damn stack. but if someone else is always upstream, you can't really redesign workflows or build anything that defensible. in specific verticals where incumbent software is fragmented enough to allow rip & replace, you'll likely see more companies running the toast playbook which is to own the system of record then make every ai feature a retention mechanism rather than a standalone product.

English
0
0
4
567
Dan Manges
Dan Manges@dan_manges·
@jeff_weinstein we did. RWX is agent-native: run from the CLI instead of git push. get semantic, parsed errors in the CLI instead of downloading logs. automatic content-based caching to skip redundancy. when agents push the build is green and it passes instantly.
English
0
0
10
463
Jeff Weinstein
Jeff Weinstein@jeff_weinstein·
who is building the next great ci startup optimized for agent generate code? (there is about to be _extremely_ ci needs)
English
37
5
110
21.5K
Dan Manges
Dan Manges@dan_manges·
@ryancarson You should try RWX. Tell your agent to run `rwx run ci.yml` and fix any issues. By the time the agent pushes, everything will be working, and with content-based caching, the CI checks will instantly be green.
English
0
0
0
51
Ryan Carson
Ryan Carson@ryancarson·
Documentation drift - it's your new worse enemy when working with agents on large existing projects. I'm using a mix of CI checks, custom linters and GitHub actions to help battle this. My Code Factory setup, which includes a Design System, is starting to work really well.
English
39
1
138
13.5K
Dan Manges
Dan Manges@dan_manges·
@realmcore_ Enabling agents to run CICD directly is also especially high leverage. With RWX you can tell agents to run `rwx run ci.yml` and fix any issues. Then when the agent pushes, the build is fully cached and instantly goes green.
English
1
0
6
264
akira
akira@realmcore_·
Lots of simple, grindy dev tasks that used to be considered low ROI and now dramatically higher leverage: - Complete test coverage - A good devops config - Good CICD - Managing envs for dev, staging, and prod All this to say, process engineering is extremely high leverage now
English
27
28
529
16.7K
Dan Manges
Dan Manges@dan_manges·
@jarredsumner This is how RWX works. Prompt: Run `rwx run .rwx/ci.yml —wait`, fix any issues and rerun until successful, and then push and open a pull request. Running your agents through GitHub like humans used to do it will not be the workflow of the future.
English
0
0
0
60
Jarred Sumner
Jarred Sumner@jarredsumner·
Also, this should be one subcommand not 3. And it should have a —wait or —watch flag that waits until all checks finish but default to show the current logs for any that have already failed . If everything is pending and no failures yet then automatically wait. Basically, fail fast by default
English
5
0
47
10.7K
Jarred Sumner
Jarred Sumner@jarredsumner·
feature request for GitHub’s gh cli: a subcommand for agents monitoring PRs - view unresolved pr review comments as markdown or xml with file:line - show failing gh action logs, maybe filtered to near the error - show lint errors from gh actions
English
40
14
645
43.7K
Dan Manges
Dan Manges@dan_manges·
@martin_casado If you’re pushing large numbers of files into ephemeral sandboxes to start working, you’re doing it wrong. It’s possible to already have the files there when it’s mostly the same contents over and over again.
English
1
0
7
418
martin_casado
martin_casado@martin_casado·
It's amazing how quickly the conversation for AI sandboxes has shifted from lightweight compute, to maximizing IOPs for files.
English
15
4
191
17.1K
Dan Manges
Dan Manges@dan_manges·
@rauchg This has been the key to our success with RWX. It's an API for running code in the cloud, while every other CI/CD platform runs through version control webhooks instead of an API.
English
0
0
1
606

Keşfet

@ryancarson @bernhardsson @ziglang @richardartoul @lukerramsden @alvinsng @FactoryAI @dboskovic