Add build vs and test pipeline#21318
Merged
wangxin merged 23 commits intosonic-net:masterfrom Jan 17, 2025
Merged
Conversation
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
1 similar comment
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
xwjiang-ms
removed
Request for 202012 Branch
Cherry Pick Conflict_202012
Cherry Pick Conflict_202205
Request for 202205 Branch
Request for 202305 Branch
Cherry Pick Conflict_202305
Request for 202311 Branch
Cherry Pick Conflict_202311
Cherry Pick Conflict_202405
Request for 202405 Branch
Request for 202411 Branch
labels
wangxin
reviewed
Jan 16, 2025
| @@ -0,0 +1,135 @@ | |||
| pr: | |||
Contributor
There was a problem hiding this comment.
Is this pipeline supposed to be executed for each PR or be manually executed?
Contributor
Author
There was a problem hiding this comment.
It's manually executed, maybe need to set to pr: none
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wangxin
approved these changes
Jan 17, 2025
VladimirKuk
pushed a commit
to Marvell-switching/sonic-buildimage
that referenced
this pull request
Jan 21, 2025
Why I did it sonic-buildimage repo integrates submodule code into the image by creating submodule advance PRs. However, these PRs often fail, and as time passes or the number of submodule PRs increases, identifying which PR caused the test failure becomes increasingly challenging. To address this, we need a pipeline capable of quickly building a VS image based on specific submodule commit IDs and precisely running the failed tests. This approach will help us efficiently pinpoint the submodule PR responsible for the failure. How I did it Create a build VS and test pipeline, users could build VS image and run tests based on specific submodule name and id, branch, topology, test scripts, features.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why I did it
sonic-buildimage repo integrates submodule code into the image by creating submodule advance PRs. However, these PRs often fail, and as time passes or the number of submodule PRs increases, identifying which PR caused the test failure becomes increasingly challenging. To address this, we need a pipeline capable of quickly building a VS image based on specific submodule commit IDs and precisely running the failed tests. This approach will help us efficiently pinpoint the submodule PR responsible for the failure.
Work item tracking
How I did it
Create a build VS and test pipeline, users could build VS image and run tests based on specific submodule name and id, branch, topology, test scripts, features.
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)