Build Libraries & InterfacesPriority-Lowbuggood first issuehacktoberfestlucene
仓库指标
- 星标
- (8,123 个星标)
- PR 合并指标
- (平均合并 5天 9小时) (30 天内合并 266 个 PR)
描述
Describe the bug
The ./gradlew run task allows plugin developers to launch a test cluster with the plugin pre-installed. This allows for quick development and testing cycles. This worked fine until 7.9 but has been broken since 7.10, and therefore in OpenSearch.
Plugin developers end up having to manually configure the 'run' task in their build.gradle file to launch a test cluster with the required plugins (and extended plugins) pre-installed.
Issues
- The 'run' task doesn't launch a test cluster.
- The test cluster launched by the 'integTest' task doesn't have the plugin pre-installed.
To Reproduce
- Create a simple OpenSearch plugin. For convenience, clone this OpenSearch plugin template - https://github.com/ketanv3/opensearch-plugin-boilerplate
- In the project's root directory, run
./gradlew run. - Gradle will be stuck at the
:runtask but no cluster will be launched.
Expected behavior A test cluster should be launched with the plugin (and extended plugins) pre-installed.
- A new test cluster should be created and registered for the 'run' task.
- For the test clusters launched by 'run' and 'integTest' tasks, pre-install the bundled plugin ZIP.
Host/Environment
- OS: Tested on macOS 11.2.3, Ubuntu 20.04.2 LTS
- Version: 1.0.0-rc1