-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Enable multiple pipeline testing per task with name-based discovery and optimized pipeline fetching. #21122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Enable multiple pipeline testing per task with name-based discovery and optimized pipeline fetching. #21122
Conversation
/azp run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refactors the task testing system to support multiple pipelines per task using name-based discovery and optimizes performance by reducing redundant pipeline fetches.
- Introduces automatic discovery of pipelines that share the task name.
- Reduces multiple fetch calls to a single pipeline-fetch at startup.
Comments suppressed due to low confidence (1)
ci/ci-test-tasks/test-and-verify-v2/src/index.ts:123
- [nitpick] The variable name 'allowParrallelRun' appears to have a typo; consider renaming it to 'allowParallelRun' for clarity.
let allowParrallelRun = true;
} else { | ||
runningTestBuilds.push(...runResult); | ||
console.log(`⚠️ No pipelines found starting with "${task}"`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change this to warning and use the original mesage from below - console.log(Cannot build and run tests for task ${taskName} - corresponding test pipeline was not found
);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated.
Context
Enable multiple pipeline testing per task with name-based discovery.
https://mseng.visualstudio.com/AzureDevOps/_workitems/edit/2221293
Task Name
Enhanced the canary test system to support multiple pipelines per task through automatic pipeline discovery and optimized pipeline fetching.
Description
Summarize the changes made in this PR clearly and concisely.
Changes
1. Multi-Pipeline Support
2. Performance Optimization
Example
For task WindowsMachineFileCopyV1, the system now automatically runs:
Risk Assessment (Low / Medium / High)
_Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility). Low
Unit Tests Added or Updated (Yes / No)
Indicate whether unit tests were added or modified to reflect these changes.
Canary Test Schedule run
Additional Testing Performed
List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).
Documentation Changes Required (Yes / No)
Indicate whether related documentation needs to be updated.
Checklist