Continuous Integration

Are you now working with source code? Whether that’s Application Code, Infrastructure as Code, Database Schemas or Data Science workbooks as code, you may have heard of a term ‘Continuous Integration’ (CI). This is the process of regularly merging code, and running a series of automated builds/tests/checks to ensure that quality remains high in your production codebase. Find out more in this video.

You may have heard about Software Code or Infrastructure as Code. Well, in this video, we’ll be talking about pipelines as code. If you’re familiar with tools like Azure DevOps, Circle CI, GitHub, GitLab and Jenkins, you may notice a trend where these platforms are allowing you to define your pipelines as code. Throughout this video, we’ll be defining a multi-stage pipeline in Azure DevOps, and picking up some tips along the way.

Recently on Twitter, I was asked by @thegraycat on whether I knew of any resources to manage pipelines in version control. I sent across several top of mind thoughts over Twitter, but it got me thinking that there may be others with the same question and it could make a good blog post. So here we are, as I talk through some of my considerations for pipelines as code.