honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/x-pack/qa/smoke-test-plugins/build.gradle

32 lines
831 B
Groovy
Raw Normal View History

Build: Add back smoke test plugins for xplugins This checks that all ES plugins and xplugins are installed. I also changed the rest check to be a simple plugin count, so it does not fail when new plugins are added. Original commit: elastic/x-pack-elasticsearch@eaab182e4390f95e42755d9374fa165ef83b330d
2015-11-24 20:07:04 -05:00
import org.elasticsearch.gradle.MavenFilteringHack
Testclusters: conver remaining x-pack (#43335) Convert x-pack tests
2019-06-20 02:21:29 -04:00
apply plugin: 'elasticsearch.testclusters'
Switch from standalone-test to standalone-rest-test standalone-rest-test doesn't configure unit tests and for these integTest only projects that is what we want. Original commit: elastic/x-pack-elasticsearch@f576dfdfbbe8ddb901311ed94c03d84f9bf1bdd5
2017-01-04 14:27:53 -05:00
apply plugin: 'elasticsearch.standalone-rest-test'
Build: Add back smoke test plugins for xplugins This checks that all ES plugins and xplugins are installed. I also changed the rest check to be a simple plugin count, so it does not fail when new plugins are added. Original commit: elastic/x-pack-elasticsearch@eaab182e4390f95e42755d9374fa165ef83b330d
2015-11-24 20:07:04 -05:00
apply plugin: 'elasticsearch.rest-test'
7.x - Create plugin for yamlTest task (#56841) (#59090) This commit creates a new Gradle plugin to provide a separate task name and source set for running YAML based REST tests. The only project converted to use the new plugin in this PR is distribution/archives/integ-test-zip. For which the testing has been moved to :rest-api-spec since it makes the most sense and it avoids a small but awkward change to the distribution plugin. The remaining cases in modules, plugins, and x-pack will be handled in followups. This plugin is distinctly different from the plugin introduced in #55896 since the YAML REST tests are intended to be black box tests over HTTP. As such they should not (by default) have access to the classpath for that which they are testing. The YAML based REST tests will be moved to separate source sets (yamlRestTest). The which source is the target for the test resources is dependent on if this new plugin is applied. If it is not applied, it will default to the test source set. Further, this introduces a breaking change for plugin developers that use the YAML testing framework. They will now need to either use the new source set and matching task, or configure the rest resources to use the old "test" source set that matches the old integTest task. (The former should be preferred). As part of this change (which is also breaking for plugin developers) the rest resources plugin has been removed from the build plugin and now requires either explicit application or application via the new YAML REST test plugin. Plugin developers should be able to fix the breaking changes to the YAML tests by adding apply plugin: 'elasticsearch.yaml-rest-test' and moving the YAML tests under a yamlRestTest folder (instead of test)
2020-07-06 15:16:26 -04:00
apply plugin: 'elasticsearch.rest-resources'
Build: Add back smoke test plugins for xplugins This checks that all ES plugins and xplugins are installed. I also changed the rest check to be a simple plugin count, so it does not fail when new plugins are added. Original commit: elastic/x-pack-elasticsearch@eaab182e4390f95e42755d9374fa165ef83b330d
2015-11-24 20:07:04 -05:00
dependencies {
Remove deprecated usage of testCompile configuration (#57921) (#58083) * Remove usage of deprecated testCompile configuration * Replace testCompile usage by testImplementation * Make testImplementation non transitive by default (as we did for testCompile) * Update CONTRIBUTING about using testImplementation for test dependencies * Fail on testCompile configuration usage
2020-06-14 16:30:44 -04:00
testImplementation project(':x-pack:qa')
Build: Add back smoke test plugins for xplugins This checks that all ES plugins and xplugins are installed. I also changed the rest check to be a simple plugin count, so it does not fail when new plugins are added. Original commit: elastic/x-pack-elasticsearch@eaab182e4390f95e42755d9374fa165ef83b330d
2015-11-24 20:07:04 -05:00
}
Testclusters: conver remaining x-pack (#43335) Convert x-pack tests
2019-06-20 02:21:29 -04:00
int pluginsCount = 0
testClusters.integTest {
Convert testclusters to use distro download plugin (#44253) (#44362) Test clusters currently has its own set of logic for dealing with finding different versions of Elasticsearch, downloading them, and extracting them. This commit converts testclusters to use the DistributionDownloadPlugin.
2019-07-15 20:53:05 -04:00
testDistribution = 'DEFAULT'
Disable security for trial licenses by default (elastic/x-pack-elasticsearch#4120) This change disables security for trial licenses unless security is explicitly enabled in the settings. This is done to facilitate users getting started and not having to deal with some of the complexities involved in getting security configured. In order to do this and avoid disabling security for existing users that have gold or platinum licenses, we have to disable security after cluster formation so that the license can be retrieved. relates elastic/x-pack-elasticsearch#4078 Original commit: elastic/x-pack-elasticsearch@96bdb889fc74d4871c43df71354a21549cc53a3e
2018-03-21 23:09:44 -04:00
setting 'xpack.security.enabled', 'true'
Test: use trial license in qa tests with security QA tests that use security need to use a trial license instead of a basic license. Basic licenses do not enable security so these tests are not running in the expected configuration. This can also lead to issues that seem completely unrelated such as authentication failures right after cluster formation. The authentication failure right after cluster formation happens since a request makes it past the authentication license checks and the request starts the authentication process. During authentication the cluster forms and the license is updated to a basic license, which disables all realms. The request that is being authenticated then tries to iterate over the realms, but the realms are empty and the request cannot be authenticated. This results in a authentication failure even though the credentials provided are correct. Closes #30306
2018-05-03 12:33:08 -04:00
setting 'xpack.license.self_generated.type', 'trial'
Testclusters: conver remaining x-pack (#43335) Convert x-pack tests
2019-06-20 02:21:29 -04:00
user username: "test_user", password: "x-pack-test-password"
project(':plugins').getChildProjects().each { pluginName, pluginProject ->
Simplify adding plugins and modules to testclusters (#61886) There are currently half a dozen ways to add plugins and modules for test clusters to use. All of them require the calling project to peek into the plugin or module they want to use to grab its bundlePlugin task, and then both depend on that task, as well as extract the archive path the task will produce. This creates cross project dependencies that are difficult to detect, and if the dependent plugin/module has not yet been configured, the build will fail because the task does not yet exist. This commit makes the plugin and module methods for testclusters symmetetric, and simply adding a file provider directly, or a project path that will produce the plugin/module zip. Internally this new variant uses normal configuration/dependencies across projects to get the zip artifact. It also has the added benefit of no longer needing the caller to add to the test task a dependsOn for bundlePlugin task.
2020-09-03 22:26:44 -04:00
plugin pluginProject.path
Testclusters: conver remaining x-pack (#43335) Convert x-pack tests
2019-06-20 02:21:29 -04:00
pluginsCount += 1
Build: Add back smoke test plugins for xplugins This checks that all ES plugins and xplugins are installed. I also changed the rest check to be a simple plugin count, so it does not fail when new plugins are added. Original commit: elastic/x-pack-elasticsearch@eaab182e4390f95e42755d9374fa165ef83b330d
2015-11-24 20:07:04 -05:00
}
Require either BuildPlugin or StandaloneTestBasePlugin to use RestTestPlugin It used to be that RestTestPlugin "came with" StandaloneTestBasePlugin but we'd like to use it with BuildPlugin for the high level rest client. Also fix some license headers. Original commit: elastic/x-pack-elasticsearch@3d5549d170e7be1e19e03361dbeafde7653a9784
2017-01-03 15:43:22 -05:00
}
Build: Add back smoke test plugins for xplugins This checks that all ES plugins and xplugins are installed. I also changed the rest check to be a simple plugin count, so it does not fail when new plugins are added. Original commit: elastic/x-pack-elasticsearch@eaab182e4390f95e42755d9374fa165ef83b330d
2015-11-24 20:07:04 -05:00
ext.expansions = [
make smoke test plugins (and ssl) work again Original commit: elastic/x-pack-elasticsearch@3d2413823e3f8cc74fbf11adff154b8e7fa2db5a
2015-12-04 02:36:35 -05:00
'expected.plugins.count': pluginsCount
Build: Add back smoke test plugins for xplugins This checks that all ES plugins and xplugins are installed. I also changed the rest check to be a simple plugin count, so it does not fail when new plugins are added. Original commit: elastic/x-pack-elasticsearch@eaab182e4390f95e42755d9374fa165ef83b330d
2015-11-24 20:07:04 -05:00
]
processTestResources {
inputs.properties(expansions)
MavenFilteringHack.filter(it, expansions)
}