-
Notifications
You must be signed in to change notification settings - Fork 141
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
CI: Geo-Spatial Plugin integration test #3244
base: main
Are you sure you want to change the base?
CI: Geo-Spatial Plugin integration test #3244
Conversation
Could you update the code base and re-run the CI workflows again? |
7037704
to
d2d4c84
Compare
Checked the log from CI build, it's blocked by #3235. |
b288a80
to
efe579f
Compare
Signed-off-by: Andy Kwok <[email protected]> Remove redundent wrapper Signed-off-by: Andy Kwok <[email protected]> Github CI Signed-off-by: Andy Kwok <[email protected]> Update spotless Signed-off-by: Andy Kwok <[email protected]> Update gradle def Signed-off-by: Andy Kwok <[email protected]> Exclude geo IT from main integ-test Signed-off-by: Andy Kwok <[email protected]>
Signed-off-by: Andy Kwok <[email protected]>
efe579f
to
cf83890
Compare
@LantaoJin All tests are passing except |
@@ -261,6 +297,11 @@ testClusters { | |||
plugin(getJobSchedulerPlugin()) | |||
plugin ":opensearch-sql-plugin" | |||
} | |||
integTestWithGeo { |
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.
Is there a specific reason for separating integTestWithGeo from integTest?
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.
integTestWithGeo
got separated as it requires an additional plugin Geo-spatial
, by having a separate build target with external deps will help troubleshot in the case of build failure.
Similar to the existing build target: integTestWithSecurity
.
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.
by having a separate build target with external deps will help troubleshot in the case of build failure.
could u elberate more on this. i think integTest already have clear hint on failed test cases.
If Geo command/function is native PPL feature, and OpenSearch release by defalut included geo-spatial plugin It not necessary to sepreate it from integTest. The geo-spatial use case is more similar to job-scheduler, instead of security plugin.
Description
This is a PR which aim to introduce a new IT test to assert and make sure the existing project setup and logic will work when Geo-Spatial installed within the same cluster.
High-level code changes include:
integTestWithGeo
to demonstrate the compatibility of Geo-Spatial and SQL plugininteg-tests-with-geo.yml
to run IT as the separate GitHub job.build.gradle
to promote code reuse betweenintegTestWithGeo
andintegTestWithSecurity
build targetnew Callable<RegularFile>()
wrapperTest-plan:
Related Issues
Resolves: #3037
Check List
--signoff
.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.