[9.1] (backport #17945) Replace buildkite jdk version check w/GH action #18214
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Replace buildkite jdk version check w/GH action Previously a weekly buildkite job would check if there is a newer JDK available than the one vendored in logstash. This job would fail until someone manually updated the JDK version in the `versions.yml` file in logstash. This commit reduces manual intervention by moving the responsibility to a GH action where there are patterns for creating PRs back to logstash. The action should run weekly and also be available in the actions UI. It is locked down with the same permissions as the version bump action. * Refactor to use updatecli * Remove gradle task in favor of updatecli * remove unused file * Dynamically generate java version lookup * make pipeline name unique' ' (cherry picked from commit 2fab5f4)
5 tasks
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
Collaborator
💚 Build Succeeded
cc @donoghuc |
donoghuc
approved these changes
Sep 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release notes
[rn:skip]
What does this PR do?
Previously a weekly buildkite job would check if there is a newer JDK available than the one vendored in logstash. This job would fail until someone manually updated the JDK version in the
versions.ymlfile in logstash. This commit reduces manual intervention by moving the responsibility to a GH action where there are patterns for creating PRs back to logstash. The action should run weekly and also be available in the actions UI. It is locked down with the same permissions as the version bump action. The gradle task has been replaced with the updatecli pattern established in #18035Why is it important/What is the impact to the user?
No user impact, quality of life improvement for logstash devs.
Checklist
How to test this PR locally
Downgrade java version in
versions.ymland run./gradlew updateJdkVersionto update it back to latest.Related issues
This is an automatic backport of pull request #17945 done by [Mergify](https://mergify.com).