5 ms·

No. It is not worth a time-scaled cost each month for them to start a job on my machines and store a few megabytes of log files. I'd happily pay a fixed monthl

No. It is not worth a time-scaled cost each month for them to start a job on my machines and store a few megabytes of log files. I'd happily pay a fixed monthly fee for this service, as I already do for GitHub. The problem here is that this is like a grocery store charging me money for every bag I bring to bag my own groceries. > But at $140 a month, how much time is that worth investing? It's not $140/month. It's $140/month today, when my company is still relatively small and it's just me. This cost will scale as my company scales, in a way that is completely bonkers.

breppp 10mo ago
> The problem here is that this is like a grocery store charging me money for every bag I bring to bag my own groceries. Maybe they can market it as the Github Actions corkage fee
otterley 10mo ago
> The problem here is that this is like a grocery store charging me money for every bag I bring to bag my own groceries. This is an odd take because you're completely discounting the value of the orchestration. In your grocery store analogy, who's the orchestrator? It isn't you.
- featherless 10mo ago
  Do you feel that orchestration runs on a per-minute basis?
  - otterley 10mo ago
    As long as they're reserving resources for your job during the period of execution, it does.
    - featherless 10mo ago
      Charging people to maintain a row in a database by the minute is top-tier, I agree.
      - deleted 10mo ago
        [deleted]
      - otterley 10mo ago
        If you really think that's all it is, I would encourage you to write your own.
        featherless 10mo ago
        It would be silly to write a new one today. Plenty of open source + indy options to invest into instead. For scheduled work, cron + a log sink is fine, and for pull request CI there's plenty of alternatives that don't charge by the minute to use your own hardware. The irony here, unfortunately, is that the latter requires I move entirely off of GitHub now.
__turbobrew__ 10mo ago
> It is not worth a time-scaled cost each month for them to start a job on my machines and store a few megabytes of log files If it is so easy why don’t you write your own orchestrator to run jobs on the hardware you own?

breppp 10mo ago

> The problem here is that this is like a grocery store charging me money for every bag I bring to bag my own groceries. Maybe they can market it as the Github Actions corkage fee

otterley 10mo ago

> The problem here is that this is like a grocery store charging me money for every bag I bring to bag my own groceries. This is an odd take because you're completely discounting the value of the orchestration. In your grocery store analogy, who's the orchestrator? It isn't you.

featherless 10mo ago
Do you feel that orchestration runs on a per-minute basis?
- otterley 10mo ago
  As long as they're reserving resources for your job during the period of execution, it does.
  - featherless 10mo ago
    Charging people to maintain a row in a database by the minute is top-tier, I agree.
    - deleted 10mo ago
      [deleted]
    - otterley 10mo ago
      If you really think that's all it is, I would encourage you to write your own.
      - featherless 10mo ago
        It would be silly to write a new one today. Plenty of open source + indy options to invest into instead. For scheduled work, cron + a log sink is fine, and for pull request CI there's plenty of alternatives that don't charge by the minute to use your own hardware. The irony here, unfortunately, is that the latter requires I move entirely off of GitHub now.

__turbobrew__ 10mo ago

> It is not worth a time-scaled cost each month for them to start a job on my machines and store a few megabytes of log files If it is so easy why don’t you write your own orchestrator to run jobs on the hardware you own?