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

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

410 lines
15 KiB
Groovy
Raw Normal View History

Build: Consolidate dependencies specified in multiple places Some dependencies must be specified in a couple places in the build. e.g. randomized runner is specified both in buildSrc (for the gradle wrapper plugin), as well as in the test-framework. This change creates buildSrc/versions.properties which acts similar to the set of shared version properties we used to have in the maven parent pom.
2015-11-10 15:34:22 +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".
Build: Consolidate dependencies specified in multiple places Some dependencies must be specified in a couple places in the build. e.g. randomized runner is specified both in buildSrc (for the gradle wrapper plugin), as well as in the test-framework. This change creates buildSrc/versions.properties which acts similar to the set of shared version properties we used to have in the maven parent pom.
2015-11-10 15:34:22 +08:00
*/
Fix Gradle 4.3.1 compatibility for logging (#27382) The build currently does not work with Gradle 4.3.1 as the Gradle team stopped publishing the gradle-logging dependency to jcenter, starting with 4.3.1 (not sure why). There are two options: - Add the repository managed by Gradle team (https://repo.gradle.org/gradle/libs-releases-local) to our build - Use an older version (4.3) of the dependency when running with Gradle 4.3.1. Not to depend on another external repo, I've chosen solution 2. Note that this solution could break on future versions, but as this is a compileOnly dependency, and the interface we use has been super stable since forever, I don't envision this to be an issue (and easily detected by a breaking build).
2017-11-15 21:50:13 +08:00
Setup build benchmark jobs (#80941) Setting up automatic benchmark builds. This PR allows testing impact on build changes on the build performance by comparing the PR source against master and run different scenarios to verify build performance by using the gradle profiler (see https://github.com/gradle/gradle-profiler) they can be triggered by adding the `build-benchmark` GitHub label
2021-12-15 16:27:16 +08:00
import org.apache.tools.ant.filters.ReplaceTokens
import org.elasticsearch.gradle.internal.conventions.info.GitInfo
Remove deprecation warnings to prepare for Gradle 5 (sourceSets.main.output.classesDirs) (#30389) * Remove deprecation warnings to prepare for Gradle 5 Gradle replaced `project.sourceSets.main.output.classesDir` of type `File` with `project.sourceSets.main.output.classesDirs` of type `FileCollection` (see [SourceSetOutput](https://github.com/gradle/gradle/blob/master/subprojects/plugins/src/main/java/org/gradle/api/tasks/SourceSetOutput.java)) Build output is now stored on a per language folder. There are a few places where we use that, here's these and how it's fixed: - Randomized Test execution - look in all test folders ( pass the multi dir configuration to the ant runner ) - DRY the task configuration by introducing `basedOn` for `RandomizedTestingTask` DSL - Extend the naming convention test to support passing in multiple directories - Fix the standalon test plugin, the dires were not passed trough, checked with a debuger and the statement had no affect due to a missing `=`. Closes #30354 * Only check Java tests, PR feedback - Name checker was ran for Groovy tests that don't adhere to the same convections causing the check to fail - implement PR feedback * Replace `add` with `addAll` This worked because the list is passed to `project.files` that does the right thing. * Revert "Only check Java tests, PR feedback" This reverts commit 9bd9389875d8b88aadb50df57a45cd0d2b073241. * Remove `basedOn` helper * Bring some changes back Previus revert accidentally reverted too much * Fix negation * add back public * revert name check changes * Revert "revert name check changes" This reverts commit a2800c0b363168339ea65e2a79ec8256e5883e6d. * Pass all dirs to name check Only run on Java for build-tools, this is safe because it's a self test. It needs more work before we could pass in the Groovy classes as well as these inherit from `GroovyTestCase` * remove self tests from name check The self complicates the task setup and disable real checks on build-tools. With this change there are no more self tests, and the build-tools tests adhere to the conventions. The self test will be replaced by gradle test kit, thus the addition of the Gradle plugin builder plugin. * First test to run a Gradle build * Add tests that replace the name check self test * Clean up integ test base class * Always run tests * Align with test naming conventions * Make integ. test case inherit from unit test case The check requires this * Remove `import static org.junit.Assert.*`
2018-06-28 20:14:34 +08:00
plugins {
id 'java-gradle-plugin'
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
id 'groovy-gradle-plugin'
Remove deprecation warnings to prepare for Gradle 5 (sourceSets.main.output.classesDirs) (#30389) * Remove deprecation warnings to prepare for Gradle 5 Gradle replaced `project.sourceSets.main.output.classesDir` of type `File` with `project.sourceSets.main.output.classesDirs` of type `FileCollection` (see [SourceSetOutput](https://github.com/gradle/gradle/blob/master/subprojects/plugins/src/main/java/org/gradle/api/tasks/SourceSetOutput.java)) Build output is now stored on a per language folder. There are a few places where we use that, here's these and how it's fixed: - Randomized Test execution - look in all test folders ( pass the multi dir configuration to the ant runner ) - DRY the task configuration by introducing `basedOn` for `RandomizedTestingTask` DSL - Extend the naming convention test to support passing in multiple directories - Fix the standalon test plugin, the dires were not passed trough, checked with a debuger and the statement had no affect due to a missing `=`. Closes #30354 * Only check Java tests, PR feedback - Name checker was ran for Groovy tests that don't adhere to the same convections causing the check to fail - implement PR feedback * Replace `add` with `addAll` This worked because the list is passed to `project.files` that does the right thing. * Revert "Only check Java tests, PR feedback" This reverts commit 9bd9389875d8b88aadb50df57a45cd0d2b073241. * Remove `basedOn` helper * Bring some changes back Previus revert accidentally reverted too much * Fix negation * add back public * revert name check changes * Revert "revert name check changes" This reverts commit a2800c0b363168339ea65e2a79ec8256e5883e6d. * Pass all dirs to name check Only run on Java for build-tools, this is safe because it's a self test. It needs more work before we could pass in the Groovy classes as well as these inherit from `GroovyTestCase` * remove self tests from name check The self complicates the task setup and disable real checks on build-tools. With this change there are no more self tests, and the build-tools tests adhere to the conventions. The self test will be replaced by gradle test kit, thus the addition of the Gradle plugin builder plugin. * First test to run a Gradle build * Add tests that replace the name check self test * Clean up integ test base class * Always run tests * Align with test naming conventions * Make integ. test case inherit from unit test case The check requires this * Remove `import static org.junit.Assert.*`
2018-06-28 20:14:34 +08:00
id 'groovy'
Simplify applying build tools conventions (#73877) Share common conventions for build tools in one plugin. e.g. we always apply the license headers check for build tools too
2021-06-23 17:44:49 +08:00
id 'elasticsearch.build-tools'
Fix eclipse for build tools (#73699) apply common eclipse config to all projects across the elasticsearch workspace including build tools projects
2021-06-08 21:26:21 +08:00
id 'elasticsearch.eclipse'
Wrap VersionPropertiesLoader in a BuildService to decouple build logic projects (#78704) By using a BuildService we can decouple the configuration of projects but keep making expensive operations (e.g. parsing properties file or reading minimumJavaCompiler from file) only once per build. This bring us closer to decouple projects and get ultimatively configuration cache compliant. In general we will bring in more BuildServices for the main build to follow along that Pattern and ultimatevely remove usages of allprojects and subprojects in our build.
2021-10-08 00:00:21 +08:00
id 'elasticsearch.versions'
Format build-tools and build-tools-internal (#78910) Our spotless configuration wasn't being applied to `build-tools` and `build-tools-internal`. Move the Spotless configuration to a Java plugin in `build-conventions`, and apply it everywhere. This resulted in a lot more Java files being subject to formatting, so I added more exclusions to the list. Also remove the `paddedCell` stuff, we've never needed it.
2021-10-14 16:38:06 +08:00
id 'elasticsearch.formatting'
Remove deprecation warnings to prepare for Gradle 5 (sourceSets.main.output.classesDirs) (#30389) * Remove deprecation warnings to prepare for Gradle 5 Gradle replaced `project.sourceSets.main.output.classesDir` of type `File` with `project.sourceSets.main.output.classesDirs` of type `FileCollection` (see [SourceSetOutput](https://github.com/gradle/gradle/blob/master/subprojects/plugins/src/main/java/org/gradle/api/tasks/SourceSetOutput.java)) Build output is now stored on a per language folder. There are a few places where we use that, here's these and how it's fixed: - Randomized Test execution - look in all test folders ( pass the multi dir configuration to the ant runner ) - DRY the task configuration by introducing `basedOn` for `RandomizedTestingTask` DSL - Extend the naming convention test to support passing in multiple directories - Fix the standalon test plugin, the dires were not passed trough, checked with a debuger and the statement had no affect due to a missing `=`. Closes #30354 * Only check Java tests, PR feedback - Name checker was ran for Groovy tests that don't adhere to the same convections causing the check to fail - implement PR feedback * Replace `add` with `addAll` This worked because the list is passed to `project.files` that does the right thing. * Revert "Only check Java tests, PR feedback" This reverts commit 9bd9389875d8b88aadb50df57a45cd0d2b073241. * Remove `basedOn` helper * Bring some changes back Previus revert accidentally reverted too much * Fix negation * add back public * revert name check changes * Revert "revert name check changes" This reverts commit a2800c0b363168339ea65e2a79ec8256e5883e6d. * Pass all dirs to name check Only run on Java for build-tools, this is safe because it's a self test. It needs more work before we could pass in the Groovy classes as well as these inherit from `GroovyTestCase` * remove self tests from name check The self complicates the task setup and disable real checks on build-tools. With this change there are no more self tests, and the build-tools tests adhere to the conventions. The self test will be replaced by gradle test kit, thus the addition of the Gradle plugin builder plugin. * First test to run a Gradle build * Add tests that replace the name check self test * Clean up integ test base class * Always run tests * Align with test naming conventions * Make integ. test case inherit from unit test case The check requires this * Remove `import static org.junit.Assert.*`
2018-06-28 20:14:34 +08:00
}
Switch build system to Gradle See #13930
2015-10-30 02:40:19 +08:00
group = 'org.elasticsearch.gradle'
Build: Add fake project to include buildSrc as normal project This is a follow up to #18173 and includes adding pom generation to the fake build-tools project, which is really just buildSrc, but builds during normal builds.
2016-05-07 13:22:38 +08:00
Introduce build qualifier parameter (#35155) * Introduce property to set version qualifier - VersionProperties.elasticsearch is now a string which can have qualifier and snapshot too - The Version class in the build no longer cares about snapshot and qualifier.
2018-11-02 11:27:40 +08:00
// we update the version property to reflect if we are building a snapshot or a release build
// we write this back out below to load it in the Build.java which will be shown in rest main action
// to indicate this being a snapshot build or a release build.
Wrap VersionPropertiesLoader in a BuildService to decouple build logic projects (#78704) By using a BuildService we can decouple the configuration of projects but keep making expensive operations (e.g. parsing properties file or reading minimumJavaCompiler from file) only once per build. This bring us closer to decouple projects and get ultimatively configuration cache compliant. In general we will bring in more BuildServices for the main build to follow along that Pattern and ultimatevely remove usages of allprojects and subprojects in our build.
2021-10-08 00:00:21 +08:00
version = versions.getProperty("elasticsearch")
Use reproducible method of generating properties file for better caching (#42539)
2019-05-25 04:46:59 +08:00
Avoid creating gradle plugin publication (#69086) The java gradle plugin plugin allows to disable the automatic creation of a publication. This allows avoiding the publication at all instead of disabling the according tasks. We ship our own publication and dont need the automatically created one. Furthermore this avoids deprecated behaviour in Gradle 7.0 and above in having multiple publications with the same target artifacts
2021-02-17 17:04:13 +08:00
gradlePlugin {
// We already configure publication and we don't need or want the one that comes
// with the java-gradle-plugin
automatedPublishing = false
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
plugins {
build {
id = 'elasticsearch.build'
implementationClass = 'org.elasticsearch.gradle.internal.BuildPlugin'
}
Fix creation of large build job archives (#102023) * Fix large file and large path handling in build tar creating
2023-11-22 03:29:27 +08:00
buildComplete {
id = 'elasticsearch.build-complete'
implementationClass = 'org.elasticsearch.gradle.internal.ElasticsearchBuildCompletePlugin'
}
Avoid overhead of zip / unzip modules when packaging distribution (#84660) This removes the overhead of zipping up modules that are immediately unzipped again when packaging the elasticsearch distribution. We also move some logic for packaging the elasticsearch distribution into a plugin and remove some outdated overhead dealing with 'meta plugins' when copying modules into a distribution. Another follow up and related optimization out of scope of this PR is, to also not zip unzip modules declared for usage in our test cluster setups. This partially addresses #76726.
2022-03-15 18:37:47 +08:00
distro {
id = 'elasticsearch.distro'
implementationClass = 'org.elasticsearch.gradle.internal.distribution.ElasticsearchDistributionPlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
distroTest {
id = 'elasticsearch.distro-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.DistroTestPlugin'
}
dockerSupport {
id = 'elasticsearch.docker-support'
implementationClass = 'org.elasticsearch.gradle.internal.docker.DockerSupportPlugin'
}
docsTest {
id = 'elasticsearch.docs-test'
implementationClass = 'org.elasticsearch.gradle.internal.doc.DocsTestPlugin'
}
Add DRA snapshot build (#91018) * Add support for building against defined build-ids of dependent artifacts * Introduce DraResolvePlugin and functional tests * Declare initial dra snapshot ci job for elasticsearch We run the DRA builds against ubuntu as other release related ci jobs have in the past. Also we only have libs2xmlutills available on our ubuntu based ci workers
2022-11-09 23:16:21 +08:00
draArtifacts {
id = 'elasticsearch.dra-artifacts'
implementationClass = 'org.elasticsearch.gradle.internal.dra.DraResolvePlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
globalBuildInfo {
id = 'elasticsearch.global-build-info'
implementationClass = 'org.elasticsearch.gradle.internal.info.GlobalBuildInfoPlugin'
}
internalAvailablePorts {
id = 'elasticsearch.internal-available-ports'
implementationClass = 'org.elasticsearch.gradle.internal.InternalAvailableTcpPortProviderPlugin'
}
internalClusterTest {
id = 'elasticsearch.internal-cluster-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.InternalClusterTestPlugin'
}
internalDistributionArchiveCheck {
id = 'elasticsearch.internal-distribution-archive-check'
implementationClass = 'org.elasticsearch.gradle.internal.InternalDistributionArchiveCheckPlugin'
}
internalDistributionArchiveSetup {
id = 'elasticsearch.internal-distribution-archive-setup'
implementationClass = 'org.elasticsearch.gradle.internal.InternalDistributionArchiveSetupPlugin'
}
internalDistributionBwcSetup {
id = 'elasticsearch.internal-distribution-bwc-setup'
implementationClass = 'org.elasticsearch.gradle.internal.InternalDistributionBwcSetupPlugin'
}
internalDistributionDownload {
id = 'elasticsearch.internal-distribution-download'
implementationClass = 'org.elasticsearch.gradle.internal.InternalDistributionDownloadPlugin'
}
internalPlugin {
id = 'elasticsearch.internal-es-plugin'
implementationClass = 'org.elasticsearch.gradle.internal.InternalPluginBuildPlugin'
}
Remove usages of elasticsearch.build plugin in non-production projects (#84890)
2022-03-15 02:27:24 +08:00
internalBasePlugin {
id = 'elasticsearch.base-internal-es-plugin'
implementationClass = 'org.elasticsearch.gradle.internal.BaseInternalPluginBuildPlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
internalTestArtifact {
id = 'elasticsearch.internal-test-artifact'
implementationClass = 'org.elasticsearch.gradle.internal.InternalTestArtifactPlugin'
}
internalTestArtifactBase {
id = 'elasticsearch.internal-test-artifact-base'
implementationClass = 'org.elasticsearch.gradle.internal.InternalTestArtifactBasePlugin'
}
internalTestClusters {
id = 'elasticsearch.internal-testclusters'
implementationClass = 'org.elasticsearch.gradle.internal.InternalTestClustersPlugin'
}
internalTestRerun {
id = 'elasticsearch.internal-test-rerun'
implementationClass = 'org.elasticsearch.gradle.internal.test.rerun.TestRerunPlugin'
}
Resolve runtime java via Gradle tool chain provider (#95319) Using gradle toolchain support in gradle requires refactoring how the composite build is composed. We added three toolchain resolver 1. Resolver for resolving defined bundled version from oracle as openjdk 2. Resolve all available jdks from Adoption 3. Resolve archived Oracle jdk distributions. We should be able to remove the JdkDownloadPlugin altogether without having that in place, but we'll do that in a separate effort. Fixes #95094
2023-05-03 21:28:47 +08:00
javaToolChainPlugin {
id = 'elasticsearch.java-toolchain'
implementationClass = 'org.elasticsearch.gradle.internal.toolchain.JavaToolChainResolverPlugin'
}
Port javadoc configuration logic into a binary plugin (#86471) Also adding test coverage and fixing certain issues we stumbled into when resolving project dependencies of compileClasspath we need to use allDependencies instead of dependencies as usually no dependencies are added directly to compileClasspath but via implementation, compileonly and api and friends Fixed javadoc setup for projects using shadowed dependencies via shadow plugin Fixed dealing with skipped javadoc tasks in referenced dependent projects. In general this PR only fixes expected javadoc generation as it was intended before this PR. This also contains some tweaks to our gradle integration test fixtures for setting up and debugging test projects
2022-05-10 15:58:43 +08:00
javaDoc {
id = 'elasticsearch.java-doc'
implementationClass = 'org.elasticsearch.gradle.internal.ElasticsearchJavadocPlugin'
}
Add zstd to native access (#105715) This commit makes zstd compression available to Elasticsearch. The library is pulled in through maven in jar files for each platform, then bundled in a new platform directory under lib. Access to the zstd compression/decompression is through NativeAccess.
2024-03-14 00:45:12 +08:00
javaBase {
id = 'elasticsearch.java-base'
implementationClass = 'org.elasticsearch.gradle.internal.ElasticsearchJavaBasePlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
java {
id = 'elasticsearch.java'
implementationClass = 'org.elasticsearch.gradle.internal.ElasticsearchJavaPlugin'
}
Add JUnit rule based integration test cluster orchestration framework (#92379) 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.
2022-12-22 07:33:46 +08:00
legacyInternalJavaRestTest {
id = 'elasticsearch.legacy-java-rest-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.rest.LegacyJavaRestTestPlugin'
}
Introduce external build-tools JavaRestTestPlugin (#77603) * Add external build tools JavaRestTestPlugin * Fix integration test Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2021-09-14 02:10:22 +08:00
internalJavaRestTest {
id = 'elasticsearch.internal-java-rest-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.rest.InternalJavaRestTestPlugin'
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
}
jdkDownload {
id = 'elasticsearch.jdk-download'
implementationClass = 'org.elasticsearch.gradle.internal.JdkDownloadPlugin'
}
Add a Gradle Plugin for compiling modular source projects. (#86602) This PR upstreams a custom Gradle Plugin for compiling modular source projects, that we've been using for a while now over on the modules branch. The Plugin infers which dependencies should be on the module path and which dependencies should be on the class path, when compilng the main java sourceset. This supports the "bottom up" modularization of Elasticsearch, where parent projects are modularized before child projects. Allowing to modularize the core of the server independently of the extension components, that can themselves be modularized later. With this plugin various subprojects can be modularized (by adding a module-info.java in the source root) with minimal fuss - no custom gradle logic is required by the subproject, beyond a couple of subproject specific compiler lint suppressions. The inference in the plugin is driven by walking the project dependencies, searching for the presence of a module-info.java, afterwhich all subprojects will be put on the module path. Again, this supports "bottom up" modularization. Co-authored-by: ChrisHegarty <christopher.hegarty@elastic.co> Co-authored-by: Mark Vieira <portugee@gmail.com> Co-authored-by: Ryan Ernst <ryan@iernst.net> Co-authored-by: Rene Groeschke <rene@breskeby.com>
2022-05-13 15:03:57 +08:00
javaModulePath {
id = 'elasticsearch.java-module'
implementationClass = 'org.elasticsearch.gradle.internal.ElasticsearchJavaModulePathPlugin'
}
Add plugin for creating MRJARs (#104883) This commit adds an elasticsearch gradle plugin which sets up a project to build an MRJAR. By applying the plugin, the src dir is checked for any directories matching mainXX where XX is the java version number. A source set is automatically setup, an appropriate compiler tied to that source set, and it's output placed in the correct part of the final jar. Additionally, the sourceset allows use of preview features in that verison of Java, and the preview bits are stripped from the resulting class files.
2024-01-30 13:06:19 +08:00
mrjar {
id = 'elasticsearch.mrjar'
implementationClass = 'org.elasticsearch.gradle.internal.MrjarPlugin'
}
Add a gradle plugin for embedded providers (#105094) x-content embeds its jackson implementation inside its jar. This commit formalizes the setup for this embedding with a gradle plugin so that it can be reused by other libs.
2024-02-06 04:21:52 +08:00
embeddedProvider {
id = 'elasticsearch.embedded-providers'
implementationClass = 'org.elasticsearch.gradle.internal.EmbeddedProviderPlugin'
}
New release notes generator tasks (#71125) Part of #67335. Add tasks for generating release notes, using information stored in files in the repository: * `generateReleaseNotes` - generates new release notes, release highlights and breaking changes * `validateChangelogs` - validates that all the changelog YAML files are well-formed (confirm to schema, have required fields depending on the `type` value) I also changed `Version` to allow a `v` prefix in relaxed mode
2021-07-28 19:09:58 +08:00
releaseTools {
id = 'elasticsearch.release-tools'
implementationClass = 'org.elasticsearch.gradle.internal.release.ReleaseToolsPlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
repositories {
id = 'elasticsearch.repositories'
implementationClass = 'org.elasticsearch.gradle.internal.RepositoriesSetupPlugin'
}
restResources {
id = 'elasticsearch.rest-resources'
implementationClass = 'org.elasticsearch.gradle.internal.test.rest.RestResourcesPlugin'
}
standaloneRestTest {
id = 'elasticsearch.standalone-rest-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.StandaloneRestTestPlugin'
}
standaloneTest {
id = 'elasticsearch.standalone-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.StandaloneTestPlugin'
}
Add StringTemplate Gradle plugin (#97388) This commit adds a StringTemplate Gradle plugin based on Antlr's StringTemplate. With this plugin we can template Java source code and generate different variants of it, e.g. implementations that vary only by primitive type.
2023-07-07 22:58:45 +08:00
stringTemplate {
id = 'elasticsearch.string-templates'
implementationClass = 'org.elasticsearch.gradle.internal.StringTemplatePlugin'
repository-s3 yamlRestTests to new cluster test framework (#102353) - Replace docker-compose based s3-fixture usages to use plain java - Support lazy evaluated system properties for local cluster definitions - Make it work with configuration cache enabled - Port Minio fixture usage to leverage test container testing library.
2023-11-22 17:08:58 +08:00
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
testFixtures {
id = 'elasticsearch.test.fixtures'
implementationClass = 'org.elasticsearch.gradle.internal.testfixtures.TestFixturesPlugin'
}
Add gradle plugin for publishing docker based test fixtures (#106229) To make those docker images available for our testcontainer based fixtures we need to publish them on a regular basis to ensure the source and the images are in sync. This adds some convenience plugin to take care of publishing our docker test fixtures
2024-03-22 00:29:38 +08:00
deployTestFixtures {
id = 'elasticsearch.deploy-test-fixtures'
implementationClass = 'org.elasticsearch.gradle.internal.testfixtures.TestFixturesDeployPlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
testBase {
id = 'elasticsearch.test-base'
implementationClass = 'org.elasticsearch.gradle.internal.ElasticsearchTestBasePlugin'
}
testWithDependencies {
id = 'elasticsearch.test-with-dependencies'
implementationClass = 'org.elasticsearch.gradle.internal.test.TestWithDependenciesPlugin'
}
testWithSsl {
id = 'elasticsearch.test-with-ssl'
implementationClass = 'org.elasticsearch.gradle.internal.test.TestWithSslPlugin'
}
validateRestSpec {
id = 'elasticsearch.validate-rest-spec'
implementationClass = 'org.elasticsearch.gradle.internal.precommit.ValidateRestSpecPlugin'
}
Add JUnit rule based integration test cluster orchestration framework (#92379) 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.
2022-12-22 07:33:46 +08:00
legacyYamlRestCompatTest {
id = 'elasticsearch.legacy-yaml-rest-compat-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.rest.compat.compat.LegacyYamlRestCompatTestPlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
yamlRestCompatTest {
id = 'elasticsearch.yaml-rest-compat-test'
Add JUnit rule based integration test cluster orchestration framework (#92379) 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.
2022-12-22 07:33:46 +08:00
implementationClass = 'org.elasticsearch.gradle.internal.test.rest.compat.compat.YamlRestCompatTestPlugin'
}
legacyYamlRestTest {
id = 'elasticsearch.legacy-yaml-rest-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.rest.LegacyYamlRestTestPlugin'
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
}
Rework minio test fixture and its usages (#102707) * Update minio fixture and usages to rely on new test cluster framework and testcontainer * Cache test fixture resources during packer caching Add logic that ensures we resolve docker images resolved from docker registry as part of our packer cache setup.
2023-12-05 16:30:50 +08:00
cacheTestFixtures {
id = 'elasticsearch.cache-test-fixtures'
implementationClass = 'org.elasticsearch.gradle.internal.packer.CacheTestFixtureResourcesPlugin'
}
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
yamlRestTest {
Introduce simple public yaml-rest-test plugin (#76554) This introduces a basic public yaml rest test plugin that is supposed to be used by external elasticsearch plugin authors. This is driven by #76215 - Rename yaml-rest-test to intern-yaml-rest-test - Use public yaml plugin in example plugins Co-authored-by: Mark Vieira <portugee@gmail.com>
2021-08-31 14:45:52 +08:00
id = 'elasticsearch.internal-yaml-rest-test'
implementationClass = 'org.elasticsearch.gradle.internal.test.rest.InternalYamlRestTestPlugin'
Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
}
}
Avoid creating gradle plugin publication (#69086) The java gradle plugin plugin allows to disable the automatic creation of a publication. This allows avoiding the publication at all instead of disabling the according tasks. We ship our own publication and dont need the automatically created one. Furthermore this avoids deprecated behaviour in Gradle 7.0 and above in having multiple publications with the same target artifacts
2021-02-17 17:04:13 +08:00
}
Build: Add fake project to include buildSrc as normal project This is a follow up to #18173 and includes adding pom generation to the fake build-tools project, which is really just buildSrc, but builds during normal builds.
2016-05-07 13:22:38 +08:00
Switch build-tools to latest target version (#34746) - we already require Java 11 to build, yet we target the minimum supported version in build-tools ( currently 8 ) - this is because we have some checks that are executed in a new JVM which could be running the minimum version. - For everything else it would be nice to be able to use new features, like the new process API. With this change, we selectively compile the few classes that need an older target version and move everything over to Java 10. Unfortunately the current Gradle version does not support 11 as a target version yet.
2018-10-25 15:03:23 +08:00
/*****************************************************************************
* Java version *
*****************************************************************************/
Separate minimum compiler and runtime Java version properties (#79108)
2021-10-15 02:09:25 +08:00
def minCompilerJava = versions.get("minimumCompilerJava")
Update Gradle Wrapper to 8.2 (#96686) - Convention usage has been deprecated and was fixed in our build files - Fix test dependencies and deprecation
2023-07-04 21:35:15 +08:00
java {
targetCompatibility = minCompilerJava
sourceCompatibility = minCompilerJava
}
Compile subset of build-tools classes with Java 8 target compatibility (#43177)
2019-06-14 01:24:28 +08:00
Improve error message when minimum compiler version is not met (#74512)
2021-06-24 23:46:09 +08:00
if (JavaVersion.current() < JavaVersion.toVersion(minCompilerJava)) {
throw new GradleException("Java ${minCompilerJava} is required to build Elasticsearch but current Java is version ${JavaVersion.current()}.")
}
Compile subset of build-tools classes with Java 8 target compatibility (#43177)
2019-06-14 01:24:28 +08:00
sourceSets {
Fix deprecation warning in ThirdpartyAuditTask (#57123)
2020-05-27 23:10:07 +08:00
integTest {
compileClasspath += sourceSets["main"].output + configurations["testRuntimeClasspath"]
runtimeClasspath += output + compileClasspath
}
Compile subset of build-tools classes with Java 8 target compatibility (#43177)
2019-06-14 01:24:28 +08:00
}
Remove minimumRuntime sourceSet from build-tools (#58417) * Remove minimumRuntime sourceSet from build-tools * remove license change in loggedexec task
2020-06-24 15:40:18 +08:00
tasks.withType(JavaCompile).configureEach {
options.encoding = 'UTF-8'
Disable incremental compilation in CI environments (#103346)
2023-12-13 05:10:27 +08:00
options.incremental = System.getenv("JENKINS_URL") == null && System.getenv("BUILDKITE_BUILD_URL") == null && System.getProperty("isCI") == null
Compile subset of build-tools classes with Java 8 target compatibility (#43177)
2019-06-14 01:24:28 +08:00
}
Switch build-tools to latest target version (#34746) - we already require Java 11 to build, yet we target the minimum supported version in build-tools ( currently 8 ) - this is because we have some checks that are executed in a new JVM which could be running the minimum version. - For everything else it would be nice to be able to use new features, like the new process API. With this change, we selectively compile the few classes that need an older target version and move everything over to Java 10. Unfortunately the current Gradle version does not support 11 as a target version yet.
2018-10-25 15:03:23 +08:00
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
tasks.named('licenseHeaders').configure {
// ignore gradle generated binary script plugins
excludes << "Elasticsearch*Plugin.java"
}
Build: Add fake project to include buildSrc as normal project This is a follow up to #18173 and includes adding pom generation to the fake build-tools project, which is really just buildSrc, but builds during normal builds.
2016-05-07 13:22:38 +08:00
/*****************************************************************************
* Dependencies used by the entire build *
*****************************************************************************/
Build: Consolidate dependencies specified in multiple places Some dependencies must be specified in a couple places in the build. e.g. randomized runner is specified both in buildSrc (for the gradle wrapper plugin), as well as in the test-framework. This change creates buildSrc/versions.properties which acts similar to the set of shared version properties we used to have in the maven parent pom.
2015-11-10 15:34:22 +08:00
Switch build system to Gradle See #13930
2015-10-30 02:40:19 +08:00
repositories {
Update Gradle wrapper to 8.8 (#108021) Fix incompatibility with 8.8 and our internal api usages - Update ospackage to a version that contains a fix we provided - Tweak build logic to avoid deprecation warnings - Use newer permission api - Use custom shadowplugin - Rework ElasticsearchDistribution dependencies resolution - Update Gradle wrapper to 8.8
2024-06-04 18:43:02 +08:00
maven {
url 'https://jitpack.io'
}
Remove jcenter repository from our build (#69517) - JCenter has been deprecated in Gradle - JCenter was announced to be sunset by JFrog - Use Gradle plugin portal as maven repository for build dependencies - Use mavenCentral as general replacement for jcenter Fixes #68476
2021-02-25 15:36:08 +08:00
mavenCentral()
gradlePluginPortal()
Switch build system to Gradle See #13930
2015-10-30 02:40:19 +08:00
}
Rework RerunTestResultProcessor to handle aborted tests better (#72710) This should address the latest occurrences of null pointer exceptions when test start events a propagated to test process as listed in #72169 Also introducing the option to have unit tests in build tools written in spock.
2021-05-05 16:13:45 +08:00
configurations {
integTestRuntimeOnly.extendsFrom(testRuntimeOnly)
}
Rework testing conventions gradle plugin (#87213) This PR reworks the testing conventions precommit plugin. This plugin now: - is compatible with yaml, java rest tests and internalClusterTest (aka different sourceSets per test type) - enforces test base class and simple naming conventions (as it did before) - adds one check task per test sourceSet - uses the worker api to improve task execution parallelism and encapsulation - is gradle configuration cache compatible This also ports the TestingConventions integration testing to Spock and removes the build-tools-internal/test kit folder that is not required anymore. We also add some common logic for testing java related gradle plugins. We will apply further cleanup on other tests within our test suite in a dedicated follow up cleanup
2022-06-20 22:26:38 +08:00
Switch build system to Gradle See #13930
2015-10-30 02:40:19 +08:00
dependencies {
Cleanup jackson build tool dependencies (#83164) - use jackson platform - use compatible schema validator version
2022-01-27 16:57:47 +08:00
components.all(JacksonAlignmentRule)
Update asm version in build tools for java19 support (#86288) This also fixes issues with using asm in functional tests where spock dependencies brought in an older version of asm not compatible with java 18
2022-05-02 16:47:11 +08:00
constraints {
// ensuring brought asm version brought in by spock is up-to-date
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
testImplementation buildLibs.asm
integTestImplementation buildLibs.asm
[Gradle] Cleanup build libs vesion catalogue and its usage (#110298) * [Gradle] Cleanup build libs vesion catalogue and its usage * Snake yaml version in version.properties still used
2024-07-01 19:57:05 +08:00
api(buildLibs.snakeyaml)
Update asm version in build tools for java19 support (#86288) This also fixes issues with using asm in functional tests where spock dependencies brought in an older version of asm not compatible with java 18
2022-05-02 16:47:11 +08:00
}
Cleanup jackson build tool dependencies (#83164) - use jackson platform - use compatible schema validator version
2022-01-27 16:57:47 +08:00
// Forcefully downgrade the jackson platform as used in production
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
api enforcedPlatform(buildLibs.jackson.platform)
Replace compile configuration usage with api (#58451) - Use java-library instead of plugin to allow api configuration usage - Remove explicit references to runtime configurations in dependency declarations - Make test runtime classpath input for testing convention - required as java library will by default not have build jar file - jar file is now explicit input of the task and gradle will ensure its properly build
2020-06-30 15:37:09 +08:00
api localGroovy()
api gradleApi()
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
api "org.elasticsearch:build-conventions:$version"
Clean up build tools dependencies and fix maven coordinates (#74520)
2021-06-24 23:55:21 +08:00
api "org.elasticsearch.gradle:build-tools:$version"
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
Update build tools internal dependencies (#82875) - use latest versions of gradle plugins - do not rely on idea annotations - remove nebula.optional-deps plugin where not used - Fix some version conflicts
2022-01-24 20:16:38 +08:00
// same version as http client transitive dep
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
api buildLibs.commons.codec
api buildLibs.apache.compress
api buildLibs.nebula.info
api buildLibs.apache.rat
api buildLibs.jna
api buildLibs.shadow.plugin
Fix creation of large build job archives (#102023) * Fix large file and large path handling in build tar creating
2023-11-22 03:29:27 +08:00
api buildLibs.gradle.enterprise
Port gradle script plugins to precompiled script plugins (#72361) Script plugins cannot apply plugins and therefore wont work with porting buildSrc to an included build as we plan. Therefore we take advantage of moving our script plugins into precompiled script plugins. As a limitation of this we ran into problems applying binary plugins from script plugins and for now moved this out of those scripts.
2021-04-29 15:33:28 +08:00
// for our ide tweaking
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
api buildLibs.idea.ext
Bump minimum compile jdk version to 15 (#67126) (cherry picked from commit c7623e63c880820cf1804e5cc1c5070d623faa5c)
2021-01-12 00:23:56 +08:00
// When upgrading forbidden apis, ensure dependency version is bumped in ThirdPartyPrecommitPlugin as well
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
api buildLibs.forbiddenApis
api buildLibs.docker.compose
api buildLibs.maven.model
Cleanup jackson build tool dependencies (#83164) - use jackson platform - use compatible schema validator version
2022-01-27 16:57:47 +08:00
// needs to match the jackson minor version in use
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
api buildLibs.json.schema.validator
api buildLibs.jackson.dataformat.yaml
Add StringTemplate Gradle plugin (#97388) This commit adds a StringTemplate Gradle plugin based on Antlr's StringTemplate. With this plugin we can template Java source code and generate different variants of it, e.g. implementations that vary only by primitive type.
2023-07-07 22:58:45 +08:00
api buildLibs.antlrst4
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
api buildLibs.asm
api buildLibs.asm.tree
api buildLibs.httpclient
api buildLibs.httpcore
Fix creation of large build job archives (#102023) * Fix large file and large path handling in build tar creating
2023-11-22 03:29:27 +08:00
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
compileOnly buildLibs.checkstyle
Rework minio test fixture and its usages (#102707) * Update minio fixture and usages to rely on new test cluster framework and testcontainer * Cache test fixture resources during packer caching Add logic that ensures we resolve docker images resolved from docker registry as part of our packer cache setup.
2023-12-05 16:30:50 +08:00
compileOnly buildLibs.reflections
[Gradle] Cleanup build libs vesion catalogue and its usage (#110298) * [Gradle] Cleanup build libs vesion catalogue and its usage * Snake yaml version in version.properties still used
2024-07-01 19:57:05 +08:00
implementation buildLibs.javaparser
Add new update version gradle task (#103335) Add an updateVersions gradle task that updates the version numbers in the ES repo as part of release automation. This will be used by the release automation tools, replacing old functionality to manually modify the java files.
2023-12-21 01:09:29 +08:00
Clean up build tools dependencies and fix maven coordinates (#74520)
2021-06-24 23:55:21 +08:00
runtimeOnly "org.elasticsearch.gradle:reaper:$version"
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
testImplementation buildLibs.checkstyle
testImplementation buildLibs.wiremock
testImplementation buildLibs.mockito.core
testImplementation buildLibs.hamcrest
Clean up build tools dependencies and fix maven coordinates (#74520)
2021-06-24 23:55:21 +08:00
testImplementation testFixtures("org.elasticsearch.gradle:build-tools:$version")
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
testImplementation(platform(buildLibs.junit5.platform))
testImplementation(buildLibs.junit5.jupiter) {
Run test task in BuildToolsInternal with junit5 (#79148) - fixes missing execution of spock tests
2021-10-14 23:18:10 +08:00
because 'allows to write and run Jupiter tests'
}
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
integTestImplementation(platform(buildLibs.junit5.platform))
integTestImplementation(buildLibs.junit5.jupiter) {
Fix ignored spock build tools integ tests (#71769) Gradle 7.0 forced us to update to spock2 because we need a groovy 3 compatible spock framework version. Spock2 requires junit5 to be executed. We use the junit5 platform but provide the vintage runner to be able to execute junit4 implemented IT tests too
2021-04-17 01:16:42 +08:00
because 'allows to write and run Jupiter tests'
}
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
integTestImplementation(buildLibs.bytebuddy) {
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
because 'Generating dynamic mocks of internal libraries like JdkJarHell'
}
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
testRuntimeOnly(buildLibs.junit5.vintage) {
Fix ignored spock build tools integ tests (#71769) Gradle 7.0 forced us to update to spock2 because we need a groovy 3 compatible spock framework version. Spock2 requires junit5 to be executed. We use the junit5 platform but provide the vintage runner to be able to execute junit4 implemented IT tests too
2021-04-17 01:16:42 +08:00
because 'allows JUnit 3 and JUnit 4 tests to run'
}
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
testRuntimeOnly(buildLibs.junit5.platform.launcher) {
Fix ignored spock build tools integ tests (#71769) Gradle 7.0 forced us to update to spock2 because we need a groovy 3 compatible spock framework version. Spock2 requires junit5 to be executed. We use the junit5 platform but provide the vintage runner to be able to execute junit4 implemented IT tests too
2021-04-17 01:16:42 +08:00
because 'allows tests to run from IDEs that bundle older version of launcher'
}
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
testImplementation platform(buildLibs.spock.platform)
testImplementation(buildLibs.spock.core) {
Rework RerunTestResultProcessor to handle aborted tests better (#72710) This should address the latest occurrences of null pointer exceptions when test start events a propagated to test process as listed in #72169 Also introducing the option to have unit tests in build tools written in spock.
2021-05-05 16:13:45 +08:00
exclude module: "groovy"
}
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
integTestImplementation platform(buildLibs.spock.platform)
integTestImplementation(buildLibs.spock.core) {
Remove minimumRuntime sourceSet from build-tools (#58417) * Remove minimumRuntime sourceSet from build-tools * remove license change in loggedexec task
2020-06-24 15:40:18 +08:00
exclude module: "groovy"
Introduce EnforceDeprecationFailuresPlugin (#58263) - extract fail on deprecated usage into its own plugin - apply on all projects - ensures we don't miss any project (missed xpack/plugin/eql/qa/security before)
2020-06-18 16:53:11 +08:00
}
Rework RerunTestResultProcessor to handle aborted tests better (#72710) This should address the latest occurrences of null pointer exceptions when test start events a propagated to test process as listed in #72169 Also introducing the option to have unit tests in build tools written in spock.
2021-05-05 16:13:45 +08:00
// required as we rely on junit4 rules
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
integTestImplementation(buildLibs.spock.junit4) {
Bump source compatibility version to Java 17 (#80851)
2021-12-07 02:58:56 +08:00
exclude module: "groovy"
}
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
testImplementation buildLibs.spock.junit4
Setup elasticsearch dependency monitoring with Snyk for production code (#88036) This adds the generation and upload logic of Gradle dependency graphs to snyk We directly implemented a rest api based snyk plugin as: the existing snyk gradle plugin delegates to the snyk command line tool the command line tool uses custom gradle logic by injecting a init file that is a) using deprecated build logic which we definitely want to avoid b) uses gradle api we avoid like eager task creation. Shipping this as a internal gradle plugin gives us the most flexibility as we only want to monitor production code for now we apply this plugin as part of the elasticsearch.build plugin, that usage has been for now the de-facto indicator if a project is considered a "production" project that ends up in our distribution or public maven repositories. This isnt yet ideal and we will revisit the distinction between production and non production code / projects in a separate effort. As part of this effort we added the elasticsearch.build plugin to more projects that actually end up in the distribution. To unblock us on this we for now disabled a few check tasks that started failing by applying elasticsearch.build. Addresses #87620
2022-06-29 19:29:14 +08:00
testImplementation buildLibs.json.assert
Port build dependencies to gradle version catalogue (#86548) We introduce the use of a Gradle version catalogue for handling build related dependencies. This provides type safe accessors for dependencies and allow centralised version definitions. Later we want to move all our dependency handling to version catalogues. Since this is a Gradle feature we remove long term maintenance cost for custom version handling in our build and make centralised version handling more straight forward and support better tooling based on version catalogues Fixes asm version alignment on the way using 9.3 everywhere in our build logic.
2022-05-10 18:15:36 +08:00
integTestImplementation buildLibs.xmlunit.core
update snakeyaml dependency (#90414) This commit updates snakeyaml to 1.33 and consolidates which version is used.
2022-09-29 02:13:03 +08:00
Make build Gradle 2.14 / 3.x compatible (#22669) This changes build files so that building Elasticsearch works with both Gradle 2.13 as well as higher versions of Gradle (tested 2.14 and 3.3), enabling a smooth transition from Gradle 2.13 to 3.x.
2017-01-19 16:56:54 +08:00
}
Build: Add fake project to include buildSrc as normal project This is a follow up to #18173 and includes adding pom generation to the fake build-tools project, which is really just buildSrc, but builds during normal builds.
2016-05-07 13:22:38 +08:00
Run test task in BuildToolsInternal with junit5 (#79148) - fixes missing execution of spock tests
2021-10-14 23:18:10 +08:00
tasks.named('test').configure {
useJUnitPlatform()
}
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
tasks.register("integTest", Test) {
systemProperty 'test.version_under_test', version
testClassesDirs = sourceSets.integTest.output.classesDirs
classpath = sourceSets.integTest.runtimeClasspath
useJUnitPlatform()
Add back eclipse configuration to buildSrc
2015-11-10 23:30:11 +08:00
}
Build: Add .settings for buildSrc on gradle eclipse We have eclipse settings added to all projects when running gradle eclipse, but buildSrc is its own special project that is not encapsulated by allprojects blocks. This adds eclipse settings to buildSrc.
2015-12-04 11:53:50 +08:00
Use compiler version for gradle code (#73777) The minimum compiler version is that which we require a developer to use when building Elasticsearch. This version is updated as newer versions of Java are released. In contrast, the minimum runtime version is that which Elasticsearch itself needs. In 7.x this is Java 8, and in master this is Java 11. Historically the version we require for gradle code has had to be the minimum runtime version since all the gradle code was distributed for plugin developers. Now that the external build tools is separated from our internal tools, the internal tools are no longer bound by that runtime requirement. Instead, they can use the latest Java, so that we can use new features within our internal tools. This commit switches the source compatibiltiy version for the internal build tools to use the minimum compiler version.
2021-06-05 05:33:46 +08:00
tasks.named("check").configure { dependsOn("integTest") }
Setup build benchmark jobs (#80941) Setting up automatic benchmark builds. This PR allows testing impact on build changes on the build performance by comparing the PR source against master and run different scenarios to verify build performance by using the gradle profiler (see https://github.com/gradle/gradle-profiler) they can be triggered by adding the `build-benchmark` GitHub label
2021-12-15 16:27:16 +08:00
tasks.register("bootstrapPerformanceTests", Copy) {
from('performance')
into('build/performanceTests')
def root = file('..')
Update to to Gradle wrapper 7.5 (#85141) This updates the gradle wrapper to a 7.5 Fixes #85123
2022-07-19 14:12:19 +08:00
inputs.property('branchWrapper', gradle.gradleVersion)
Set explicitly Gradle version in benchmark scenarios (#85229) Gradle versions in scenarios are not automatically resolved from the gradle wrapper version
2022-03-23 16:29:16 +08:00
filter(ReplaceTokens, tokens: [
testGitCommit:GitInfo.gitInfo(root).revision,
Update references to master branch in build benchmark configuration (#88787)
2022-07-27 00:51:42 +08:00
mainWrapper:"${ -> resolveMainWrapperVersion()}".toString(),
Update to to Gradle wrapper 7.5 (#85141) This updates the gradle wrapper to a 7.5 Fixes #85123
2022-07-19 14:12:19 +08:00
branchWrapper:"${-> gradle.gradleVersion}".toString()])
Set explicitly Gradle version in benchmark scenarios (#85229) Gradle versions in scenarios are not automatically resolved from the gradle wrapper version
2022-03-23 16:29:16 +08:00
}
Improve efficiency of nested Gradle builds (#92801)
2023-01-12 04:51:48 +08:00
tasks.named("jar") {
exclude("classpath.index")
}
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 90888b1 (#114284) This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `c16d3ad` -> `90888b1` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
2024-10-08 22:39:19 +08:00
spotless {
java {
// IDEs can sometimes run annotation processors that leave files in
// here, causing Spotless to complain. Even though this path ought not
// to exist, exclude it anyway in order to avoid spurious failures.
toggleOffOn()
}
}
Update references to master branch in build benchmark configuration (#88787)
2022-07-27 00:51:42 +08:00
def resolveMainWrapperVersion() {
new URL("https://raw.githubusercontent.com/elastic/elasticsearch/main/build-tools-internal/src/main/resources/minimumGradleVersion").text.trim()
Remove nebula extra configuration plugin (#82934) This was used to mark dependencies as optional. Within Gradle those deps are handled as usual and optional is only added to the according pom file. When packaging our distro those modules are added anyhow including the optional dependencies The initial motiviation to remove the plugin was it is incompatible with the gradle configuration cache
2022-01-24 22:28:51 +08:00
}
Cleanup jackson build tool dependencies (#83164) - use jackson platform - use compatible schema validator version
2022-01-27 16:57:47 +08:00
abstract class JacksonAlignmentRule implements ComponentMetadataRule {
void execute(ComponentMetadataContext ctx) {
ctx.details.with {d ->
if (d.id.group.startsWith("com.fasterxml.jackson")) {
// declare that Jackson modules all belong to the Jackson virtual platform
belongsTo("com.fasterxml.jackson:jackson-bom:${d.id.version}")
}
}
}
Remove usages of elasticsearch.build plugin in non-production projects (#84890)
2022-03-15 02:27:24 +08:00
}