root
/
elasticsearch
mirror of https://github.com/elastic/elasticsearch.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity
elasticsearch/qa/smoke-test-multinode/build.gradle

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

33 lines
1.1 KiB
Groovy
Raw Permalink Normal View History

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.
2017-01-04 04:39:36 +08:00
/*
Update sources with new SSPL+Elastic-2.0 license headers As per the new licensing change for Elasticsearch and Kibana this commit moves existing Apache 2.0 licensed source code to the new dual license SSPL+Elastic license 2.0. In addition, existing x-pack code now uses the new version 2.0 of the Elastic license. Full changes include: - Updating LICENSE and NOTICE files throughout the code base, as well as those packaged in our published artifacts - Update IDE integration to now use the new license header on newly created source files - Remove references to the "OSS" distribution from our documentation - Update build time verification checks to no longer allow Apache 2.0 license header in Elasticsearch source code - Replace all existing Apache 2.0 license headers for non-xpack code with updated header (vendored code with Apache 2.0 headers obviously remains the same). - Replace all Elastic license 1.0 headers with new 2.0 header in xpack.
2021-02-03 05:41:39 +08:00
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
Add AGPLv3 as a supported license
2024-09-14 04:28:03 +08:00
* or more contributor license agreements. Licensed under the "Elastic License
* 2.0", the "GNU Affero General Public License v3.0 only", and the "Server Side
* Public License v 1"; you may not use this file except in compliance with, at
* your election, the "Elastic License 2.0", the "GNU Affero General Public
* License v3.0 only", or the "Server Side Public License, v 1".
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.
2017-01-04 04:39:36 +08:00
*/
Convert smoke test multinode (#92774)
2023-01-11 00:51:04 +08:00
apply plugin: 'elasticsearch.internal-yaml-rest-test'
Build: Get multi node smoke tests working This change adds back the multi node smoke test, as well as making the cluster formation for any test allow multiple nodes. The main changes in cluster formation are abstracting out the node specific configuration to a helper struct, as well as making a single wait task that waits for all nodes after their start tasks have run. The output on failure was also improved to log which node's info is being printed.
2015-11-23 06:46:47 +08:00
Smarter copying of the rest specs and tests (#52114) This PR addresses the unnecessary copying of the rest specs and allows for better semantics for which specs and tests are copied. By default the rest specs will get copied if the project applies `elasticsearch.standalone-rest-test` or `esplugin` and the project has rest tests or you configure the custom extension `restResources`. This PR also removes the need for dozens of places where the x-pack specs were copied by supporting copying of the x-pack rest specs too. The plugin/task introduced here can also copy the rest tests to the local project through a similar configuration. The new plugin/task allows a user to minimize the surface area of which rest specs are copied. Per project can be configured to include only a subset of the specs (or tests). Configuring a project to only copy the specs when actually needed should help with build cache hit rates since we can better define what is actually in use. However, project level optimizations for build cache hit rates are not included with this PR. Also, with this PR you can no longer use the includePackaged flag on integTest task. The following items are included in this PR: * new plugin: `elasticsearch.rest-resources` * new tasks: CopyRestApiTask and CopyRestTestsTask - performs the copy * new extension 'restResources' ``` restResources { restApi { includeCore 'foo' , 'bar' //will include the core specs that start with foo and bar includeXpack 'baz' //will include x-pack specs that start with baz } restTests { includeCore 'foo', 'bar' //will include the core tests that start with foo and bar includeXpack 'baz' //will include the x-pack tests that start with baz } } ```
2020-02-26 08:46:32 +08:00
restResources {
restTests {
includeCore '*'
}
Build: Rework integ test setup and shutdown to ensure stop runs when desired (#23304) Gradle's finalizedBy on tasks only ensures one task runs after another, but not immediately after. This is problematic for our integration tests since it allows multiple project's integ test clusters to be simultaneously. While this has not been a problem thus far (gradle 2.13 happened to keep the finalizedBy tasks close enough that no clusters were running in parallel), with gradle 3.3 the task graph generation has changed, and numerous clusters may be running simultaneously, causing memory pressure, and thus generally slower tests, or even failure if the system has a limited amount of memory (eg in a vagrant host). This commit reworks how integ tests are configured. It adds an `integTestCluster` extension to gradle which is equivalent to the current `integTest.cluster` and moves the rest test runner task to `integTestRunner`. The `integTest` task is then just a dummy task, which depends on the cluster runner task, as well as the cluster stop task. This means running `integTest` in one project will both run the rest tests, and shut down the cluster, before running `integTest` in another project.
2017-02-23 04:43:15 +08:00
}
Convert smoke test multinode (#92774)
2023-01-11 00:51:04 +08:00
dependencies {
clusterModules project(":modules:mapper-extras")
clusterModules project(":modules:ingest-common")
Synonym Mgmnt API: PUT request (#95895)
2023-05-31 16:48:56 +08:00
clusterModules project(":modules:reindex")
Fix synonyms API analyzers reloading (#97621)
2023-07-13 20:28:28 +08:00
clusterModules project(":modules:analysis-common")
Make the ShardsAvailabilityIndicator pluggable (#101394) * Make the ShardsAvailabilityIndicator pluggable This commit makes the `ShardsAvailabilityIndicator` pluggable. It currently provides the existing `ShardsAvailabilityHealthIndicatorService` (without moving it) for the `shards_availability` output in the health report API. This will allow us in the future to provide a separate `shards_availability` plugin to override the way that health is reported for shards.
2023-10-27 22:02:41 +08:00
clusterModules project(":modules:health-shards-availability")
Enable data-streams module in REST tests (#106875)
2024-03-29 00:31:50 +08:00
clusterModules project(":modules:data-streams")
Warn users if security is implicitly disabled (#70114) * Warn users if security is implicitly disabled Elasticsearch has security features implicitly disabled by default for Basic and Trial licenses, unless explicitly set in the configuration file. This may be good for onboarding, but it also lead to unintended insecure clusters. This change introduces clear warnings when security features are implicitly disabled. - a warning header in each REST response if security is implicitly disabled; - a log message during cluster boot.
2021-04-14 00:33:41 +08:00
}
Port QA projects to use javaRestTest and yamlRestTest (#86703) Do not use deprecated elasticsearch.rest-test plugin
2022-05-12 17:32:07 +08:00
tasks.named("yamlRestTest").configure {
Remove OSS specific distribution packaging (#69775) * Remove OSS projects from distribution packaging * Remove OSS flavor from ElasticsearchDistribution * Remove OSS handling from docker build setup
2021-03-03 20:39:29 +08:00
systemProperty 'tests.rest.blacklist', [
'cat.templates/10_basic/No templates',
'cat.templates/10_basic/Sort templates',
'cat.templates/10_basic/Multiple template',
].join(',')
QA: System property to override distribution (#30591) This configures all `qa` projects to use the distribution contained in the `tests.distribution` system property if it is set. The goal is to create a simple way to run tests against the default distribution which has x-pack basic features enabled while not forcing these tests on all contributors. You run these tests by doing something like: ``` ./gradlew -p qa -Dtests.distribution=zip check ``` or ``` ./gradlew -p qa -Dtests.distribution=zip bwcTest ``` x-pack basic *shouldn't* get in the way of any of these tests but nothing is ever perfect so this we have to disable a few when running with the zip distribution.
2018-05-16 05:16:16 +08:00
}