Make gradle the root of every dependency graph by donoghuc · Pull Request #18471 · elastic/logstash

donoghuc · 2025-12-08T23:32:49Z

Release notes

[rn:skip]

What does this PR do?

Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate. By moving everything to gradle we can start leveraging the dependency management to ensure that jruby etc is stardardized across CI use cases and therefore stop managing jruby environments that match that which is shipped with logstash separately.

Closes Make gradle the main entrypoint for any logstash related build task #18475

github-actions · 2025-12-08T23:33:00Z

🤖 GitHub comments

Just comment with:

run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
/run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

mergify · 2025-12-08T23:33:25Z

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

Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate.

donoghuc · 2025-12-10T01:47:03Z

Note to self: make sure to re-evaluate https://github.com/elastic/logstash/pull/18340/files#r2488030095

donoghuc · 2025-12-10T23:39:33Z

run exhaustive tests

donoghuc · 2025-12-11T00:05:06Z

Got through PR tests, moving on the exhaustive next (Still need to do DRA and ansillary).

donoghuc · 2025-12-12T00:13:19Z

rubyUtils.gradle

 }

+// Spawn rake as external process (for CI compatibility)
+def rakeExternal(File projectDir, File buildDir, String task) {


Seems like file descriptor inheretance is tripping up how fpm (https://github.com/jordansissel/fpm/blob/d9be49871fe040937b63d1223491fc352508ab78/lib/fpm/util.rb#L8) wants to shell out to tar. I found jruby/jruby#5249 which seems similar (but should have been resolved).

For now tasks that use fpm shell out to rake instead of using jruby via gradle.

example failure https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/2998#019b0aa3-ff39-4b6b-9f37-cfd4cf1aa73b:

2025-12-10 15:45:17 PST | [artifact:deb] building deb package for x86_64 2025-12-10 15:45:17 PST | Rake task error: Errno::EBADF: Bad file descriptor - tar 2025-12-10 15:45:27 PST | Backtrace: org/jruby/RubyProcess.java:1779:in `spawn' 2025-12-10 15:45:17 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/fpm-1.17.0/lib/fpm/util.rb:145:in `execmd' 2025-12-10 15:45:17 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/fpm-1.17.0/lib/fpm/util.rb:186:in `safesystem' 2025-12-10 15:44:34 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/fpm-1.17.0/lib/fpm/package/deb.rb:1043:in `block in write_control_tarball' 2025-12-10 15:45:27 PST | <internal:uri:classloader:/jruby/kernel/kernel.rb>:19:in `tap' 2025-12-10 15:44:34 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/fpm-1.17.0/lib/fpm/package/deb.rb:1033:in `write_control_tarball' 2025-12-10 15:45:17 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/fpm-1.17.0/lib/fpm/package/deb.rb:677:in `output' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/rakelib/artifacts.rake:853:in `package' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/rakelib/artifacts.rake:672:in `package_with_jdk' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/rakelib/artifacts.rake:313:in `block in <main>' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/rake-13.3.1/lib/rake/task.rb:281:in `block in execute' 2025-12-10 15:45:27 PST | org/jruby/RubyArray.java:2009:in `each' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/rake-13.3.1/lib/rake/task.rb:281:in `execute' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/rake-13.3.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain' 2025-12-10 15:45:27 PST | org/jruby/ext/monitor/Monitor.java:82:in `synchronize' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/rake-13.3.1/lib/rake/task.rb:199:in `invoke_with_call_chain' 2025-12-10 15:45:27 PST | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1765410090515934184/elastic/logstash-exhaustive-tests-pipeline/vendor/bundle/jruby/3.1.0/gems/rake-13.3.1/lib/rake/task.rb:188:in `invoke' 2025-12-10 15:45:27 PST | <script>:6:in `<main>'

donoghuc · 2025-12-12T00:26:18Z

run exhaustive tests

donoghuc · 2025-12-12T00:28:22Z

Made more progress on acceptance tests... The fpm gem does not like being called from gradle/jruby 😅 #18471 (comment)

Also, there will be some follow on work with invokingh bunlder directly for acceptance tests. For now, instead of invoking rake i'm invoking bundler, but i have not decided if that is actually a win or not.

donoghuc · 2025-12-12T23:58:55Z

Today i was able to figure out the fpm issues but the problem i'm playing whack-a-mole with is the management of dowloading jdk. The exhaustive test pipeline provides an example of an issue i'm facing.

Currently as a prep step we run ./gradlew clean bootstrap artifactDeb artifactRpm to prepare artifacts for testing on linux targets which consume .rpm and .deb packages. When run in isolation (for example artifactDeb) we can prepare a complete artifact (in this case one that includes a jdk). This has a dependsOn for copyJdk and is "finalized" by a delete of that jdk. Unfortunately when run together (artifactDeb artifactRpm) the deletion does not inform gradle that copyJdk is needed again and the wrong JDK is used.

I need to figure out exactly which tasks need the copyJdk (and which explicitly need it deleted) in order to figure out how to best represent it in gradle.

This reverts commit c5387b6.

donoghuc · 2025-12-15T20:01:33Z

run exhaustive tests

donoghuc · 2025-12-15T21:21:35Z

run exhaustive tests

build.gradle

rubyUtils.gradle

donoghuc · 2025-12-16T21:16:33Z

run exhaustive tests

donoghuc · 2025-12-16T21:17:16Z

I kicked off a DRA snapshot job on this to double check things would build. Obviously it fails to be published (desireable). Just wanted to make sure build is all working. Seems good! https://buildkite.com/elastic/logstash-dra-snapshot-pipeline/builds/4307

elasticmachine · 2025-12-16T21:42:56Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: e83867d

Failed CI Steps

🥼 IT Persistent Queues / part 4-of-6

History

💛 Build #3965 was flaky e9b6883
💚 Build #3963 succeeded edb91db
💚 Build #3960 succeeded 30467c9
💛 Build #3959 was flaky 295b9a0
💔 Build #3958 failed c5387b6
💚 Build #3956 succeeded 5c08684

mashhurs

LGTM!
I don't have much context but from the "rake calling to gradle" goal point of view, looks great. Thank you for the effort!

mashhurs · 2025-12-16T22:26:46Z

build.gradle

 }

 clean {
+    dependsOn deleteLocalJdk


mashhurs · 2025-12-16T22:41:45Z

rakelib/artifacts.rake

  def package_with_jdk(platform, jdk_arch, variant = :standard)
-    safe_system("./gradlew copyJdk -Pjdk_bundle_os=linux -Pjdk_arch=#{jdk_arch}")
    package(platform, variant, true, jdk_arch)
-    safe_system('./gradlew deleteLocalJdk -Pjdk_bundle_os=linux')


It looks like we removed all jdk_bundle_os usages, maybe removing in seelctOsType() also makes sense?

Yeah, i'll look in to that with the removal tasks #18476

mashhurs · 2025-12-16T22:47:30Z

ci/acceptance_tests.sh


 echo "--- Acceptance: Running the tests"
+# TODO: figure out how to encapsulate all this in gradle or at least ensure the bundler
+# used here ends up using the runtime managed with LS. 


Are you going to follow up with next iterations?

yep! this will fall under the ticket for using gradle for managing ruby runtime #18477

donoghuc · 2025-12-19T19:29:03Z

Now that the 9.3 branch has been cut, i'm going to get this merged so i can build the PR for removal of unused tasks on this. I'll keep an eye on CI in the main branch to make sure there are no surprises!

github-actions · 2026-01-20T23:38:36Z

@Mergifyio backport 8.19 9.1 9.2 9.3

mergify · 2026-01-20T23:38:47Z

backport 8.19 9.1 9.2 9.3

✅ Backports have been created

Details

#18607 [8.19] (backport #18471) Make gradle the root of every dependency graph has been created for branch 8.19 but encountered conflicts

Cherry-pick of ca1fe37 has failed:

On branch mergify/bp/8.19/pr-18471
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit ca1fe3761.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/scripts/dra/build_docker.sh
	modified:   .buildkite/scripts/dra/build_packages.sh
	modified:   .buildkite/scripts/exhaustive-tests/generate-steps.py
	modified:   ci/acceptance_tests.sh
	modified:   ci/ci_docs.sh
	modified:   ci/docker_acceptance_tests.sh
	modified:   rakelib/compile.rake
	modified:   rakelib/z_rubycheck.rake

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   build.gradle
	both modified:   rakelib/artifacts.rake
	both modified:   rakelib/test.rake
	both modified:   rakelib/vendor.rake

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

#18608 [9.1] (backport #18471) Make gradle the root of every dependency graph has been created for branch 9.1 but encountered conflicts

Cherry-pick of ca1fe37 has failed:

On branch mergify/bp/9.1/pr-18471
Your branch is up to date with 'origin/9.1'.

You are currently cherry-picking commit ca1fe376.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/scripts/dra/build_docker.sh
	modified:   .buildkite/scripts/dra/build_packages.sh
	modified:   .buildkite/scripts/exhaustive-tests/generate-steps.py
	modified:   ci/acceptance_tests.sh
	modified:   ci/ci_docs.sh
	modified:   ci/docker_acceptance_tests.sh
	modified:   rakelib/compile.rake
	modified:   rakelib/z_rubycheck.rake

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   build.gradle
	both modified:   rakelib/artifacts.rake
	both modified:   rakelib/test.rake
	both modified:   rakelib/vendor.rake

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

#18609 [9.2] (backport #18471) Make gradle the root of every dependency graph has been created for branch 9.2 but encountered conflicts

Cherry-pick of ca1fe37 has failed:

On branch mergify/bp/9.2/pr-18471
Your branch is up to date with 'origin/9.2'.

You are currently cherry-picking commit ca1fe376.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/scripts/dra/build_docker.sh
	modified:   .buildkite/scripts/dra/build_packages.sh
	modified:   .buildkite/scripts/exhaustive-tests/generate-steps.py
	modified:   ci/acceptance_tests.sh
	modified:   ci/ci_docs.sh
	modified:   ci/docker_acceptance_tests.sh
	modified:   rakelib/artifacts.rake
	modified:   rakelib/compile.rake
	modified:   rakelib/z_rubycheck.rake

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   build.gradle
	both modified:   rakelib/test.rake
	both modified:   rakelib/vendor.rake

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

#18610 [9.3] (backport #18471) Make gradle the root of every dependency graph has been created for branch 9.3 but encountered conflicts

Cherry-pick of ca1fe37 has failed:

On branch mergify/bp/9.3/pr-18471
Your branch is up to date with 'origin/9.3'.

You are currently cherry-picking commit ca1fe376.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/scripts/dra/build_docker.sh
	modified:   .buildkite/scripts/dra/build_packages.sh
	modified:   .buildkite/scripts/exhaustive-tests/generate-steps.py
	modified:   ci/acceptance_tests.sh
	modified:   ci/ci_docs.sh
	modified:   ci/docker_acceptance_tests.sh
	modified:   rakelib/artifacts.rake
	modified:   rakelib/compile.rake
	modified:   rakelib/z_rubycheck.rake

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   build.gradle
	both modified:   rakelib/test.rake
	both modified:   rakelib/vendor.rake

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

* WIP: Make gradle the root of every dependency graph Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate. * replicate rake behavior with copyjdk * jdk for observabilitySRE artifact * serialize jdk cleanup * try sub process * and rpm... * fix acceptance script * rake task from qa dir context * revert to calling bundler directly * fix copy paste * remove complex function and add explicit require * manage jdk at task level * Revert "manage jdk at task level" This reverts commit c5387b6. * stop deleting jdk * cleanup * remove unused file * more cleanup * copyjdk for all artifacts * fpm file descriptor workaround * postpone deletion work * restore rake task impl for unused script (cherry picked from commit ca1fe37) # Conflicts: # build.gradle # rakelib/artifacts.rake # rakelib/test.rake # rakelib/vendor.rake

* WIP: Make gradle the root of every dependency graph Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate. * replicate rake behavior with copyjdk * jdk for observabilitySRE artifact * serialize jdk cleanup * try sub process * and rpm... * fix acceptance script * rake task from qa dir context * revert to calling bundler directly * fix copy paste * remove complex function and add explicit require * manage jdk at task level * Revert "manage jdk at task level" This reverts commit c5387b6. * stop deleting jdk * cleanup * remove unused file * more cleanup * copyjdk for all artifacts * fpm file descriptor workaround * postpone deletion work * restore rake task impl for unused script (cherry picked from commit ca1fe37) # Conflicts: # build.gradle # rakelib/test.rake # rakelib/vendor.rake

…ph (#18607) * Make gradle the root of every dependency graph (#18471) * WIP: Make gradle the root of every dependency graph Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate. * replicate rake behavior with copyjdk * jdk for observabilitySRE artifact * serialize jdk cleanup * try sub process * and rpm... * fix acceptance script * rake task from qa dir context * revert to calling bundler directly * fix copy paste * remove complex function and add explicit require * manage jdk at task level * Revert "manage jdk at task level" This reverts commit c5387b6. * stop deleting jdk * cleanup * remove unused file * more cleanup * copyjdk for all artifacts * fpm file descriptor workaround * postpone deletion work * restore rake task impl for unused script (cherry picked from commit ca1fe37) # Conflicts: # build.gradle # rakelib/artifacts.rake # rakelib/test.rake # rakelib/vendor.rake * fix merge conflicts --------- Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>

#18608) * Make gradle the root of every dependency graph (#18471) * WIP: Make gradle the root of every dependency graph Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate. * replicate rake behavior with copyjdk * jdk for observabilitySRE artifact * serialize jdk cleanup * try sub process * and rpm... * fix acceptance script * rake task from qa dir context * revert to calling bundler directly * fix copy paste * remove complex function and add explicit require * manage jdk at task level * Revert "manage jdk at task level" This reverts commit c5387b6. * stop deleting jdk * cleanup * remove unused file * more cleanup * copyjdk for all artifacts * fpm file descriptor workaround * postpone deletion work * restore rake task impl for unused script (cherry picked from commit ca1fe37) # Conflicts: # build.gradle # rakelib/artifacts.rake # rakelib/test.rake # rakelib/vendor.rake * resolve merge conflicts --------- Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>

#18609) * Make gradle the root of every dependency graph (#18471) * WIP: Make gradle the root of every dependency graph Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate. * replicate rake behavior with copyjdk * jdk for observabilitySRE artifact * serialize jdk cleanup * try sub process * and rpm... * fix acceptance script * rake task from qa dir context * revert to calling bundler directly * fix copy paste * remove complex function and add explicit require * manage jdk at task level * Revert "manage jdk at task level" This reverts commit c5387b6. * stop deleting jdk * cleanup * remove unused file * more cleanup * copyjdk for all artifacts * fpm file descriptor workaround * postpone deletion work * restore rake task impl for unused script (cherry picked from commit ca1fe37) # Conflicts: # build.gradle # rakelib/test.rake # rakelib/vendor.rake * resolve merge conflicts --------- Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>

#18610) * Make gradle the root of every dependency graph (#18471) * WIP: Make gradle the root of every dependency graph Do a fist pass at removing circular dependency on rake calling to gradle. Replace every "top level" task with a gradle task. This allows doing all dependency management with gradle, while still allowing us to use rake for leaf node tasks when appropriate. * replicate rake behavior with copyjdk * jdk for observabilitySRE artifact * serialize jdk cleanup * try sub process * and rpm... * fix acceptance script * rake task from qa dir context * revert to calling bundler directly * fix copy paste * remove complex function and add explicit require * manage jdk at task level * Revert "manage jdk at task level" This reverts commit c5387b6. * stop deleting jdk * cleanup * remove unused file * more cleanup * copyjdk for all artifacts * fpm file descriptor workaround * postpone deletion work * restore rake task impl for unused script (cherry picked from commit ca1fe37) # Conflicts: # build.gradle # rakelib/test.rake # rakelib/vendor.rake * fix merge conflicts --------- Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>

donoghuc force-pushed the gradle-everywhere branch from 6b91281 to 4fd6bbb Compare December 8, 2025 23:53

donoghuc mentioned this pull request Dec 9, 2025

Make gradle the main entrypoint for any logstash related build task #18475

Closed

donoghuc added 2 commits December 10, 2025 14:49

replicate rake behavior with copyjdk

6fabba3

jdk for observabilitySRE artifact

09be295

donoghuc added 5 commits December 11, 2025 10:48

serialize jdk cleanup

1f8697b

try sub process

87dd607

and rpm...

ce8c78a

fix acceptance script

2463b35

rake task from qa dir context

3b4a571

donoghuc commented Dec 12, 2025

View reviewed changes

revert to calling bundler directly

090182e

donoghuc added 2 commits December 12, 2025 12:37

fix copy paste

2b6945b

remove complex function and add explicit require

5c08684

donoghuc added 3 commits December 15, 2025 11:14

manage jdk at task level

c5387b6

Revert "manage jdk at task level"

8d6a63f

This reverts commit c5387b6.

stop deleting jdk

295b9a0

cleanup

30467c9

donoghuc commented Dec 15, 2025

View reviewed changes

build.gradle Outdated Show resolved Hide resolved

donoghuc commented Dec 15, 2025

View reviewed changes

rubyUtils.gradle Outdated Show resolved Hide resolved

mashhurs approved these changes Dec 16, 2025

View reviewed changes

donoghuc merged commit ca1fe37 into elastic:main Dec 19, 2025
12 of 13 checks passed

donoghuc mentioned this pull request Dec 30, 2025

Use gradle and bundled jruby for acceptance tests orchestration #18536

Merged

donoghuc added the backport-active-all Automated backport with mergify to all the active branches label Jan 20, 2026

mergify bot mentioned this pull request Jan 20, 2026

[8.19] (backport #18471) Make gradle the root of every dependency graph #18607

Merged

mergify bot mentioned this pull request Jan 20, 2026

[9.1] (backport #18471) Make gradle the root of every dependency graph #18608

Merged

mergify bot mentioned this pull request Jan 20, 2026

[9.2] (backport #18471) Make gradle the root of every dependency graph #18609

Merged

mergify bot mentioned this pull request Jan 20, 2026

[9.3] (backport #18471) Make gradle the root of every dependency graph #18610

Merged

donoghuc mentioned this pull request Feb 5, 2026

Respect ARCH env var when downloading JDK via gradle #18733

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Make gradle the root of every dependency graph#18471

Make gradle the root of every dependency graph#18471
donoghuc merged 21 commits intoelastic:mainfrom
donoghuc:gradle-everywhere

donoghuc commented Dec 8, 2025 •

edited

Loading

github-actions bot commented Dec 8, 2025

mergify bot commented Dec 8, 2025

donoghuc commented Dec 10, 2025

donoghuc commented Dec 10, 2025

donoghuc commented Dec 11, 2025

donoghuc Dec 12, 2025

donoghuc commented Dec 12, 2025

donoghuc commented Dec 12, 2025

donoghuc commented Dec 12, 2025

donoghuc commented Dec 15, 2025

donoghuc commented Dec 15, 2025

Uh oh!

Uh oh!

donoghuc commented Dec 16, 2025

donoghuc commented Dec 16, 2025

elasticmachine commented Dec 16, 2025

mashhurs left a comment

mashhurs Dec 16, 2025

mashhurs Dec 16, 2025

donoghuc Dec 19, 2025

mashhurs Dec 16, 2025

donoghuc Dec 19, 2025

donoghuc commented Dec 19, 2025

Uh oh!

github-actions bot commented Jan 20, 2026

mergify bot commented Jan 20, 2026 •

edited

Loading

Labels

3 participants

Conversation

donoghuc commented Dec 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release notes

What does this PR do?

github-actions bot commented Dec 8, 2025

🤖 GitHub comments

mergify bot commented Dec 8, 2025

donoghuc commented Dec 10, 2025

donoghuc commented Dec 10, 2025

donoghuc commented Dec 11, 2025

donoghuc Dec 12, 2025

Choose a reason for hiding this comment

donoghuc commented Dec 12, 2025

donoghuc commented Dec 12, 2025

donoghuc commented Dec 12, 2025

donoghuc commented Dec 15, 2025

donoghuc commented Dec 15, 2025

Uh oh!

Uh oh!

donoghuc commented Dec 16, 2025

donoghuc commented Dec 16, 2025

elasticmachine commented Dec 16, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

History

mashhurs left a comment

Choose a reason for hiding this comment

mashhurs Dec 16, 2025

Choose a reason for hiding this comment

mashhurs Dec 16, 2025

Choose a reason for hiding this comment

donoghuc Dec 19, 2025

Choose a reason for hiding this comment

mashhurs Dec 16, 2025

Choose a reason for hiding this comment

donoghuc Dec 19, 2025

Choose a reason for hiding this comment

donoghuc commented Dec 19, 2025

Uh oh!

github-actions bot commented Jan 20, 2026

mergify bot commented Jan 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Backports have been created

Labels

3 participants

donoghuc commented Dec 8, 2025 •

edited

Loading

mergify bot commented Jan 20, 2026 •

edited

Loading