91–100 of 131 posts
>DevOps Is at the Center of Gitlab Yeah, just had a call with them and they confirmed that for only VCS its not feasible to use their platform. What are people migrating to? I am looking at bitbucket again I guess.
Anyone have experience with gitlab's Auto-DevOps stuff? Haven't really had an opportunity to use it (I do use their CI product) but am curious how people who've tried it find it.
This is why we left Gitlab. DevOps become center part of Gitlab which we don’t use and need any of those feature. We all need a code storage, code review, issue tracking and the CI/CD. We would pay advance features of those (epics, multiple assignee, etc) but we have to pay super expensive top tier which includes unnecessary DevOps stuff. We left and happy so far. We are using Kubernetes and custom DevOps tools but d…
This is happening everywhere. The current industry cycle is one of scope expansion, moving away from the do one thing well paradigm. This will lead to bloated software that do a little bit of everything but not very well, which will trigger the next industry cycle, of doing one thing well paradigm.
Gitlab has too many half-baked features. Ive hit those issues at least a dosen times.
From the top of my head:
- Environment variables dont work with triggers
- MS Teams integration does not support multiple channels
- Masking doesnt work for all variables
- Code AutoDeploy quite often just breaks for no reason..
- Kubernetes integration is super poor
I would prefer to have fewer fearures that actually work well and have good support instead of bunch of stuff you have to sometimes wait years for to be fixed (looking at their issue tracker).
Earlier quoted context omitted.
This is happening everywhere. The current industry cycle is one of scope expansion, moving away from the do one thing well paradigm. This will lead to bloated software that do a little bit of everything but not very well, which will trigger the next industry cycle, of doing one thing well paradigm.
Ive started working with Gitlab in last few months for new contract and this was exactly what hit me hard. Gitlab has too many half-baked features. Ive hit those issues at least a dosen times. From the top of my head: - Environment variables dont work with triggers - MS Teams integration does not support multiple channels - Masking doesnt work for all variables - Code AutoDeploy quite often just breaks for no reason.…
[1] https://docs.gitlab.com/ee/user/clusters/agent/ [2] https://about.gitlab.com/direction/monitor/observability/#pr...
>DevOps Is at the Center of Gitlab Yeah, just had a call with them and they confirmed that for only VCS its not feasible to use their platform. What are people migrating to? I am looking at bitbucket again I guess.
As usual for Atlassian products, every click takes 1-2 seconds.
Finding comments requires manually scrolling. There is a filter function, but it takes some time to load. And even then, there's no way to sort comments chronologically. As a result, we would be constantly missing responses if it wasn't for the email notifications.
If a correction is made through force-push, you'll have no idea what was changed compared to the replaced commit.
The phone interface is unusable. On iPad, scrolling unintentionally adds comments.
There is a VSCode Plugin which is slightly better, but even there we frequently miss comments or changes.
Now, a question: Why established IT companies rarely understand the importance of the words "Identity" and "Brand Differentiation"?
Old logo was probably the cleverest rendering of a fox using very few lines. The new logo is a lot less smart, much more standard. Typography is also uninspiring: seems to be using Inter, which is designed to not have any character (pun not intended). Although, to be fair, old logo also had very basic typography.
The GitLab logo/mascot is actually a tanuki, a Japanese racoon dog. It symbolizes our values as a smart animal that works in a group to achieve a common goal.
You might as well have a bright yellow circle to represent the moon.
>DevOps Is at the Center of Gitlab Yeah, just had a call with them and they confirmed that for only VCS its not feasible to use their platform. What are people migrating to? I am looking at bitbucket again I guess.
Earlier quoted context omitted.
This is happening everywhere. The current industry cycle is one of scope expansion, moving away from the do one thing well paradigm. This will lead to bloated software that do a little bit of everything but not very well, which will trigger the next industry cycle, of doing one thing well paradigm.
Ive started working with Gitlab in last few months for new contract and this was exactly what hit me hard. Gitlab has too many half-baked features. Ive hit those issues at least a dosen times. From the top of my head: - Environment variables dont work with triggers - MS Teams integration does not support multiple channels - Masking doesnt work for all variables - Code AutoDeploy quite often just breaks for no reason.…
Still - I do like it overall
Ohhhhhhhh it just dawned on me that when GitLab says "DevOps" – they aren't confusingly saying "terraform, etc" type DevOps (Developer/Operations tasks combined), which is actually what everyone else means. I think they mean "the operations around running a development shop" ... like "Developer Operations." Silly, but makes so much of their random language about DevOps actually make sense now.