ChipTuner on Nostr: Yeah thanks for the info! I have no intentions of using GitHub for anything personal ...
Yeah thanks for the info! I have no intentions of using GitHub for anything personal but worth getting an idea.
My E2EE testing can take upwards of 10 minutes now and run as a separate step (normal) I was just considering the minimal build time from source to running application binaries.
I've been trying to gauge this usage because we were considering offering CI as an option for GitCitadel (npub1s3h…75wz) but I was cautious because I know just building 2-3 of my projects at one time with testing can keep a cluster node busy enough it slows down the pipeline. With literally one client, me. If we extended that to a ~30 projects I'd need to scale to like full 48u rack full of compute, or come up with some kind of crafty scheduling scheme. Not sure if Jenkins allows for better hardware scheduling.
It would probably become pretty unaffordable to offer CI as a service on cloude compute.
My E2EE testing can take upwards of 10 minutes now and run as a separate step (normal) I was just considering the minimal build time from source to running application binaries.
I've been trying to gauge this usage because we were considering offering CI as an option for GitCitadel (npub1s3h…75wz) but I was cautious because I know just building 2-3 of my projects at one time with testing can keep a cluster node busy enough it slows down the pipeline. With literally one client, me. If we extended that to a ~30 projects I'd need to scale to like full 48u rack full of compute, or come up with some kind of crafty scheduling scheme. Not sure if Jenkins allows for better hardware scheduling.
It would probably become pretty unaffordable to offer CI as a service on cloude compute.