mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-09 14:34:43 +00:00
8a3181ceed
To add support for jdk9 tests for x-pack we need a number of parameters for the jvm, passed in the gradle command. To resolve issues with arg passing through bash variables and improve readability, switch to an array construct for storing the arguments. Add new jdk9 target to allow execution of jdk-9-ea based tests in the CI infra. Relates: elastic/elasticsearch#4415 Relates: https://github.com/elastic/infra/issues/1573#issuecomment-267832307 Original commit: elastic/x-pack-elasticsearch@b41e5f4b98
= Elasticsearch X Plugins A set of Elastic's commercial plugins: - License - Security - Watcher - Monitoring = Setup You must checkout x-plugins and elasticsearch in the same directory as siblings. This elasticsearch checkout will be used when building x-plugins. = Build - Run unit tests: + [source, txt] ----- gradle clean test ----- - Run all tests: + [source, txt] ----- gradle clean check ----- - Run integration tests: + [source, txt] ----- gradle clean integTest ----- - Package X-Pack (wihtout running tests) + [source, txt] ----- gradle clean assemble ----- - Install X-Pack (wihtout running tests) + [source, txt] ----- gradle clean install ----- - If you don't work on the UI side of x-plugins, you can force gradle to skip building kibana by adding `xpack.kibana.build=false` to your `~/.gradle/gradle.properties`. Alternatively you add `-Pxpack.kibana.build=false` on the command line if you only want to do this on individual builds (or `-Pxpack.kibana.build=true` if you need to override having added this to your `gradle.properties`).