Google Git
Sign in
chromium/external/github.com/gradle/gradle/refs/heads/fix-CapturingUserInputCrossVersionSpec
commit
ef7027f5f5a6360acc2556dd6d2e5faf26996abe
[log]
author
Bo Zhang <bo@gradle.com>
Wed Jun 03 03:50:24 2026
committer
Bo Zhang <bo@gradle.com>
Wed Jun 03 03:50:24 2026
tree
6532a714896d74a7972f7e7e6a2640cb4dffc259
parent
cdf0115de5d796708f704f2c42cf76e50ea5e798 [diff]
Exclude Gradle 8.8 daemon from CapturingUserInputCrossVersionSpec

The "TAPI current -> Gradle 8.8" direction fails deterministically: the answer
forwarded on stdin comes back as "License accepted: null".

Gradle 8.8 is a unique broken window. It shipped the new client-side prompt
protocol (PromptOutputEvent/UserResponse), but the daemon still greedily
consumed the client's stdin, so the forwarded "yes" is swallowed as raw stdin
before the prompt response is read and askYesNoQuestion returns null. The greedy
consumption was removed in 8.9 (66832d04eff); 8.7 and earlier use the older
protocol and are unaffected. The 8.8 daemon is released and cannot be fixed.

Exclude only the 8.8 daemon via `!8.8`, preserving coverage for all other
versions and for the reverse "TAPI 8.8 -> Gradle current" direction.

Verified locally (ByteArrayInputStream, --rerun-tasks): current->8.7 and
current->8.9 pass 3/3, current->8.8 fails 3/3; with the exclusion the 8.8 daemon
direction is no longer run while 8.7/8.9 and the 8.8->current direction pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 file changed
tree: 6532a714896d74a7972f7e7e6a2640cb4dffc259
  1. .github/
  2. .idea/
  3. .teamcity/
  4. architecture/
  5. build-logic/
  6. build-logic-commons/
  7. build-logic-settings/
  8. contributing/
  9. gradle/
  10. images/
  11. packaging/
  12. platforms/
  13. subprojects/
  14. testing/
  15. .coderabbit.yaml
  16. .editorconfig
  17. .gitattributes
  18. .gitignore
  19. .mailmap
  20. AI_POLICY.md
  21. build.gradle.kts
  22. CONTRIBUTING.md
  23. gradle.properties
  24. gradlew
  25. gradlew.bat
  26. KEYS.md
  27. LICENSE
  28. README.md
  29. released-versions.json
  30. settings.gradle.kts
  31. version.txt
README.md

🐘 Gradle Build Tool

Gradle is a highly scalable build automation tool designed to handle everything from large, multi-project enterprise builds to quick development tasks across various languages. Gradle’s modular, performance-oriented architecture seamlessly integrates with development environments, making it a go-to solution for building, testing, and deploying applications on Java, Kotlin, Scala, Android, Groovy, C++, and Swift.

For a comprehensive overview, please visit the official Gradle project homepage.

🚀 Getting Started

Starting with Gradle is easy with these essential resources. Follow these to install Gradle, set up initial projects, and explore supported platforms:

📘 Explore Gradle’s full array of resources through the Gradle Documentation.

🛠 Seamless IDE & CI Integration

Gradle is built to work smoothly with a variety of Integrated Development Environments (IDEs) and Continuous Integration (CI) systems, providing extensive support for a streamlined workflow:

🎓 Learning Resources for Gradle

Kickstart your Gradle knowledge with courses, guides, and community support tailored to various experience levels:

  • DPE University Free Courses: A collection of hands-on courses for learning Gradle, complete with project-based tasks to improve real-world skills.
  • Gradle Community Resources: Discover a range of resources, tutorials, and guides to support your Gradle journey, from foundational concepts to advanced practices.

💬 Community Support & Resources

The Gradle community offers a range of forums, documentation, and direct help to guide you through every step of your Gradle journey:

  • Documentation: The Gradle User Manual covers everything from basic to advanced configurations.
  • Community Forum: Engage with others on the Gradle Forum for discussions, tips, and best practices.
  • Community Slack: Join our Slack Channel for real-time discussions, with specialized channels like #github-integrations for integration topics.
  • Newsletter: Subscribe to the Gradle Newsletter for news, tutorials, and community highlights.

Quick Tip: New contributors to Gradle projects are encouraged to ask questions in the Slack #community-support channel.

🌱 Contributing to Gradle

  • Contribution Guide: Contribute to Gradle by submitting patches or pull requests for code or documentation improvements.
  • Code of Conduct: Gradle enforces a Code of Conduct to ensure a welcoming and supportive community for all contributors.

🔗 Additional Resources

To make the most out of Gradle, take advantage of these additional resources:

🌟 Stay connected with the Gradle Community and access the latest news, training, and updates via Slack, Forum, and our Newsletter.