# via a symlink.
# Helpful since the internal CI utilizes a T:\ drive, part of which is mounted
# to the container, and would result in C:\<path> != T:\<path> mismatches,
# when using variables like `TFCI_OUTPUT_DIR` in `docker exec commands,
# requiring conditional path adjustments throughout the CI scripts.
# Note: This does not work for `docker cp` commands.
# For a little more detail, see:

echo "Remove $gradleInit"
Remove-Item -Recurse -Force $gradleInit -ErrorAction Ignore
New-Item -ItemType directory -Path $gradleInit
echo "Copy .ci/init.gradle to $gradleInit"
Copy-Item .ci/init.gradle -Destination $gradleInit

[Environment]::SetEnvironmentVariable("JAVA_HOME", $null, "Machine")
$env:PATH="C:\Users\jenkins\.java\$env:ES_BUILD_JAVA\bin\;$env:PATH"
$env:JAVA_HOME=$null

          values:
            - 'checkPart1'
            - 'checkPart2'
            - 'bwcTestSnapshots'
            - 'checkRestCompat'
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'
          properties-content: |
            JAVA_HOME=$USERPROFILE\\.java\\$ES_BUILD_JAVA
            RUNTIME_JAVA_HOME=$USERPROFILE\\.java\\$ES_RUNTIME_JAVA

import java.util.Optional;

import org.apache.maven.api.cli.cisupport.CIInfo;

/**
 * Service interface to detect CI system process runs on, if any.
 *
 * @since 4.0.0
 */
public interface CIDetector {
    /**
     * Returns non-empty optional with CI information, if CI is detected, empty otherwise.
     */
    Optional<CIInfo> detectCI();

        shell: bash
        run: |
          mkdir -p ${{ env.MIMIR_BASEDIR }}
          cp .github/ci-mimir-session.properties ${{ env.MIMIR_BASEDIR }}/session.properties
          cp .github/ci-mimir-daemon.properties ${{ env.MIMIR_BASEDIR }}/daemon.properties
          cp .github/ci-extensions.xml .mvn/extensions.xml

      - name: Restore Mimir caches

[license]: https://www.apache.org/licenses/LICENSE-2.0
[build]: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/
[build-4.0]: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-4.0.x/
[build-3.10]: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.10.x/
[build-3.9]: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/

        --lockfile=requirements.txt:./requirements_lock_3_12.txt
        --lockfile=requirements.txt:./ci/official/containers/linux_arm64/devel.requirements.txt
        --lockfile=requirements.txt:./ci/official/containers/linux_arm64/jax.requirements.txt

`requirements_lock_3_12.txt` for `Python 3.12`).

To update the lock files, make sure
`ci/official/requirements_updater/requirements.in` contains the desired direct
dependencies list and then execute the following command (which will call
[pip-compile](https://pypi.org/project/pip-tools/) under the hood):

```
bazel run //ci/official/requirements_updater:requirements.update --repo_env=HERMETIC_PYTHON_VERSION=3.12
```

#          allow-empty-results: true
      # Upload additional logs
      - google-cloud-storage:
          credentials-id: 'elasticsearch-ci-gcs-plugin'
          uploads:
            - classic:
                file-pattern: 'build/*.tar.bz2'
                storage-location: 'gs://elasticsearch-ci-artifacts/jobs/$JOB_NAME'
                share-publicly: false
                upload-for-failed-jobs: true
                show-inline: true

    triggers:
      - timed: "H 7 * * *"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'
          properties-content: |
            JAVA_HOME=$HOME/.java/$ES_BUILD_JAVA
      - shell: |
          #!/usr/local/bin/runbld --redirect-stderr