I did as well! No issues any worse than people using habitually using "github" to mean "the remote git repository in the cloud".
I expect this will continue indefinitely until the product becomes little more than an AI training corpus and genericized trademark, similar to how our Xerox machines at work are actually made by Brother, while Xerox the actual brand has faded into obsolescence.
I will note that we don't use many of the CI/CD/issue tracking/wiki/etc. features, though both Github and Gitlab offer them. I'm sure they have their own particular quirks that may be a hassle to migrate between and have people relearn. I prefer to keep those tools separate, allowing the git repository be almost exclusively a git repository and spinning up other tools as needed.
We use GitLab ci, issue tracking, dep scanning, everything at work and I can report it is amazing. All self hosted and never had any issues. I’ve got our entire deployment process setup through GitLab ci and it’s been rock solid. It’s $150/month per seat for the ultimate tier, but it’s 100% been worth it for us.
Doesn't GitLab suffer from the same problem of pushing AI? They have many AI features, and position themselves as "The most-comprehensive AI-powered DevSecOps platform".
I'm not using any AI features, and I'm not even aware of any, but I did see it on their website too and it's a bit concerning. My hope is that it's just something they have to say right now and not a strategic direction. Otherwise I will definitely switch to self-hosting, even though the managed CI/CD in the cloud has been working very well for me.
I did as well! No issues any worse than people using habitually using "github" to mean "the remote git repository in the cloud".
I expect this will continue indefinitely until the product becomes little more than an AI training corpus and genericized trademark, similar to how our Xerox machines at work are actually made by Brother, while Xerox the actual brand has faded into obsolescence.
I will note that we don't use many of the CI/CD/issue tracking/wiki/etc. features, though both Github and Gitlab offer them. I'm sure they have their own particular quirks that may be a hassle to migrate between and have people relearn. I prefer to keep those tools separate, allowing the git repository be almost exclusively a git repository and spinning up other tools as needed.
We use GitLab ci, issue tracking, dep scanning, everything at work and I can report it is amazing. All self hosted and never had any issues. I’ve got our entire deployment process setup through GitLab ci and it’s been rock solid. It’s $150/month per seat for the ultimate tier, but it’s 100% been worth it for us.
Doesn't GitLab suffer from the same problem of pushing AI? They have many AI features, and position themselves as "The most-comprehensive AI-powered DevSecOps platform".
I'm not using any AI features, and I'm not even aware of any, but I did see it on their website too and it's a bit concerning. My hope is that it's just something they have to say right now and not a strategic direction. Otherwise I will definitely switch to self-hosting, even though the managed CI/CD in the cloud has been working very well for me.
As the kids would say, Gitlab CI is the GOAT.