Know the facts

How green is your DevOps?

Pavan Belagatti

“Worked fine in dev — ops problem now” is a rather common one-liner but it’s also true. Mitigating the ‘fight’ between Dev and Ops is no easy job but that’s where DevOps comes into play. In this post, Pavan Belagatti explains the meaning of green DevOps.

The aim of DevOps is to mitigate the ‘fight’ between Dev and Ops and encourage a strong bond between the two so that the software development process can be as smooth as silk.

We have often seen this thing happening in organizations that don’t practice DevOps (or don’t practice it correctly).

Screen Shot 2017-01-31 at 1.51.52 PM

When the blame game starts, the other processes of software development are the ones that suffer and everything is delayed.

But now things have changed; now you know everything you need to know about the mistake that was made and can remove the problem like a Band-Aid: fast and painlessly — that’s the beauty of adapting to CI/CD and automation. Dealing with problems manually takes time and are the process is prone to mistakes whereas a proper CI/CD platform will be flawless. Therefore, choosing a proper CI/CD platform is of utmost importance. 

What is green DevOps?

Green DevOps is the term we use for doing DevOps the right way. It’s not only about practicing DevOps but about how well it goes.

Some questions to ask yourself:

  • Do your developers know about different DevOps tools?

If the answer is Yes, you are on the right (or green) track

  • Have the developers gone through proper DevOps training?

If the answer is Yes, you are on the right (or green) track

  • Do your developers often commit code to the master/main branch?

If the answer is Yes, you are on the right (or green) track

  • Does your organization believe in automation?

If the answer is Yes, you are on the right (or green) track


6 C’s of green DevOps

DevOps is not just any set of tools, it’s a culture that helps to deliver things faster. However, to practice DevOps, youneed to have a set of

need to have a set of DevOps tools, the willingness to change and the right attitude.

You need to know these 6 C’s of DevOps cycle to better understand the process:

1. Continuous business planning

In short, you need to identify the skills, outcomes, and resources needed.

2. Collaborative development

This starts with development sketch plan and programming.

3. Continuous testing

Unit and integration testing help increase the efficiency and speed of the development.

SEE ALSO: Fear of failure feeds our reluctance to change

4. Continuous release and deployment

A nonstop CD pipeline will help you implement code reviews and developer check-ins easily.

5. Continuous monitoring

This is needed to monitor changes and address errors and mistakes spontaneously whenever they happen.

6. Customer feedback and optimization

This allows for an immediate response from your customers, thus allowing you to modify things accordingly.

So let’s discuss: how green is your DevOps?



To read more about DevOps, download the latest issue of JAX Magazine:

People like Patrick Debois, Andrew Shafer and John Allspaw (to name a few) have given us the means to transform this group of concepts into a movement but now it’s time to focus on some of its facets: continuous delivery, business culture, cloud platforms, microservices and container technology. Let’s allow our authors to convince you that these ingredients are equally important to DevOps. Mark Hinkle, VP at The Linux Foundation will tell you what’s next for the effort to improve coordination between software developers and operations personnel while Justin Arbuckle, CTO & Agile, Lean and DevOps Transformation Leader for Sococo, Inc. will explain why measuring DevOps ROI is essential for companies that are embracing the industry’s forward movement.

Thirsty for more? Open the magazine and see what we have prepared for you.

Pavan Belagatti
Pavan is a DevOps influencer working at JFrog and a guest writer at various top-notch technology platforms.

Inline Feedbacks
View all comments