AjDevops

개발 운영 팀은 통합을 목표로하는 소프트웨어 엔지니어링 문화와 관행입니다.

The DevOps movement aims to improve communication between developers and operations teams to solve critical issues such as fear of change and risky deployments. But the same way that Agile development would likely fail without continuous integration tools, the DevOps principles need tools to make them real, and provide the automation required to actually be implemented. Most of the so called DevOps tools focus on the operations side, and there should be more than that, the automation must cover the full process, Dev to QA to Ops and be as automated and agile as possible. Tools in each part of the workflow have evolved in their own silos, and with the support of their own target teams. But a true DevOps mentality requires a seamless process from the start of development to the end in production deployments and maintenance, and for a process to be successful there must be tools that take the burden out of humans.

Build automation Tools:

maven

Configuration Management Tools:

Ansible,Chef,Puppet,SaltStack

Continuous Integration Tools:

Jenkins,TeamCity

Continuous Monitoring Tools:

Nagios,Genios

Testing Tools:

JUnit

Version Control Tools:

SVN,GIT