4 ms·

DevOps is a methodology.

systemvoltage 5y ago
Well, I was trying to clarify this statement from OP: > 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. It reads to me like this: "We don't use DevOps features in Gitlab, but we use CI/CD pipelines in Gitlab". So it is contradicting. As they responded, CI/CD is a subset of DevOps methodology. I've used Gitlab and didn't know there were more DevOps tools other than their CI/CD features and runners. I am still slightly confused.
- sercand 5y ago
  DevOps is whole set of tools. Gitlab includes features like monitoring, code scanning, Kubernetes integration, docker registry, cloud security and protections. And those are $1188 per year per person. By CI/CD I mean good old Jenkins that runs on a computer in the office that builds iOS Apps and uploads them to Apple AppStore (of course current generation of CI/CD is much better). Gitlab CI/CD and runners were there much before this "Gitlab is the one DevOps platform" saga. Everyone in our company including HR, marketing, design people were also using Gitlab for task tracking. Therefore we need those fancy issue tracking features for better management. This features are in the tier that $1188/year per person. For the features we don't use is not something that we could afford.
  - systemvoltage 5y ago
    Ah got it, thanks. I wasn’t aware that they’ve built all this stuff.
- bogomipz 5y ago
  I thought the OP was maybe referring to Gitlab's "AutoDevOps" features which were introduced a few years ago. From their site: >"GitLab Auto DevOps is a collection of pre-configured features and integrations that work together to support your software delivery process." I remember upgrading a Gitlab instance at that time and ended up with an issue that was the result of the AutoDevOps feature set. It seemed that AutoDevops was turned on by default. My issue was easy to resolve but I remember thinking at the time it was rather opinionated. [1] https://docs.gitlab.com/ee/topics/autodevops/ https://docs.gitlab.com/ee/topics/autodevops/
andrewstuart2 5y ago
I think you're mistaken. DevOps is a very specific team allowed to touch the Jenkins box, and is the old branding for what is now SRE which are both just rebranded names for Systems Administration, but with Cloud certifications instead of Cisco and Dell. I kid. But this is just as much the meme I've encountered as Agile. Some successful company releases a book about something they do that's fundamentally different, and almost instantly enterprises across the globe have a department for that thing with that name. Progress.
- c17r 5y ago
  SRE jokingly stands for "SysAdmin, Really Expensive"
  - kodah 5y ago
    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.
    - vosper 5y ago
      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.
      - bogomipz 5y ago
        Your comments really come off as bitter. I think this maybe just says more about the companies you've worked for than anything else. SRE is a methodology and a pretty-well understood methodology at this point.[1] The actual title is less important than the practice. It also goes by different names at different companies, example at FB it's called Production Engineer. 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-start-and-assess-your-sre-journey https://cloud.google.com/blog/products/devops-sre/how-to-sta...

Well, I was trying to clarify this statement from OP: > 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. It reads to me like this: "We don't use DevOps features in Gitlab, but we use CI/CD pipelines in Gitlab". So it is contradicting. As they responded, CI/CD is a subset of DevOps methodology. I've used Gitlab and didn't know there were more DevOps tools other than their CI/CD features and runners. I am still slightly confused.

sercand 5y ago
DevOps is whole set of tools. Gitlab includes features like monitoring, code scanning, Kubernetes integration, docker registry, cloud security and protections. And those are $1188 per year per person. By CI/CD I mean good old Jenkins that runs on a computer in the office that builds iOS Apps and uploads them to Apple AppStore (of course current generation of CI/CD is much better). Gitlab CI/CD and runners were there much before this "Gitlab is the one DevOps platform" saga. Everyone in our company including HR, marketing, design people were also using Gitlab for task tracking. Therefore we need those fancy issue tracking features for better management. This features are in the tier that $1188/year per person. For the features we don't use is not something that we could afford.
- systemvoltage 5y ago
  Ah got it, thanks. I wasn’t aware that they’ve built all this stuff.
bogomipz 5y ago
I thought the OP was maybe referring to Gitlab's "AutoDevOps" features which were introduced a few years ago. From their site: >"GitLab Auto DevOps is a collection of pre-configured features and integrations that work together to support your software delivery process." I remember upgrading a Gitlab instance at that time and ended up with an issue that was the result of the AutoDevOps feature set. It seemed that AutoDevops was turned on by default. My issue was easy to resolve but I remember thinking at the time it was rather opinionated. [1] https://docs.gitlab.com/ee/topics/autodevops/ https://docs.gitlab.com/ee/topics/autodevops/

andrewstuart2 5y ago

I think you're mistaken. DevOps is a very specific team allowed to touch the Jenkins box, and is the old branding for what is now SRE which are both just rebranded names for Systems Administration, but with Cloud certifications instead of Cisco and Dell. I kid. But this is just as much the meme I've encountered as Agile. Some successful company releases a book about something they do that's fundamentally different, and almost instantly enterprises across the globe have a department for that thing with that name. Progress.

c17r 5y ago
SRE jokingly stands for "SysAdmin, Really Expensive"
- kodah 5y ago
  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.
  - vosper 5y ago
    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.
    - bogomipz 5y ago
      Your comments really come off as bitter. I think this maybe just says more about the companies you've worked for than anything else. SRE is a methodology and a pretty-well understood methodology at this point.[1] The actual title is less important than the practice. It also goes by different names at different companies, example at FB it's called Production Engineer. 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-start-and-assess-your-sre-journey https://cloud.google.com/blog/products/devops-sre/how-to-sta...