DevOps workflow
DevOps workflow
DevOps is gaining more popularity day by day. Here are some benefits of
implementing
DevOps Practice.
Release Velocity: DevOps enable organizations to achieve a great release velocity.
We
can release code to production more often and without any hectic problems.
Development Cycle: DevOps shortens the development cycle from initial design to
production.
Full Automation: DevOps helps to achieve full automation from testing, to build,
release
and deployment.
Deployment Rollback: In DevOps, we plan for any failure in deployment rollback due
to a
bug in code or issue in production. This gives confidence in releasing feature
without
worrying about downtime for rollback.
Defect Detection: With DevOps approach, we can catch defects much earlier than
releasing to production. It improves the quality of the software.
Collaboration: With DevOps, collaboration between development and operations
professionals increases.
Performance-oriented: With DevOps, organization follows performance-oriented
culture in
2/71
which teams become more productive and more innovative.
Question: What Is The Typical DevOps workflow?
The typical DevOps workflow is as follows:
Atlassian Jira for writing requirements and tracking tasks.
Based on the Jira tasks, developers checking code into GIT version control system.
The code checked into GIT is built by using Apache Maven.
The build process is automated with Jenkins.
During the build process, automated tests run to validate the code checked in by a
developer.
Code built on Jenkins is sent to organization’s Artifactory.
Jenkins automatically picks the libraries from Artifactory and deploys it to
Production.
During Production deployment, Docker images are used to deploy same code on
multiple hosts.
Once a code is deployed to Production, we use monitoring tools like ngios are
used to check the health of production servers.
Splunk based alerts inform the admins of any issues or exceptions in production.