Downgrade gradle to coninute testing on windows server 2016

[donoghuc]

Release notes

[rn:skip]

What does this PR do?

When gradle was upgraded in #17947 the windows 2016 acceptance tests started to fail due to gradle dropping support for that platform. #18209 (comment)

We want to keep the forward compatability changes in #17947 and downgrade to the last version of gradle that supports windows 2016 (probably 8.11.1 according to gradle/gradle#31939 (comment)).

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• If no backport is necessary, please add the backport-skip label

[donoghuc]

Exhaustive test run forcing win 2016: https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/2640

[donoghuc]

This passes, https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/2640#0199a73d-a744-44da-943c-1031fe4fce85

The failures are expected for observabilitySRE as ES not available yet for 9.3. This should be G2G

[jsvd]

when changing the version of the gradle wrapper one typically has to run it twice:
First call bumps the version in gradle/wrapper/gradle-wrapper.properties like in this PR.
The second call now knows to fetch 8.11.1 and will fetch it and unpack it, resulting in a few more modified files:

❯ git diff --name-status
M       gradle/wrapper/gradle-wrapper.jar
M       gradlew
M       gradlew.bat

[donoghuc]

Interesting. I'm not seeing those files modified with two invocations of gradle clean.

➜  logstash git:(downgrade-gradle) ✗ ./gradlew clean
Downloading https://services.gradle.org/distributions/gradle-8.11.1-bin.zip
.............10%.............20%.............30%.............40%.............50%.............60%.............70%.............80%.............90%.............100%

Welcome to Gradle 8.11.1!

Here are the highlights of this release:
 - Parallel load and store for Configuration Cache
 - Java compilation errors at the end of the build output
 - Consolidated report for warnings and deprecations

For more details see https://docs.gradle.org/8.11.1/release-notes.html

To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.11.1/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build

BUILD SUCCESSFUL in 20s
10 actionable tasks: 10 executed
➜  logstash git:(downgrade-gradle) ✗ git diff
➜  logstash git:(downgrade-gradle) ✗ ./gradlew clean
To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.11.1/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build

BUILD SUCCESSFUL in 3s
10 actionable tasks: 10 up-to-date
➜  logstash git:(downgrade-gradle) ✗ git diff --name-status

UPDATE: solved, i need to actually run gradlew wrapper (not gradle clean or other tasks).

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 3bf5c5a

Failed CI Steps

• Observability SRE container smoke test
• Observability SRE container smoke test
• Observability SRE container smoke test
• Observability SRE container smoke test
• 🥼 Integration Tests - FIPS mode / part 1-of-6

History

• 💔 Build #3648 failed 95f03a2
• 💔 Build #3647 failed 079898b

[jsvd]

Can you try 2 graded wrapper invocations in a row?

…

On Fri, 3 Oct 2025 at 19:19, Elastic Machine ***@***.***> wrote: *elasticmachine* left a comment (elastic/logstash#18263) <#18263 (comment)> 💔 Build Failed - Buildkite Build <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3649> - Commit: 3bf5c5a <3bf5c5a> Failed CI Steps - Observability SRE container smoke test <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3649#0199ab23-5974-4f76-94f3-03b87cf29c0f> - Observability SRE container smoke test <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3649#0199ab2e-8477-4edf-9126-2dec2a5b9ab7> - Observability SRE container smoke test <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3649#0199ab39-4377-45ac-b282-9e6fe275f334> - Observability SRE container smoke test <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3649#0199ab43-ed36-4d99-b904-88dda32321bf> - 🥼 Integration Tests - FIPS mode / part 1-of-6 <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3649#0199ab23-5975-4e5c-b5e0-a7997c1fcef2> History - 💔 Build #3648 <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3648> failed 95f03a2 <95f03a2> - 💔 Build #3647 <https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/3647> failed 079898b <079898b> — Reply to this email directly, view it on GitHub <#18263 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAHYQPMSV74QWKN4DDZZFL3V244NAVCNFSM6AAAAACIE52YESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRWG42TSNJRGY> . You are receiving this because you commented.Message ID: ***@***.***>

[donoghuc]

Yep that worked! thanks

[jsvd]

LGTM