-
Notifications
You must be signed in to change notification settings - Fork 73
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
Add option to run BWC tests in distribution level #766
Conversation
Signed-off-by: Zelin Hao <zelinhao@amazon.com>
b6af132
to
a579602
Compare
Codecov Report
@@ Coverage Diff @@
## 2.x #766 +/- ##
============================================
+ Coverage 79.43% 79.49% +0.06%
- Complexity 4293 4295 +2
============================================
Files 302 302
Lines 17956 17956
Branches 1906 1906
============================================
+ Hits 14263 14274 +11
+ Misses 2790 2776 -14
- Partials 903 906 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Can this be targeted to |
Yeah currently the distribution build for our 3.0.0 are failing and we don't have a stable bundle to test on. So I'm targeting to 2.5 version for now. I could draft a new PR to onboard on main when we getting close. |
Got it. I think as long as this is tracked on the infra side this is fine, thanks! |
Description
Add option to run BWC tests in distribution level, which is running tests in the test cluster with latest distribution bundle installed and all plugins (included in the latest manifest) present.
The command to run BWC tests in distribution level would be
./gradlew bwcTestSuite -Dtests.security.manager=false -PcustomDistributionDownloadType=bundle
If property
customDistributionDownloadType
is not set nor set tobundle
, the BWC tests would be default to run in plugins level as previously configured.Issues Resolved
Part of opensearch-project/opensearch-build#2870
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.