Open DevOps is powered by Jira Software, the #1 tool used by agile teams.
Teams can focus on building and operating software while Open DevOps integrates Atlassian and partner tools automatically.
Bring your existing tools or swap out our tools with just a few clicks.
Open DevOps starts with Jira Software, Confluence, Bitbucket, and Opsgenie. Teams can easily add the tools they want, such as GitHub or GitLab, with a single click.
Toolchain Capabilities
In this blog they suggest a catalogue of examples, organized by the major phases in the DevOps process, describing the capabilities required for each and what tools can be used to achieve them:
Phase
Capabilities
Tools
Plan
Continuously gathering user feedback, organizing it into actionable inputs, and prioritizing those actions for your development teams.
Integrations and feature flags. Wherever you decide to scope your feature or project, it should be converted into user stories in your development backlog.
Jira
Confluence
Slack
Build
Production-identical environments for development.
Infrastructure as code.
Source control and collaborative coding.
Kubernetes
Docker
Ansible
Chef
Puppet
Terraform
Bitbucket
GitHub
Gitlab
Continuous integration and deployment
Continuous integration is the practice of checking in code to a shared repository several times a day, and testing it each time. That way, you automatically detect problems early, fix them when they’re easiest to fix, and roll out new features to your users as early as possible.
Code review by pull-requests requires branching.
Automatically apply your tests to development branches, and give you the option to push to main when branch builds are successful.
Jenkins
AWS
Bitbucket
CircleCI
Snyk
Sonarsource
Mabl
Sauce Labs
XRay
Zephyr SmartBear
Operate / Monitor
There are two types of monitoring that should be automated: server monitoring and application performance monitoring.
Software that is listening and recording data 24/7. Ongoing observability is a key capability for successful DevOps teams.
Tools that integrate with your group chat client so alerts go straight to your team’s room, or a dedicated room for incidents.
App Dynamics
Datadog
Slack
Splunk
New Relic
Opsgenie
Pingdom
Nagios
Dynatrace
Sumo Logic
Continuous feedback
Continuous feedback includes both the culture and processes to collect feedback regularly, and tools to drive insights from the feedback.
Continuous feedback practices include collecting and reviewing NPS data, churn surveys, bug reports, support tickets, and even tweets. In a DevOps culture, everyone on the product team has access to user comments because they help guide everything from release planning to exploratory testing sessions.
Look for applications that integrate your chat tool with your favorite survey platform for NPS-style feedback. Twitter and/or Facebook can also be integrated with chat for real-time feedback.