Parliament of South Australia
This project involved migrating legacy CI/CD pipelines to modern Azure DevOps pipelines, focusing on creating streamlined workflows between environments such as development, UAT, and production. The objective was to enhance operational efficiency and facilitate a smooth transition to contemporary DevOps practices.
The project included providing guidance on the most effective ways to utilise the new pipelines, building new workflows tailored to specific client needs, and resolving bugs encountered in the legacy pipelines.
Additionally, an assessment was conducted to identify pipelines that had not been used for an extended period. This involved mapping these pipelines to cloud resources to determine their relevance and whether they were still operational. This comprehensive evaluation aimed to optimise the client’s DevOps processes, ensuring the retention of only essential and effective pipelines in the upgraded Azure DevOps environment.
The migration to YAML-based pipelines from legacy systems represents a significant advancement in the DevOps landscape. YAML pipelines offer greater flexibility, maintainability, and version control, allowing teams to define their build and deployment processes as code. This shift enables more streamlined collaboration among team members, as pipeline configurations can be stored alongside application code in version control systems. Unlike traditional graphical interfaces, YAML-based pipelines provide a clear, text-based format that simplifies the process of updating and iterating on CI/CD workflows. Overall, this transition fosters improved automation and a more efficient development lifecycle, aligning with modern practices in software development.
Stages and pre-approvals are essential components of modern CI/CD workflows, enhancing control and reliability during the deployment process. Stages break down the pipeline into distinct phases—such as build, test, and deploy—allowing for better monitoring and management of code changes. Pre-approvals add governance by requiring stakeholder reviews at critical points, mitigating risks associated with untested code. This structure fosters collaboration and ensures high quality and compliance standards while accelerating software delivery.
