-
Notifications
You must be signed in to change notification settings - Fork 282
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
Custom jenkins job for running concurrent search tests #3729
Comments
From the offline discussion if this automation can be solved with Github Actions (using default GitHub Runners) that can be managed by @neetikasinghal and team, then the Jenkins solution is not required. @neetikasinghal and team, please test the execution using GH Actions https://docs.github.com/en/actions/quickstart and update with the results here. Sample examples of how we use the GH Actions in the build repo: |
The ask is if we can setup some automation (using the existing Jenkins mechanism from EE team) to run it automatically either on some events or as a cron at regular cadence. The command that needs to be executed will be below:
|
We were able to solve this via a github action: https://github.com/neetikasinghal/OpenSearch/actions/runs/5626243180/workflow |
Closing this issue as it was resolved using a different method. |
Is your feature request related to a problem? Please describe
Currently Search ITs do not run with Concurrent Search feature on the main branch as part of the gradle check. We are looking for a custom jenkins job that could run the tests with the feature flag on.
In order to run the tests, as of now, we need to run the command manually on the dev computer:
./gradlew :server:internalClusterTest --tests "org.opensearch.search.*" -Dopensearch.experimental.feature.concurrent_segment_search.enabled=true
Relates
Describe the solution you'd like
We would to have a jenkins job that can automatically run the tests with day with the feature flag on
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: