azure-pipelines
azure-pipelines copied to clipboard
Should we use a Azure Task?
spontoreau's Task might be a good basis for us. See discussion below
Original
Including
- Repo name(s)
- One or more repos
- One or more branches
- Folder hierarchy
Inputs
- Allow evolution
- Don't break CIs
- Simple, naiive case should not lead user to unstable resources
- If using branches for different versions, someone might naiively grab the URL for a master version of a script and we could end up breaking them
- Testability
- Azure Pipelines: each template repo has to be explicitly added in the
resources
- Easy changelog management