Member-only story
Build Self-Service Pipeline to Deploy Self-Hosted Environment Agents on Azure Workloads — The Pre-Pipeline Phase
The foundational groundwork is set, the floor is mopped, and it’s time to start building the pre-pipeline that leverages the scripts in Azure Pipelines.
In the token phase, you’ve created a bunch of scripts responsible for fetching a Personal Access Token (PAT). Since Azure Pipelines can easily run PowerShell in step tasks, you can dot-source the scripts.
Because you are building the pipeline as a self-service capability, it makes sense to use the pipeline templates functionality Azure DevOps Services provided.
Using these templates, provide you with either one of two things:
- Advanced users can clone or fork the templates and change them if needed into their own projects
- Beginners can simply run the pipeline that you’ve exposed without knowing the underlying logic
If you want to follow along, you need a live Azure VM because you’ll learn how you can install the agent unattentively in this phase.
Let’s get it going first by bringing all the logic together and start creating YAML templates.
