3 ms·

Have you read the GitLab S-1? They have great retention with larger companies. Can you substantiate any of your claims? (FYI I have no horse in this race, I eva

by exhaze 5y ago

Have you read the GitLab S-1? They have great retention with larger companies. Can you substantiate any of your claims? (FYI I have no horse in this race, I evaluated GH vs GL recently and decided to stay on GH for now)

adduc 5y ago
From their S-1: > We do not have an adequate history with our subscription or pricing models to accurately predict the long-term rate of customer subscription renewals or adoption, or the impact these renewals and adoption will have on our revenues or operating results. For context, GitLab recently axed their lowest priced plan and grandfathered in existing users at cheaper rates for the next year. Their retention rate may drop once discounts run out and the new pricing kicks in. As to the parent's comment about "The Homer" and non-core features being bad, I'd point to their CI autoscaling solution as an example of being underdeveloped, over-marketed, and suffering from technical debt. Their autoscaler uses docker machine behind-the-scenes, which hooks into various cloud providers to abstract away the act of spinning up new VMs. It works reasonably well, but Docker has archived the repository and no longer supports the software. GitLab forked the repository and maintains it for critical fixes, but is not willing to develop or accept new features. It has been known to break against new versions of Docker, does not handle concurrency very well in new environments, and does not allow [1] executing multiple concurrent jobs within spun up VMs, despite marketing that it can [2]. While the autoscaler does work, it's limitations and quirks reduces it's utility and cost-savings significantly within smaller organizations. The technical debt leaves me doubting any improvements will come within the next few years as they try to architect a new solution to replace the existing one. I have no idea how GitLab compares in other areas, but within CI autoscaling it seems they're stuck with a cliff to climb down before they can move forward again. [1]: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2787#note_68200142 https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2787#no... [2]: https://about.gitlab.com/blog/2017/11/23/autoscale-ci-runners/ https://about.gitlab.com/blog/2017/11/23/autoscale-ci-runner...
- rossmohax 5y ago
  CI is moving in Kubernetes everywhere I know. Builtin kubernetes pod autoscaler can add capacity based on job queue length metric, so no need for docker machine anymore.
- Aeolun 5y ago
  To some extend, yes. On the other hand, they’re currently the only service where I can set up one VM, give it my AWS credentials, and have fully automated scaling. The hoops you have to jump through in Github are absolutely unfun.
vultour 5y ago
I never said they don't have retention with large companies. In fact I work at one that uses GitLab, which just proves the points in my comment - nobody uses features like issues, wiki, or pages because it's already established via other applications.

by exhaze 5y ago

adduc 5y ago

From their S-1: > We do not have an adequate history with our subscription or pricing models to accurately predict the long-term rate of customer subscription renewals or adoption, or the impact these renewals and adoption will have on our revenues or operating results. For context, GitLab recently axed their lowest priced plan and grandfathered in existing users at cheaper rates for the next year. Their retention rate may drop once discounts run out and the new pricing kicks in. As to the parent's comment about "The Homer" and non-core features being bad, I'd point to their CI autoscaling solution as an example of being underdeveloped, over-marketed, and suffering from technical debt. Their autoscaler uses docker machine behind-the-scenes, which hooks into various cloud providers to abstract away the act of spinning up new VMs. It works reasonably well, but Docker has archived the repository and no longer supports the software. GitLab forked the repository and maintains it for critical fixes, but is not willing to develop or accept new features. It has been known to break against new versions of Docker, does not handle concurrency very well in new environments, and does not allow [1] executing multiple concurrent jobs within spun up VMs, despite marketing that it can [2]. While the autoscaler does work, it's limitations and quirks reduces it's utility and cost-savings significantly within smaller organizations. The technical debt leaves me doubting any improvements will come within the next few years as they try to architect a new solution to replace the existing one. I have no idea how GitLab compares in other areas, but within CI autoscaling it seems they're stuck with a cliff to climb down before they can move forward again. [1]: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2787#note_68200142 https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2787#no... [2]: https://about.gitlab.com/blog/2017/11/23/autoscale-ci-runners/ https://about.gitlab.com/blog/2017/11/23/autoscale-ci-runner...

rossmohax 5y ago
CI is moving in Kubernetes everywhere I know. Builtin kubernetes pod autoscaler can add capacity based on job queue length metric, so no need for docker machine anymore.
Aeolun 5y ago
To some extend, yes. On the other hand, they’re currently the only service where I can set up one VM, give it my AWS credentials, and have fully automated scaling. The hoops you have to jump through in Github are absolutely unfun.

vultour 5y ago

I never said they don't have retention with large companies. In fact I work at one that uses GitLab, which just proves the points in my comment - nobody uses features like issues, wiki, or pages because it's already established via other applications.