-
Notifications
You must be signed in to change notification settings - Fork 744
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
[Impacted Area Based PR testing] Roll out rest of the PR checkers #16565
base: master
Are you sure you want to change the base?
[Impacted Area Based PR testing] Roll out rest of the PR checkers #16565
Conversation
/azp run |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
a356ed8
to
3cd1ced
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
3cd1ced
to
f1cdc14
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
b33d3d7
to
f0635ec
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
619d7ba
to
122bf05
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-pipelines.yml
Outdated
- job: impacted_area_t0_2vlans_elastictest | ||
displayName: "impacted-area-kvmtest-t0_2vlans by Elastictest - optional" | ||
dependsOn: get_impacted_area | ||
condition: contains(dependencies.get_impacted_area.outputs['SetVariableTask.PR_CHECKERS'], '2vlans') |
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.
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.
“eq” is used to determine whether two strings are equal. In our case, we need to determine whether one string contains another string or one string in another string. As the value dependencies.get_impacted_area.outputs['SetVariableTask.PR_CHECKERS']
only can be a string, so we refrain from using overlapping string
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.
As we discussed, we will add a suffix for t0 and t1.
122bf05
to
c37676c
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
8c41cab
to
fbf1745
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
a470ed2
to
0b6d1aa
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
07d6c24
to
53ed317
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Description of PR
In #15666, we introduced a new approach to PR testing called Impacted Area-Based PR Testing. This model will be rolled out in phases. This PR implement the left PR checkers.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
In #15666, we introduced a new approach to PR testing called Impacted Area-Based PR Testing. This model will be rolled out in phases. This PR implement the left PR checkers.
How did you do it?
Roll out the left PR checkers.
How did you verify/test it?
Test by pipeline itself, to see if PR checkers are running as expected.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation