Why CI/CD Continues to Evolve – InApps Technology is an article under the topic Devops Many of you are most interested in today !! Today, let’s InApps.net learn Why CI/CD Continues to Evolve – InApps Technology in today’s post !
Read more about Why CI/CD Continues to Evolve – InApps Technology at Wikipedia
You can find content about Why CI/CD Continues to Evolve – InApps Technology from the Wikipedia website
Continuous integration and delivery (CI/CD) has seen some radical changes during the past few years, especially for continuous delivery. While not so long ago, application development and delivery were exclusively for monolithic stacks, delivering software for microservices and container environments is a very different animal.
In this InApps Technology Maker podcast recorded at KubeCon+CloudNativeCon in October, guest Rob Zuber, chief technology officer, CircleCI, discussed the evolution of CI/CD from the perspective of CircleCI’s experience for over a decade.
Alex Williams, founder and publisher of InApps Technology, hosted this podcast.
Why CI/CD Continues to Evolve
Also available on Apple Podcasts, Google Podcasts, Overcast, PlayerFM, Pocket Casts, Spotify, Stitcher, TuneIn
CI/CD is “becoming fairly mainstream — people recognize that this is how we deliver software or how we aspire to deliver software. But the context into which we’re deploying our software has been changing significantly over the 10-year lifespan of CircleCI,” Zuber said. “When we started the company, everyone was building [monoliths] basically and now everyone is talking about microservices and containers and orchestration. We’re delivering in a very different world.”
Adapting to this new context has been an ongoing process for CircleCI ’s evolution as a software provider. “Making sure that we’re building the product that supports people as the way they build changes is really important and one of the things that we’re seeing develop as a trend is the complexity of production is increasing. We’re doing things to make the individual complexity for a developer smaller — like you can work on an individual service, but the overall system is getting harder to predict because you can change your service while I’m trying to change my service, and we don’t necessarily know about those two changes happening simultaneously, which is good, because it gives us the freedom to move quickly,” Zuber said.
“But then we need to be able to understand that those things could impact each other and so some of the issues that we’re seeing people run into are not occurring until all their software is in production. So, we extend how we help customers understand that their code is good all the way out into production and give them tools to manage the release process as they put capabilities in front of customers.”
DevOps teams’ needs and wants for CI/CD should continue to evolve and change — and it will be up to CircleCI and other CI/CD providers to adapt.
“Will people build new tools in a different context in terms of how we deliver? Our goal is not to be rigid about a particular approach, but rather to understand what it is the customer is trying to do, which is to get value to their customers — that’s what they care about,” Zuber said. “And so we are focused on spending our time figuring out how to help them do that effectively, as the environment around them is changing.”
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.