Dev Ops 2
Dev Ops 2
org/wiki/DevOps
[c][d]
From an academic perspective, Len Bass, Ingo Weber, and Liming Zhu — three computer science
researchers from the CSIRO and the Software Engineering Institute — suggested defining DevOps
as "a set of practices intended to reduce the time between committing a change to a system and the
change being placed into normal production, while ensuring high quality".[6]
History
In 2009, the first conference named devopsdays was held in Ghent, Belgium. The conference was
founded by Belgian consultant, project manager and agile practitioner Patrick Debois.[8][9] The
conference has now spread to other countries.[10]
In 2012, the State of DevOps report was conceived and launched by Alanna Brown at Puppet.[11][12]
As of 2014, the annual State of DevOps report was published by Nicole Forsgren, Gene Kim, Jez
Humble and others.[13][14] In 2014, they found that DevOps adoption was accelerating.[13] Also in
2014, Lisa Crispin and Janet Gregory wrote the book More Agile Testing, containing a chapter on
testing and DevOps.[15][16]
Toolchains
As DevOps is intended to be a cross-functional mode of working, those that practice the
methodology use different sets of tools—referred to as "toolchains"—rather than a single one.[17]
These toolchains are expected to fit into one or more of the following categories, reflective of key
aspects of the development and delivery process:[18][19]
1. Coding – code development and review, source code management tools, code merging
2. Building – continuous integration tools, build status
3. Testing – continuous testing tools that provide quick and timely feedback on business risks
4. Packaging – artifact repository, application pre-deployment staging
5. Releasing – change management, release approvals, release automation
6. Configuring – infrastructure configuration and management, infrastructure as code tools
7. Monitoring – applications performance monitoring, end-user experience
Some categories are more essential in a DevOps toolchain than others; especially continuous
integration (e.g. Jenkins, Gitlab, Bitbucket pipelines) and infrastructure as code (e.g., Terraform,
Ansible, Puppet).[20][21]
Forsgren et al. found that IT performance is strongly correlated with DevOps practices like source
code management and continuous delivery.[13]
2 of 11 30-01-2020, 16:05