What are the dos and don’ts when going down the Continuous Delivery path? What are the most common obstacles that teams will hit when moving towards CD? JAXenter editor Gabriela Motroc talked with Tommy Tynjä, Senior Software Engineer and Continuous Delivery Consultant at Diabol at JAX DevOps 2018 about all this and more.
Organisations may have started with a simple release cycle with a small number of developers and QA testers but projects have quickly become more complex, requiring more developers, more teams and more time. In this article, Bob Davis explains why the case for continuous delivery management is likely to become indisputable over time.
DevOps has cultural change at its core but sometimes organizations find it hard to grasp the importance of the cultural aspect of DevOps. We invited Helen Beal, Head of DevOps at Ranger4 and speaker at JAX DevOps 2017 to talk about the contributing methodologies that converge and combine to drive DevOps evolution and to weigh in on the steps for DevOps success.
Continuous Delivery is the antidote for stressful, scary and fragile releases. A proper CD pipeline gives us the certainty that most of the mines got detected and disarmed and even if anything was overlooked, we have a way to quickly revert the damage. We invited Anton Weiss, Principal Consultant and CEO at Otomato and DevOps evangelist, to talk about the pitfalls of not putting continuous delivery into practice and the advantages of having a proper CD pipeline.
I learned the hard way building PaaS and SaaS frameworks, and perhaps there is no easy way, but here are some tips on how you can move beyond CI to CD by taking advantage of Jenkins Workflow.
It’s very easy for organizations to pick good practices from forward-looking companies and put them here and there, but truly effective teams are those that constantly question the status quo. We asked Eduards Sizovs, the leader of the Latvian Software Craftsmanship Community, to comment on the myth of one-size-fits-all Continuous Delivery, the importance of automation and more.
The idea that Continuous Delivery (CD) and DevOps can cut time to market and enable companies to ship higher quality code faster has driven widespread adoption. An impressive 65 percent of organizations are practicing CD on either their first project, or expanding and onboarding additional projects and teams, according to a DBMaestro survey.
Microservices and containers such as Docker are among the most discussed topics in the world of enterprise software today. Many DevOps practitioners are looking at these technologies as a key part of delivering large software projects faster. While successful implementations are most common among smaller, “born in the cloud” organizations, larger enterprises can benefit from microservices and containers too — as long as they address some challenges head-on.
“Continuous Delivery is a journey.” Organizations are complex systems, but if people and departments do not share the same goal, they are bound to fail. JAXenter editor Gabriela Motroc talked to Eduards Sizovs, leader of the Latvian Software Craftsmanship Community, at DevOpsCon about shadow continuous delivery and its pitfalls, and also about the importance of communication between teams and departments.
Sacha Labourey, CEO and founder of CloudBees, explains in this JAX London keynote how Jenkins-based DevOps and Continuous Delivery approaches are transforming software delivery processes.
The positive change that DevOps brings for enterprise IT is becoming more and more obvious. And yet DevOps success doesn’t come easily. When it comes to implementing a DevOps approach together with Continuous Delivery, the key to success is trust and visibility.
Continuous integration techniques are useful not only for project development, but also for software infrastructures. In this video tutorial, we find out how to improve infrastructure quality, reproducibility and speed with an infrastructure-as-code approach.
JAX London keynote speaker Jeff Sussna shares his progressive ideas regarding continuous delivery and system change with his proposal on pervasive refactoring. For Sussna, it will contribute to less overall failure, less cost and more robust systems.
Switching to continuous delivery means abandoning existing practices and habits, and applying and developing new ones. But it doesn’t need to be a fast change, says CD coach Eduards Sizovs.