E

Questions on Earthly and GitLab CI

Summary

The user is using GitLab for CI with both Fleeting autoscaling runners and GitLab shared runners. They have questions about using Earthly, specifically regarding job parallelization on the same satellite potentially leading to memory issues, the cost implications of using both a self-hosted runner and a satellite VM, and how to parallelize jobs across multiple VMs without a satellite.

Status
open
Tags
  • GitLab
  • Earthly
  • CI/CD
  • GitLab
  • Earthly
  • Fleeting autoscaling runners
Source
#earthly
    n

    naftoligug

    9/11/2024
    1. Earthly parallelizes jobs. But it seems like they run on the same satellite, which means if jobs use a lot of memory it could run out?
    n

    naftoligug

    9/11/2024
    1. If I ran Earthly builds without a satellite, how would I parallelize jobs across multiple VMs?
    n

    naftoligug

    9/11/2024
    1. If I already have a (self) hosted runner, why should I pay for the compute time of that VM plus the satellite VM?
    n

    naftoligug

    9/11/2024

    Now if I want to use Earthly, there are some things I don't get.

    n

    naftoligug

    9/11/2024

    I use gitlab for CI. For some projects I'm using Fleeting to have my own autoscaling runners. Some projects use http://gitlab.com|gitlab.com shared runners. Now if I want to use Earthly, there are some things I don't get.

    1. Earthly parallelizes jobs. But it seems like they run on the same satellite, which means if jobs use a lot of memory it could run out?
    2. If I already have a (self) hosted runner, why should I pay for the compute time of that VM plus the satellite VM?
    3. If I ran Earthly builds without a satellite, how would I parallelize jobs across multiple VMs?