DevOps 2018
Automation Best Practice-DevOps Road-map
Refer previous article before continue to read Devops abstract-Automation Scope-Goals of DevOps
4. DevOps automation Best Practice
DevOps is more than just a set of practices. There are many that are used in the industry. The following section will list the top and commonly used practice in a DevOps automation process in an IT organization.
- Use a centralized source control system to maintain all code and project artifacts
- Build, test and integrate early in the project life cycle
- Automate build, test and deployment activities
- Adopt test-driven development (TDD) practices
- Adopt continuous integration and deployment
Concentrate on the process and not on the tools.It is better to be tool independent and a good process should have the ability to replace one tool with another without too much disruption.
5. DevOps Automation Implementation
Implementing a good DevOps automation process will benefit any organization to a great extent. This includes planning, developing, integration and automation.
There are a few product areas that can immediately benefit from some integration and automation tasks that will reduce the manual work involved, increase the responsiveness of support team and also optimize the resources used.
A typical DevOps automation implementation will integrate and automate the different process with tools appropriate to the customer and would look like the image below.
In order to address the DevOps automation processes were set up which fine-tuned processes as given below.
- Build and deployment processes across all projects were made consistent through Maven scripts. This also led to reuse of existing scripts.
- Jenkins CI was used as the continuous integration tool to develop a robust deployment framework. The CI tool reduced many of the manual activities such as manual build, manual testing, manual packaging etc.,
- Build and testing was automated using Jenkins plugins. Junit and Selenium frameworks were used to automate unit and acceptance testing.
- Jenkins dashboard was used as a unified project dashboard to monitor project status, build failures, code coverage and etc.,
- Notification plugin was used to alert the administrator in case of build failures.
- Automation and continuous integration reduced the average production release time.
6. DevOps Road-map
Manual: Start with an existing system which uses manual processes, traditional release and deployment activities.
Automation : Identify tasks and process which can be automated. In the automated phase will implement standard set of processes to manage development and release activities.
Optimized : In the Optimized phase will be implementing with truly self service environment with a continuous improvement model and unified processes.
Continue to read DevOps Transformation strategy approach- Devops Automation Framework
Continue to read DevOps Transformation strategy approach- Devops Automation Framework
DevOps-Continuous Integration- Jenkins Basics for Beginners
Why we need Jenkins?
Manage Jenkins
Jenkins build job-Build a free-style software project-testing on multiple environment
Notification set-up-email-sms in Jenkins
Source Code Management section-build jobs in Jenkins
Artifact archive-Status Ball indication of Jenkins dashboard
Trend Graph-Javadocs-Jenkins reporting
Code coverage metrics-build server for Jenkins
Slave machine-multiple build machines
No comments:
Post a Comment