Accelerate Testing and Development with Continuous Delivery: An Interview with Naga Jayadev


In this interview, Naga Jayadev of CA Technologies digs into continuous delivery, continuous testing, DevOps, and virtualization. He explains what he does at CA Technologies, the trends when it comes to testing, and the value of velocity within your development lifecycle.

Jennifer Bonine: All right. We are back with another virtual interview, and we have Naga with us. Naga, thank you for joining us.

Naga Jayadev: Welcome.

Jennifer Bonine: You come to us from CA, correct?

Naga Jayadev: I do.

Jennifer Bonine: Perfect. For those out there aren't familiar with your background, maybe give them a little context around your background and then we can maybe dive into that world of service virtualization, because I know a lot of people want to hear about that and where it's at. Tell us a little bit about your background.

Naga Jayadev: Yeah. I am the chief technologist for our continuous delivery business unit at CA. My goal is to help organizations on their digital transformation. This is about how can we lead into DevOps and make things more efficient, better quality, more resilient, and so on. We have ways we can plug-ins to the continuous delivery pipeline and look into things like continuous quality, continuous testing, continuous virtualization and so on. How does that manifest itself across the supply chain of your daily delivery cycle. That's my goal.

Jennifer Bonine: Interesting question for you. We hear about continuous integration, continuous delivery, and continuous deployment, right? You talked about continuous delivery. How are you seeing the adoption, or are you seeing the adoption and where, maybe, for a continuous deployment?

Naga Jayadev: Yup. There is. There is continuous deployment, just to separate that from continuous release. Deployment could be dev to test, test to stage, and so and so. The idea is how do you deploy frequently what are the inhibitors for you to stopping you from making sure that you have a continuous integration and continuous deployments cycles, right? Which is why service virtualization fits in.

The idea is how I can make sure ... If you look at a pipeline. I look at a manufacturing line and things move along and you don't want the line to stop. We're looking at things that are saying, "What are the big rocks that are making my line to stop?" What is stopping this manufacturing line from tuning out things at an efficient way?

When you look at deployment and the frequent releases that go on, virtualization is addressing a part of what is saying is if something stops me from doing my daily job, how can I make sure that that keeps moving on a day-to-day basis?

About the author

Upcoming Events

Oct 01
Oct 15
Oct 24
Nov 05