mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-08 22:14:59 +00:00
28f1bc5d28
https://github.com/elastic/x-plugins/pull/3229 broke the possibility of building+testing x-pack without Kibana via dev-tools/ci by setting an option in ~/.gradle/gradle.properties as described in https://github.com/dliappis/x-plugins/blob/master/README.asciidoc, unless nvm is present. Conditionally execute the nvm/nodejs code only if `xpack.kibana.build=false` is not set in `~/.gradle/gradle.properties` Original commit: elastic/x-pack-elasticsearch@affb4ac711
= 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`).