Azure / Azure/azure-functions-dotnet-worker
Update CI pipelines to run when changes are made to templates
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 466
- Forks
- 215
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
Problem Statement
Today, if we make any changes to an azure pipeline CI template file, the CI pipelines that consume the template do not run; because of this, there is no validation that a change made to the templates didn't break the CI pipelines that use it.
The purpose of this story is to update our azure CI pipeline files so that those pipelines run on template changes to validate that the template changes did not break anything.
A clear example of this is our extension pipelines. We have a template that is used by all of the extension CI pipelines e.g. the Cosmos DB CI file. When we make changes to the extensions-ci.yml file, the cosmos DB extension CI pipeline should run to validate the changes are not breaking.
Tasks
- Update our azure CI pipelines and/or template files so that a template change triggers a pipeline run for any pipeline that consumes the template
Definition of done
- When an azure CI template file is changed, any CI pipelines using that template should be triggered as part of the PR
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with build/pipelines/templates/extensions-ci.yml and the consuming extensions/Worker.Extensions.CosmosDB/ci.yml file. Inspect how Azure pipeline triggers and template relationships are configured, then review the other consuming pipelines. Done means changing an Azure CI template triggers every pipeline that uses it, including the Cosmos DB extension pipeline, as stated in the definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100