JAXenter: Why do we need continuous deployment? How can we use it to prevent problems from happening? (an example of a problem-solution situation would be great)
Michiel Rook: At the end of the day, it’s about meeting business demand. Moving fast (or slightly faster) than the business requires. CD enables companies to react faster to the market, be more in control of their product and (quickly) validate product ideas. Last but not least, it radically improves the time to recover from failures.
JAXenter: What tool do you use the most when setting up or managing a CI/CD pipeline?
Michiel Rook: I try not to be overly attached to one particular tool. My current project uses Jenkins, but I’ve used Travis, Circle, Gitlab and a few others in the past.
JAXenter: What do most people or businesses get wrong about CD?
Michiel Rook: Automation is a key (if not critical) part of successfully implementing CD. Manual gates, tests and processes are removed in favor of just enough, well-maintained, and fast automated solutions. Beyond that, an organization has to change. Barriers should be broken down and collaboration promoted.
JAXenter: What is your best tip or trick for avoiding downtime when implementing a database migration with CD?
Michiel Rook: Don’t block the pipeline by running long database migrations before you deploy code. Separate / split the steps. Always ensure backwards compatibility. Test your migrations on a (anonymized) copy of production data.
JAXenter: Can you tell us about a time when CI/CD failed and what you learned from it?
Michiel Rook: From a (development) team point of view, an unstable CI/CD pipeline can significantly hinder adoption and trust. A stable and fast pipeline that regularly delivers to production is essential.
JAXenter: What will participants be able to take away from your talk?
Michiel Rook: My first talk, attendees will hear my thoughts on what working in an Agile or DevOps environment means for a leader. We’ll discuss various theories, practical examples and what I consider to be effective leadership.
In my second talk, I’ll take attendees on a little tour of useful tools and a few strategies to migrate data safely, without causing (unintended) downtime. Some of the other topics that will be discussed are non-destructive changes, rollbacks and large data sets.
Thank you very much!