Yes if you compare just the price of a compute minute, then it is fair to state that the per-minute price is more than other services or do-it-yourself Runner on public clouds. And, of course, with GitLab, you can easily attach a self-managed Runner to a group or project, as there are no limitations or additional pricing that would prevent you from doing so.
However, we believe that the value of the GitLab SaaS solution will save you additional overhead costs over the long term compared to a do-it-yourself build environment. And we will continue to add more value to GitLab SaaS in the coming months, which your developers will immediately be able to use.
Darren here - PM for GitLab Runner. At this time, we aren't considering adding Podman to GitLab SaaS Runners on Linux. I created this issue, so please add comments there so we can continue the discussion.
Hello - I am the product manager for GitLab Runner. The SIGTERM-related issues have been quite complex due to the different execution environments in which the Runner can operate. Can you add the details of your use case and workaround to the issue below? We need to take another look at this functionality, given the various reports of inconsistent behavior with long-running processes.
Yes if you compare just the price of a compute minute, then it is fair to state that the per-minute price is more than other services or do-it-yourself Runner on public clouds. And, of course, with GitLab, you can easily attach a self-managed Runner to a group or project, as there are no limitations or additional pricing that would prevent you from doing so.
However, we believe that the value of the GitLab SaaS solution will save you additional overhead costs over the long term compared to a do-it-yourself build environment. And we will continue to add more value to GitLab SaaS in the coming months, which your developers will immediately be able to use.