111–120 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.
>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.
I work at GitLab, but curious what your use case is for just VCS ? I assume your company has other solutions for the software lifecycle that you are happy with? Depending on the size of your org, If it's small GitLab CE is free and can readily handle VCS no problem, you won't have a support contract though.
Ye, just VCS. Nothing else.
Why do you ask? I don’t build my code/text. Hell I don’t even want to ever compile it. I like making code/text changes and play push and pull and sometimes merge. And reviews, don’t forget them. I’ve some peers who also like that. Maybe we do it just for the kicks. Maybe it pays as well. We want to do all of this on an excellent git platform with a fantastic intuitive UI; and we definitely want to pay for it. Just give us a solid VCS. What about that?
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…
They should have just focused on being the best vcs. Oh and you get what you pay for. Want to hire a bunch of mediocre engineers? you’ll get a bunch of half baked features
>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.
If the intent of the redesign was to make this more apparent, it also failed in that goal. Old and new both look like a fox. Old(er) tanuki-like logo for comparison https://gitlab.com/gitlab-com/gitlab-artwork/-/blob/9b07772f...
The intent of the redesign is for the logo to reflect GitLab's place at the center of the DevOps infinity loop.
Just be a really great vcs, that would make devs love you. Right now they are playing the atlassian game of checking feature boxes which are all built poorly.
Earlier quoted context omitted.
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.
Your logo is a fox to everyone though, doesn't really matter what the intent was.
https://gitlab.com/gitlab-com/gitlab-artwork/-/blob/9b07772f...
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…
Yeah this is a really bad direction for gitlab. All of their devops features are terrible. They don’t pay their engineers which is why everything is poorly built. They should have just focused on being the best vcs. Oh and you get what you pay for. Want to hire a bunch of mediocre engineers? you’ll get a bunch of half baked features
Mainly it's because I strongly prefer to orient most of my flow around Kubernetes deployments and namespaces tied to git metadata like commit sha or branch name, and thus far, I haven't found a better more interested way of doing so than GitLab.
Earlier quoted context omitted.
Real SREs are great. Who wouldn't want a Systems Engineer that codes and can interrogate kernel issues or a Software Engineer capable of writing their own compiler running your operations? Most companies, even if they hire these people, don't know how to use or listen to them though. What usually happens is they get lumped in with a bunch of Application Operations folks and it sours the idea entirely.
Yeah, this. There's a gulf between people like Brendan Gregg (my go-to example of a "Real SRE") and those I've actually worked with, who anointed themselves with the same title... As a side-note, is any tech group more keen on title inflation than SREs? In the time I've been a developer / software-engineer I've seen sys admin, DevOps, Cloud Ops, SRE... it's literally the same people.
By the way Brendan Gregg is a Performance Engineer not an SRE. I believe that's been his title for close to 20 years, according to the the bio in his books. I don't believe he has ever had the title SRE.
[1] https://cloud.google.com/blog/products/devops-sre/how-to-sta...
I mean I don't need all the ci cd but the project management like burn down chart Weighting and such
