this post was submitted on 14 Jan 2026
44 points (92.3% liked)
Technology
79015 readers
3168 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Damn you're running a whole production pipeline and it only takes two minutes? That's pretty good. I've worked with projects that take tens of minutes, if not hours, just to compile.
Now if I was running some dinky little solo dev project, I'd probably just use some system-local CI thing for rapid iteration, if my changes needed to go through CI at all. Maybe Jenkins if I was feeling fancy. But a big project with a bunch of users on a remote platform? Getting a result in just 2-3 minutes is awesome.
At work we have CI runs that take almost a week. On fairly powerful systems too. Multiple decades of a “no change without a test case” policy in a large project combined with instrumented debug builds…
Tbf we don’t run those on every single change though. The per change ones take a couple hours only.
We do it in several 'stages', we have a check pipeline to just compile a single component and run the unit tests, that takes perhaps 5 minutes.
Then we build a incremental AOSP build with the change on top. That takes about 40 minutes.
Then we run the incremental build together with all the other changes for the Das and Do a manual smoke test that the most important stuff works and when it does only then we merge all those changes from the previous day. That takes about two to three hours.
Then there is the nightly test where we build the latest main branch and do static code analysis. That takes forever like 4 hours or so.
Then there are release builds from scratch which also run all the google compliance tests for AOSP and those things run practically for more than a day.
It's a interesting test of your personal patiance :D. But I don't think it's possible to do it with GitHub Actions, we use zuul for it like BMW and Volvo: https://www.youtube.com/watch?v=Z8rofKRen3w