* Include branch information in build scans for buildkite jobs (#101284)
# Conflicts:
# build-tools-internal/src/main/groovy/elasticsearch.build-scan.gradle
* Align with other branches
* Update gradle wrapper to 8.3 (#97838)
Gradle now fully supports compiling, testing and running on Java 20.
Among other general performance improvements this release introduces --test-dry-run command line option that allows checking if tests are filtered or not by gradle.
Required updating nebula ospackage plugin as setuid was broken in gradle 8.3.
(cherry picked from commit b23e000c30)
# Conflicts:
# build-tools-internal/src/integTest/groovy/org/elasticsearch/gradle/internal/test/rest/LegacyYamlRestCompatTestPluginFuncTest.groovy
# build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/ElasticsearchJavaModulePathPlugin.java
# build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/test/rest/compat/compat/AbstractYamlRestCompatTestPlugin.java
# build-tools-internal/src/main/resources/minimumGradleVersion
# gradle/verification-metadata.xml
# gradle/wrapper/gradle-wrapper.jar
# gradlew
# x-pack/plugin/watcher/qa/with-monitoring/src/javaRestTest/java/org/elasticsearch/smoketest/MonitoringWithWatcherRestIT.java
* [7.17] Use patched nebula os package gradle plugin
* Update testingconvention precommit integ test
* Update Gradle Wrapper to 8.2 (#96686)
- Convention usage has been deprecated and was fixed in our build files
- Fix test dependencies and deprecation
We should only test snapshot version when running "check". Due to a
misswired task dependency, we were incorrectly running tests for the
full matrix of supported backward compatible versions.
The docker-compose plugin uses randomized auto-generated project names
for test fixtures. This can cause issues on some platforms where it will
generate an invalid identifier. This commit simply configures the plugin
to use the gradle project name for docker compose.
The standard Gradle `withType()` method that takes an action is the
"legacy" API which realizes tasks eagerly. To avoid this, we need to
explicitly use `configureEach()` to pass our configuration action.
Currently, the rest resources plugin relies on explicit project
configurations to wire up dependencies. This works for project
dependencies, but not for module dependencies, which are used when
bringing in these artifacts in a composite build. Add a unique usage
attribute to the api specs, tests, and xpack tests configurations so
they can be resolved in a composite or external build.
* Migrate core rest tests with security to new testing framework (#92575)
# Conflicts:
# x-pack/qa/core-rest-tests-with-security/build.gradle
* Fixes
* More fixes
* More fixes
* More more fixes
* Fixes for module projects in new tests clusters and auto security config (#92533)
Fix an issue where the build cannot resolve a module dependency for the
current module project. Also add partial support for security auto-
configuration in test clusters.
# Conflicts:
# build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/test/rest/RestTestBasePlugin.java
# modules/aggregations/build.gradle
# modules/aggs-matrix-stats/src/yamlRestTest/java/org/elasticsearch/search/aggregations/matrix/MatrixStatsClientYamlTestSuiteIT.java
# test/test-clusters/src/main/java/org/elasticsearch/test/cluster/local/LocalClusterHandle.java
* Post-merge fixes
* Spotless
This commit adds a new test framework for configuring and orchestrating
test clusters for both Java and YAML REST testing. This will eventually
replace the existing "test-clusters" Gradle plugin and the build-time
cluster orchestration.
