Building scalable Pipeline with Azure DevOps

  • Ensure your pipeline(main) is as short as possible as people who will be dealing with it may not be familiar...what we can do is create template or create modules in programming terminology and reference in our main pipeline.
  • Create separate Repo only to host your template/module and do not open access to all.
  • In separate repo let’s call it as azure-templates and create PARAM, variable and other task based template like, maven build task related, docker task related, helm task related etc. Key thing to note here only create template for static and global contain.
  • Once you have separate repo and template for all the reusable task, jobs, PARAM, variable it make life much more easy to build pipeline for multiple component of application.
  • Last part is to leverage “resources” as we talked earlier in this post in your pipeline to link your pipeline to your template/module repo. you can also add PARAM, variable that is pipeline specific.
  • This way we will be able to reference same template/module in multiple pipelines without re-inviting wheels in corporate teams and improve time to market or deployment.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store