3 ms·
Can't help but feel that their focus on moving all operation insights into gitlab itself will not be as successful as they want it to be (as far as I read, thei
by jbergstroem 7y ago
Can't help but feel that their focus on moving all operation insights into gitlab itself will not be as successful as they want it to be (as far as I read, their goal was to replace their operations and monitoring tools with gitlab itself[1]). I've worked with the ultimate edition for a year and the kubernetes integration is nowhere close to the insight you would get from google, amazon or azure in terms of insight and integration with ops-land. I wish all these hours were spent on improving the developer lifecycle instead.
I can understand how their huge success of "built-in CI" quickly leads to "built-in XYZ", but competing with github that lets other companies solve developer/ci problems via marketplace (and now CI via their new terraform actions) may lead to loosing market-leader [my take on their product] position for a code/test/review/merge ecosystem.
[1]: https://about.gitlab.com/2018/10/01/gitlab-product-vision/ https://about.gitlab.com/2018/10/01/gitlab-product-vision/
- dgruesso 7y agoHi jbergstroem. GitLab PM here. thanks for the feedback. Our vision is indeed ambitious and we recognize that not all of our categories are yet "complete" (more on our category maturity here https://about.gitlab.com/handbook/product/categories/maturity/ https://about.gitlab.com/handbook/product/categories/maturit...). While we are aiming to make GitLab a first class application for operators, we continue to focus on the developer lifecycle at the same time. You can see what each of our groups is focusing on upcoming releases here https://about.gitlab.com/direction/configure/#upcoming-releases https://about.gitlab.com/direction/configure/#upcoming-relea.... I'd love to learn what areas and level of insight you'd like to see in out application that would make you consider using it as your daily ops-land driver. Thanks.