-
Notifications
You must be signed in to change notification settings - Fork 0
Glossary
This page contains key terms and concepts used by the CWDS DevOps Engineering (DOE) team. Our goal in providing this glossary is that is should be readable by key technical and non-technical stakeholders as well as the general public. It is important that our stakeholders know what these concepts mean to us, the DevOps Engineering Team, because some of these concepts are only useful when presented in context.
Definitions are presented in "newspaper" format, with high-level introductions and details given in subsequent paragraphs. This list is not inclusive; if we have nothing to add to a definition provided by Wikipedia, we will not spend time trying to redefine it here.
Feedback or questions regarding these terms should be submitted to the DevOps GitHub Issues.
Build is used to describe the process of assembling software into a product as well as a specific, versioned output of that process. Build is one of the three primary DOE disciplines practiced by CWDS.
Synonyms: DOE At CWDS, we distinguish between the practice of DevOps and the team responsible for executing the core engineering disciplines that are at its heart. The DOE Team sits at the center of the software development process, and bridges between business, development, and operations. We help development teams build and deploy their software, and help operations teams support that software and the infrastructure it runs on.
More information about the DOE team can be found at our DOE Team page.
We believe that DevOps is an organizational and cultural adoption of Agile engineering practices that address the anti-pattern separate silos for Development and Operations. The problem with these silos is that these two groups have competing needs and cultures, which can be a source of mistrust and reduced business value for information technology investments.