ee202a642f
This change changes the way to run our test suites in JVMs configured in FIPS 140 approved mode. It does so by: - Configuring any given runtime Java in FIPS mode with the bundled policy and security properties files, setting the system properties java.security.properties and java.security.policy with the == operator that overrides the default JVM properties and policy. - When runtime java is 11 and higher, using BouncyCastle FIPS Cryptographic provider and BCJSSE in FIPS mode. These are used as testRuntime dependencies for unit tests and internal clusters, and copied (relevant jars) explicitly to the lib directory for testclusters used in REST tests - When runtime java is 8, using BouncyCastle FIPS Cryptographic provider and SunJSSE in FIPS mode. Running the tests in FIPS 140 approved mode doesn't require an additional configuration either in CI workers or locally and is controlled by specifying -Dtests.fips.enabled=true |
||
|---|---|---|
| .. | ||
| jobs.t | ||
| README.md | ||
| build.sh | ||
| bwcVersions | ||
| dockerOnLinuxExclusions | ||
| init.gradle | ||
| java-versions.properties | ||
| make-branch-config.sh | ||
| matrix-build-javas.yml | ||
| matrix-java-exclusions.yml | ||
| matrix-runtime-javas.yml | ||
| os.ps1 | ||
| os.sh | ||
| packer_cache.sh | ||
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 .