How to manage a multi-user task queue for building android images on a single machine

[Minghui Ma]

hi all,

What I'm looking for: On a single machine, a simple queue that accepts enqueues from multiple users to be run  sequentially for make android img.

Is there any software that does that. I've looked at task spooler.Is there anything better

[Music Pie]

Hello, can you tell me more about your project please

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/9c18b17c-5948-486e-969f-0b5e40943639o%40googlegroups.com.

[Igor Kukushkin]

Hello,

There's no single best optimization solution for that; If you do multiple devices or build types at once, that's one optimization, if you do a single target but introduce lot of changes it is another optimization, if you also need chromium... In my setup I have/had some workers using btrfs snapshots, some with ram drives (200+gb disk IO per build is no joke, don't want to ruin my nvmes in a month), but in general if you need 5-6 builds a day, then this is sure an overkill to go that deep. Queueing based on changes is another thing (waiting to accumulate changes while not making whole builddir dirty isn't exactly a definition of easy CI pipeline).

The best thing I could possibly recommend is renting a moderately priced host for build server (64gb / some i7 / striped raid can be found under 50 eur/month), adding ccache, setting mitigations=off for kernel, doing a thorough check of installclean.mk's and setting up zram + lots of swap (bind mounts, overlayfs etc). Or if you possibly could be interested in a more straightforward solution to save more than a day of developer's work without spending rest of the weekend on unhealthy linux experimenting, send me an email and we'll find a solution.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CAJX%3DaXGp37NV07bzmOp6K68uofHf_h8ardcfTCW1evRykQN9tw%40mail.gmail.com.