DevOps Toolchain

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. These toolchains are expected to fit into one or more of the following categories, reflective of key aspects of the development and delivery process:

  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).

Source: YouTube


Snippet from Wikipedia: DevOps toolchain

A DevOps toolchain is a set or combination of tools that aid in the delivery, development, and management of software applications throughout the systems development life cycle, as coordinated by an organisation that uses DevOps practices.

Generally, DevOps tools fit into one or more activities, which supports specific DevOps initiatives: Plan, Create, Verify, Package, Release, Configure, Monitor, and Version Control.