New JIPP instance for Eclipse Leda
To prepare builds for the Eclipse Leda project, we need a CI instance.
Unfortunately, the system requirements for a Yocto/BitBake-based build system is very high:
- At least 150GB permanent disk space for hosting caches for downloads, temporary build artifacts and final build artifacts.
- An initial build takes up 50-100GB and 4-5 hours on a potent machine (16 vCPUs, 32GB RAM), as it downloads and compiles the whole operating system, linux kernel and all software packages on top.
- A permanent disk/storage is required to host the download and build caches, so subsequent builds only take 10-30 minutes instead of hours. It can be an external storage for these caches as well if it can be mounted into the build machine and has high bandwidth/low latency.
The Leda build process is comparable to the one from Eclipse Oniro, which is also based on Yocto/BitBake. See https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/pipelines
In our internal development environment, we're using some bigger Azure VMs as custom GitHub Runners, so that we can fully utilize GitHub Workflows features and have permanent disks for our caches.
Questions:
- Can we get a CI instance with enough permanent disk space on Eclipse infrastructure?
- Can it be integrated with GitHub Workflow, or do we need to work on gitlab.eclipse.org?
- Dedicated Agents from the CBI may just be enough to build, although the builds may take much longer due to less vCPUs.
- Can the setup from the Eclipse Oniro project be reused or used as a template?