CI configuration for Elasticsearch
==================================

Layout and Syntax
-----------------

CI is run by Jenkins at [elasticsearch-ci](https://elasticsearch-ci.elastic.co/).
Jobs live in the [jobs.t](jobs.t) directory, these are defined in YML using a syntax 
simmilar to [JJB](https://elasticsearch-ci.elastic.co/view/Elasticsearch%20master/).
Macros are not allowed, and each job must be defined in its own file.

# This file is used with all of the non-matrix tests in Jenkins.

# This .properties file defines the versions of Java with which to
# build and test Elasticsearch for this branch. Valid Java versions
# are 'java' or 'openjdk' followed by the major release number.

ES_BUILD_JAVA=openjdk16

# This file is used as part of a matrix build in Jenkins where the
# values below are included as an axis of the matrix.

# This axis of the build matrix represents the versions of Java on
# which Elasticsearch will be tested.  Valid Java versions are 'java'
# or 'openjdk' followed by the major release number.

ES_RUNTIME_JAVA:
  - java11
  - openjdk16
  - zulu11
  - corretto11
  - adoptopenjdk11

# This file is used as part of a matrix build in Jenkins where the
# values below are included as an axis of the matrix.

# java11 should always be included as we only support Oracle Java 11 in
# FIPS 140-2 mode. 
# We also want to test with the bundled JDK so that we proactively find
# issues that might later be backported to JDK11. Current bundled JDK is
# openjdk16

ES_RUNTIME_JAVA:
  - java11

    display-name: "elastic / elasticsearch - pull request part-2 windows"
    description: "Testing of Elasticsearch pull requests - part-2 windows"
    node: "windows-immutable"
    workspace: "C:\\Users\\jenkins\\workspace\\pr-part-2\\${BUILD_NUMBER}"
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:
            - "${ghprbActualCommit}"
    triggers:

    description: "Testing of Elasticsearch pull requests - packaging-tests-windows"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"
    project-type: matrix
    node: master
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:

/**
 * CI support: this class contains gathered information and more from CI that Maven process runs on.
 *
 * @since 4.0.0
 */
public interface CIInfo {
    /**
     * Short distinct name of CI system: "GH", "Jenkins", etc.
     */
    @Nonnull
    String name();

    /**
     * May return a message that will be logged by Maven explaining why it was detected (and possibly more).
     */
    @Nonnull

    description: "Testing of Elasticsearch pull requests - packaging-tests-windows-sample"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"
    project-type: matrix
    node: master
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:

    description: "Testing of Elasticsearch pull requests - packaging-tests-windows-sample-nojdk"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"
    project-type: matrix
    node: master
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:

    Defaults   env_keep += "SYSTEM_JAVA_HOME"
SUDOERS_VARS
sudo chmod 0440 /etc/sudoers.d/elasticsearch_vars

# Bats tests still use this locationa
sudo rm -Rf /elasticsearch
sudo mkdir -p /elasticsearch/qa/ && sudo chown jenkins /elasticsearch/qa/ && ln -s $PWD/qa/vagrant /elasticsearch/qa/

# sudo sets it's own PATH thus we use env to override that and call sudo annother time so we keep the secure root PATH