OpenSearch/.ci
Mark Vieira d3cf89b563
Upgrade to Gradle 6.0 (#49211) (#49994)
This upgrade required a few significant changes. Firstly, the build
scan plugin has been renamed, and changed to be a Settings plugin rather
than a project plugin so the declaration of this has moved to our
settings.gradle file. Second, we were using a rather old version of the
Nebula ospackage plugin for building deb and rpm packages, the migration
to the latest version required some updates to get things working as
expected as we had some workarounds in place that are no longer
applicable with the latest bug fixes.

(cherry picked from commit 87f9c16e2f8870e3091062cde37b43042c3ae1c5)
2019-12-09 11:34:35 -08:00
..
jobs.t Move env vars to script, add build scan wrapper (#49070) 2019-11-15 16:25:55 +02:00
README.md Move periodic job to ES repo (#48570) 2019-11-13 17:12:42 +02:00
build.sh Move env vars to script, add build scan wrapper (#49070) 2019-11-15 16:25:55 +02:00
bwcVersions Update CI BWC versions 2019-12-03 16:18:49 -08:00
dockerOnLinuxExclusions Add Docker packaging tests on 7.x (#48857) 2019-11-05 15:17:59 +00:00
init.gradle Apply 2-space indent to all gradle scripts (#49071) 2019-11-14 11:01:23 +00:00
java-versions.properties Upgrade to Gradle 6.0 (#49211) (#49994) 2019-12-09 11:34:35 -08:00
make-branch-config.sh Move periodic job to ES repo (#48570) 2019-11-13 17:12:42 +02:00
matrix-build-javas.yml Disable building on JDK 13 in CI 2019-06-05 09:55:37 -04:00
matrix-java-exclusions.yml Java versions for ci (#29320) 2018-04-02 14:24:25 -04:00
matrix-runtime-javas.yml Start testing against AdoptOpenJDK (#45666) 2019-08-29 08:56:21 -04:00
os.ps1 Read build and runtime java from properties file (#48355) 2019-10-23 13:23:40 +03:00
os.sh Add Docker packaging tests on 7.x (#48857) 2019-11-05 15:17:59 +00:00
packer_cache.sh Make packer cache branches explicit (#41990) 2019-05-27 09:46:43 +03:00

README.md

CI configuration for Elasticsearch

Layout and Syntax

CI is run by Jenkins at elasticsearch-ci. Jobs live in the jobs.t directory, these are defined in YML using a syntax simmilar to JJB. Macros are not allowed, and each job must be defined in its own file. Merging of the default configuration is customized so unlike in standard JJB, it recurses into YML objects. Further (internal) documentation on the setup is available .