microsoft / microsoft/Analysis-Services
Help: Continuous Integration Script to Run Rules Against Modified Datasets/Reports in Pull Request
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 732
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
Hey there,
I'm requesting help to modify the pbidevmode/sample-ado-pipelines/ContinuousIntegration-Rules.yml script to only run the rules based on the reports/datasets that were modified during the pull request.
Currently, I have 10 datasets in the repository, and the build pipeline checks all datasets. I would prefer if it only checked the dataset(s) that were modified.
Current Setup:
- Repository with 10 datasets.
- Build pipeline checks all datasets.
Desired Setup:
- Build pipeline should only check the dataset(s) modified in the pull request.
- Could someone guide me on how to achieve this modification? Any examples or references would be greatly appreciated.
Thanks in advance!
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 pbidevmode/sample-ado-pipelines/ContinuousIntegration-Rules.yml and trace how the build pipeline currently discovers and checks all datasets. Research how the pull request identifies modified reports or datasets, then verify the pipeline checks only those changed items while preserving the existing rules behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100