4 ms·
Don't want to discourage you. I've these questions: 1. Are you targeting startups or enterprises? 2. Do you foresee savings in the range of millions with this
by the_arun 1y ago
Don't want to discourage you. I've these questions:
1. Are you targeting startups or enterprises?
2. Do you foresee savings in the range of millions with this approach?
3. What if the ci/cd pipeline takes > x mins? should the laptop be turned on stayed connected to network during this time?
4. In an enterprise, a typical ci/cd pipeline get connected to other dependent services - eg. security pipeline (even 3P) etc. Now, every developer needs to onboard to those services?
- vishu42 1y ago1.) Well, both startups and enterprises. both can benefit from reduced costs. 2.) Haven't worked out any figure yet. 3.) I was thinking an agent could run on the laptop/machine exposing compute and making sure it doesn't sleep, also report availability i.e if it can schedule a job or not. 4.) Correct, it should be a drop-in replacement type of thing, where for instance only changing the runs-on bit in github actions should suffice. Machines could became part of a node-pool via vpn? and jobs could be scheduled on the ones that are available.