Commit 53f72bc5 authored by Mark Pundsack's avatar Mark Pundsack

Rearrange intersection

parent a9fd0aef
Pipeline #12414366 passed with stages
in 7 minutes and 19 seconds
......@@ -92,19 +92,31 @@ development, operations, and quality assurance.
*<small>Image by Rajiv.Pant, derived from Devops.png:, [CC BY 3.0](https://commons.wikimedia.org/w/index.php?curid=20202905)</small>*
There's also the DevOps tool chain definition, which includes everything from
code, to releasing, to monitoring.
For the most part, my personal interest in DevOps has been in that intersection.
We do great code management; we’ve done that for quite a while. How do we get
that code into production? How do we get it into QA?
Review apps are a great example that fits squarely in that tiny, little triangle
in the middle of the Venn diagram. You take your code, you deploy it, which is
an operations thing, but you have it deployed in a temporary, ephemeral, app,
just for QA people (or designers, product managers, or anyone who is not a
primary coder), so they can test your application for quality assurance, feature
assurance, or whatever.
But now, I'm looking beyond the intersection. Here's the [DevOps tool chain
definition](https://en.wikipedia.org/wiki/DevOps_toolchain) from Wikipedia:
![DevOps Toolchain](/images/blogimages/devops-strategy-devops-toolchain.png){: .shadow}
*<small>Image by Kharnagy (Own work) [CC BY-SA 4.0](http://creativecommons.org/licenses/by-sa/4.0), via Wikimedia Commons</small>*
Well, that’s everything. That’s not the intersection. That’s the union of
everything. And that's where things get confusing. Sometimes when people talk
about DevOps, they’re not talking about all of your code stuff. It’s the
intersection parts that are the interesting parts of DevOps. It’s the parts
where we let developers get their code into production easily. That slice, that
intersection, of the Venn diagram, that’s the interesting part about DevOps.
Well, that’s everything! That’s not the intersection; that’s the union of
everything from code, to releasing, to monitoring. And that's where things get
confusing. Sometimes when people talk about DevOps, they’re not talking about
all of your code stuff. It’s the intersection parts that are the interesting
parts of DevOps. It’s the parts where we let developers get their code into
production easily. That slice, that intersection, of the Venn diagram, that’s
the interesting part about DevOps.
Having said that, as a product company, we are going to deliver things that are
pretty squarely on the development side, and, eventually, we’re going to deliver
......@@ -115,21 +127,6 @@ fetched at this point, but it could happen. Why not? Just have GitLab be
your one operations dashboard, and then it’s not just about the intersection of
the DevOps, it’s the whole DevOps tool chain.
### Intersection
For the most part, my personal interest in DevOps has been in the intersection.
We do great code management; we’ve done that for quite a while. How do we get
that code into production? How do we get it into QA?
Review apps are a great example that fits squarely in that tiny, little triangle
in the middle of the Venn diagram. You take your code, you deploy it, which is
an operations thing, but you have it deployed in a temporary, ephemeral, app,
just for QA people (or designers, product managers, or anyone who is not a
primary coder), so they can test your application for quality assurance, feature
assurance, or whatever.
But now, I'm looking beyond the intersection.
So, that is the whirlwind, high-level summary of where we've been, and a little
bit about where we’re going. Now let's get into specific issues.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment