-
Notifications
You must be signed in to change notification settings - Fork 277
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
Adding orchestrator pipeline and refactoring testsuite job #523
Conversation
Signed-off-by: Himanshu Setia <setiah@amazon.com>
Signed-off-by: Himanshu Setia <setiah@amazon.com>
Codecov Report
@@ Coverage Diff @@
## main #523 +/- ##
=======================================
Coverage 69.65% 69.65%
=======================================
Files 59 59
Lines 1575 1575
=======================================
Hits 1097 1097
Misses 478 478 Continue to review full report at Codecov.
|
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.
Minor comments, most of the changes look good to me.
PerfTests: { | ||
build job: 'perf-test', | ||
parameters: [ | ||
string(name: 'opensearch_version', value: "${params.opensearch_version}"), | ||
string(name: 'build_id', value: "${params.build_id}"), | ||
string(name: 'architecture', value: "${params.architecture}"), | ||
string(name: 'test_run_id', value: "${TEST_RUN_ID}") | ||
] | ||
}, |
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.
- Do we want to get this in even though the job doesn't exist? I would prefer to hold off if this piece of code is un-used.
- Do we know if these params are good for perf test?
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.
- I have added a perf-test job in staging. The perf-test logic can be updated independent of the orchestrator DSL so it should be fine. Let me know if you have a strong preference otherwise.
- These common params should be good. The configurations around which rally tests to run can be part of the
opensearch-build
repo as code, similar to the test_manifest.yml config. Keeping the DSL simple and uniform will help avoid the need for frequent jenkins deployments.
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.
Sure, if we have a strong sense that this is the code I am good with it.
Feels like it is :)
Signed-off-by: Himanshu Setia <setiah@amazon.com>
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.
Thanks @setiah for this change!
This PR adds the DSL for orchestration pipeline and refactors the testsuite job to identify test-suite type based on the jenkins job name
Signed-off-by: Himanshu Setia setiah@amazon.com
Issues Resolved
#262
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.