Viktor Farcic is a senior consultant at CloudBees, member of the Docker Captains, and author. He has coded in a plethora of languages (excluding Fortran)—Pascal (yes, he is old), Basic (before it got Visual prefix), ASP (before it got .Net suffix), C, C++, Perl, Python, ASP.Net, Visual Basic, C#, JavaScript, Java, Scala, etc. His current favorite is Go. Passionate about DevOps, microservices, continuous integration, delivery and deployment, and test-driven development, Viktor often speaks at community gatherings and conferences. He published The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices; The DevOps 2.1 Toolkit: Docker Swarm, and the Test-Driven Java Development. His random thoughts and tutorials can be found in his blog.
Why did your attempt to implement continuous delivery fail? There cannot be one answer that fits all scenarios. However, some prerequisites and steps should be taken in almost all cases. The chances are that you missed some, if not all, of the commandments that we’ll explore in this session.