[CI Optimization]: Optimize Jenkins Pipeline for Efficient Resource Utilization #391
+67
−61
Conversation
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
Signed-off-by: Abukhoyer Shaik <[email protected]>
abukhoy
requested review from
quic-rishinr,
ochougul and
quic-amitraj
as code owners
Signed-off-by: Abukhoyer Shaik <[email protected]>
| stage('CLI and Vllm Tests'){ | ||
| parallel { | ||
| stage('CLI Tests') { | ||
| steps { |
There was a problem hiding this comment.
As discussed yesterday we need to avoid parallelism for CLI and VLLM Test.
Also we discussed to have 4 jenkin jobs corresponding to each PR.
There was a problem hiding this comment.
Yes, I am working on it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR optimizes the Jenkins pipeline to improve resource utilization, reduce testing time, and enhance parallelization. Key changes include:
Changes Made
CLI Teststo use -n 1.QNN CLITests to use -n 2.QNN Non-CLITests to use -n 2.Testing
Impact
Checklist
Note: It is on experiment stage, not final.