DevOps workflow
The DevOps workflow is as follows:
- Atlassian Jira is used for writing requirements and tracking tasks.
- Based on the Jira tasks, developers checking code into the 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 the organization’s Artifactory repository tool Nexus
- Jenkins automatically picks the libraries from Artifactory and deploys it to Production.
- During Production deployment, Docker tool is used to create images and deploy the same code on multiple hosts.
- Once a code is deployed to Production, we use monitoring tools like Nagios are used to check the health of production servers.
There are so many factors at play here when it comes to CI/CD tooling that its a challenge to meet the "ideal". I found that one important factor (especially when it comes to larger organizations) is to ensure that at the very least there is an agreed tool set for all dev teams to follow and utilize.
Nice Info on DevOps workflow
Good
Typical vs Ideal? If you could start with a blank slate what would your ideal look like? More tools or less? (Disclaimer, I work for GitLab...A full DevOps Platform delivered as a Single Application)