4 ms·
That's usually the wrong question, as people only make greenfield decisions once. If, however, you've been running GHE for years and have it integrated with ot
by _jal 5y ago
That's usually the wrong question, as people only make greenfield decisions once.
If, however, you've been running GHE for years and have it integrated with other tooling and workflows, and your developers understand it, the question is,
"Why would anyone rip all that out, replace it, reintegrate it and retrain everyone over a handful of features, most of which you don't care about?"
- stavros 5y ago"Because there's one feature we really care about". That's why we migrated to GitLab CI. We made some pretty complicated pipelines, with tens of stages, many of them dynamic, and it worked with minimal hassle. It was a great success story internally.
- sofixa 5y ago> "Why would anyone rip all that out, replace it, reintegrate it and retrain everyone over a handful of features, most of which you don't care about Functioning CI/CD for free is certainly a huge feature to care about. For a user moving between Github and Gitlab is at worst a slight annoyance, the UX and DX are pretty similar; most third-party tooling that isn't github.com ( SaaS) only supports both Github and Gitlab self-hosted (i'd even wager there are more tools that support self-hosted Gitlab than Github, the first is much more popular).