Continuous Delivery and DevOps

Continuous Delivery and DevOps

Introduction:

DevOps is the acronym given to the combination of Development and Operations. It refers to a collaborative approach to making the Application Development team and the IT Operations team of an organization seamlessly work with better communication.

DevOps History:

The DevOps movement started to coalesce some time between 2007 and 2008 when IT operations and software development communities raised concerns about what they felt was a fatal level of dysfunction in the industry.

Over the years DevOps has become quite the buzzword. Although DevOps has been challenging to describe because of its abstract nature, it’s described mainly as a culture change, where Dev and Ops teams collaborate to establish a more agile and reliable framework that counts on trust, transparency, and seamless communication to improve productivity and speed of software development from code commit to deploy.

Adoption of new techniques, better tools, and improved collaboration methods continue to be on the rise in the DevOps universe. Enterprises today are looking for automation in the area of continuous integration, continuous testing, and continuous delivery to facilitate their DevOps adoption.

DevOps TOOLS:

A typical DevOps process consists of 8 stages: plan, code, build, test, release, deploy, operate and monitor. There are a plethora of tools available — open-source and OEM solutions — that can be used for each of these stages and some across various stages. There’s no single magical tool to implement or facilitate DevOps. As organizations embark on their DevOps journey, they will have to research, evaluate and try various tools for various functionalities. To make it simple for DevOps teams, we have put together a list of 10 DevOps tools that can be used to achieve a successful DevOps transformation.

DevOps stages

#DevOps ToolsDevOps

Stages:

1.GitCode, Build

2.GradleBuild

3.SeleniumTest

4.JenkinsBuild, Test, Deploy

5.PuppetDeploy, Operate

6.ChefDeploy, Operate

7.DockerBuild, Deploy, Operate

8.KubernetesBuild, Deploy, Operate

9.AnsibleDeploy, Operate

10.eG EnterpriseMonitor

DevOps Practices:

The 7 key practices of DevOps are:

  • Configuration Management.
  • Continuous Integration.
  • Automated Testing.
  • Infrastructure as Code.
  • Continuous Delivery.
  • Continuous Deployment.
  • Continuous Monitoring.

26-Apr-2020

Continuous Delivery in DevOps:

Continuous integration is a DevOps software development practice where developers regularly merge their code changes into a central repository, after which automated builds and tests are run. Continuous integration most often refers to the build or integration stage of the software release process and entails both an automation component (e.g. a CI or build service) and a cultural component (e.g. learning to integrate frequently). The key goals of continuous integration are to find and address bugs quicker, improve software quality, and reduce the time it takes to validate and release new software updates.

Continuous Delivery:

What is continuous delivery in DevOps? AWS notes that continuous delivery is a DevOps software development practice where “code changes are automatically built, tested, and prepared for a release to production.

Pipeline Concept:

A DevOps pipeline is a set of automated processes and tools that allows both developers and operations professionals to work cohesively to build and deploy code to a production environment. ... This includes continuous integration, continuous delivery/deployment (CI/CD), continuous feedback, and continuous operations.

Different Phases in a Typical DevOps Pipeline. The core of a DevOps pipeline constitutes the following: continuous integration/continuous delivery (CI/CD), continuous testing (CT), continuous deployment, continuous monitoring, continuous feedback, and continuous operations.

Ultimate Goal:

The primary DevOps goal is to optimize the flow of value from idea to end-user. Obviously, there's a cultural change that must happen for a company to be successful with DevOps, so culture is a big focus, but the DevOps goal is to make the delivery of value more efficient and effective.

Conclusion:

DevOps is fundamentally changing how dev and ops are done today. And it will change how security is done, too. It requires new skills, new tools, and a new set of priorities. It will take time and a new perspective. So the sooner you get started, the better.DevOps is helping businesses in a tremendous way. It's bridging the gap between developers' need for change and operations' resistance to change and thus creates a smooth path for Continuous Development and Continuous Integration.





To view or add a comment, sign in

More articles by Vishnu Priya Ila

Others also viewed

Explore content categories