Skip to content
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

[manual] [PR:15667] feat: add parallel run toggle to pipeline #16128

Closed
wants to merge 1 commit into from

Conversation

cyw233
Copy link
Contributor

@cyw233 cyw233 commented Dec 18, 2024

Description of PR
Add parallel run toggle to pipeline definition

Summary:
Fixes # (issue) Microsoft ADO 29843837

Approach
What is the motivation for this PR?
We want to enable parallel run via pipeline, so we need to add the parallel run toggle to the pipeline definition

co-authorized by: [email protected]

Description of PR

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

Description of PR
Add parallel run toggle to pipeline definition

Summary:
Fixes # (issue) Microsoft ADO 29843837

Approach
What is the motivation for this PR?
We want to enable parallel run via pipeline, so we need to add the parallel run toggle to the pipeline definition

co-authorized by: [email protected]
@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@cyw233
Copy link
Contributor Author

cyw233 commented Dec 18, 2024

Original PR: #15667

Copy link
Collaborator

@yejianquan yejianquan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@yejianquan yejianquan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need to update test_plan.py in feature branches.
We download from master and then use,
@lerry-lee could you please confirm if the logic is still the same?

@cyw233
Copy link
Contributor Author

cyw233 commented Dec 18, 2024

We don't need to update test_plan.py in feature branches. We download from master and then use, @lerry-lee could you please confirm if the logic is still the same?

Confirmed with @lerry-lee: If the PR only contains changes to .azure-pipelines/run-test-elastictest-template.yml and .azure-pipelines/test_plan.py, then there's no need to cherry pick to feature branch as the internal pipeline will download them from GitHub master branch.

@cyw233 cyw233 closed this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants