Welche DevOps-Tools sollten verwendet werden?
Which DevOps tools should be used?
In order to choose the right DevOps tools for applying the DevOps principles, it is particularly important that they meet the requirements of your own company. The following are known tools, categorized by objective:
- Continuous integration: Jenkins, Travis CI, Bamboo, Hudson, TeamCity or CircleCI
- Planning and collaboration: "DevOps JIRA", "DevOps Locker", Zoom, Clarizens or Ansana
- Source code management: SVN, "DevOps Git", Bit Bucket or "DevOps GitHub"
- Build: Ant, Maven, Grundzen or Gradle
- Configuration Management: Marionette, Chef, Ansible, Saltstack, Terraform or Hobo
- Continuous security: Snyk or Netsparker
- Test machines: Selenium, TestNG or JUnit
- Monitoring: Nagios, Sematext, Sensu, Datadog, Grafana, ELCH or New Relic
- Cloud hosting: AWS, azure or GCP
- Containerization / orchestration: "DevOps Docker" or "DevOps Kubernetes"
All of these DevOps tools help to implement the DevOps approach. In most cases, several DevOps tools are used in the sense of a DevOps toolchain (tool chain as a series of programs) for software development in order to develop and deliver a product along the DevOps cycle. Ongoing DevOps testing provides new input for improvements. In a DevOps course, you will learn more about DevOps tools:
- DevOps principle
- DevOps roles
- DevOps Open Source
- DevOps Login
- DevOps API and DevOps Rest API
- DevOps Git, DevOps GitHub and DevOps GitLab
- DevOps costs
- DevOps licenses
- DevOps KPI and DevOps Report
- DevOps Safe
