DevOps Transformation-Strategy approach-Scope of DevOps automation-DevOps best practice

DevOps - 2018
Abstract-Automation Scope-Goals  

1. Abstract

Devops automation is fast assuming greater importance in deciding the agility of an enterprise. A robust DevOps automation setup is crucial for successful agile delivery and minimal risk. It's greatly optimizes release management costs and team productivity, resulting in reduced time to deliver the quality applications. At the same time, DevOps automation enables organizations to make rapid product release with increased quality and manage customer's expectations.

DevOps simply recognizes that manual processes are the enemy of fast value delivery, high productivity, and safety. But automation is not just about saving time. It also enables the creation of repeatable environments and processes, which are self-documenting and, therefore, easier to understand, improve, secure, and audit. The entire continuous delivery pipeline is automated to achieve a fast, Lean flow.

In this article we explore various aspects of DevOps automation. We look at key success attributes, main processes, tools and frameworks that play an elementary role in DevOps.

2. DevOps Automation Scope

DevOps automation is practice of optimizing development and operations activities through structured processes, automation and collaborations. It aims to synergize processes between Continuous Integrations, Continuous Deployment and Continuous Monitoring. 

2.1 In-Scope

Release management activities such as development, static code analysis, testing(Unit, Functional, Integration and Regression) and deployment will be automated using tools and scripts. This would greatly enhance team productivity and improve the quality of the deliverable.

Continuous and iterative delivery : Processes will be enable iterative delivery such that business capabilities and delivered in iterations and each iteration is thoroughly tested.

Early and iterative testing : Each release will be included with automation testing iteratively in early stages. This would reduce the defects rate and risk involved in regression testing.

Continuous integration : Carrying out frequent, integrated builds from a centralized source control system is key. Integrations with enterprise interfaces will be done iteratively to reduce integrating risk.

Governance : standard set of well-defined processes will be established for release management and deployment.

Agility : All processes related to development, Integration, testing and release and deployment will be agile so that it is easy to absorb, test and deploy changes.

2.2 Out of Scope

Based on your industry policy and technical challenges in your project out of scope will be defined.

3. Goals of DevOps Automation

• Standardized processes
• Increased collaboration across all teams using automated process and Consistent goals.
• Iterative / Agile development and testing with incremental releases
• Reduced cost, effort and time to market
• Automation testing and continuous validations
• Reduced cost and risk due to Continuous integration and testing
• Continuous Deployment
• Continuous monitoring
• Automated, on-demand, infrastructure provisioning with metrics-based monitoring.

Continue to Read : Devops Transformation  strategy approach-Automation Best Practice-DevOps Road-map

Jenkins FAQ
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