Welcome to the July 2022 Gradle Build Tool newsletter.
What a big month for the community! This edition features tips and insights from new faces and familiar favorites. From The Gradle Build Tool Team, we launched a new mentorship program, invited new members to the Gradle Fellowship, shared our ideas on remote/distributed builds, and simplified plugin publishing with a new plugin.
From the Community
- There Is No Single Dependency Graph - We talk a lot about a project’s dependency graph; this reminds us that dependencies are a more nuanced concept and need more careful consideration.
- Schrodinger’s Input - Having a remote cache miss is a common problem; here is a good use case for how to walk through the problem.
- Gradle Configuration Caching — Replacing a Build Listener With Build Services - The example takes advantage of the full Configuration Cache potential while still collecting Gradle build information.
- First Steps Developing Custom Gradle Plugins - Need custom build logic but not sure where to start? This introduction starts from nothing and uses the Gradle documentation to publish the custom build logic as plugins to mavenLocal.
- Run Groovy Shell in the Context of a Gradle Build - Use ObjectBrowser GUI to explore the Gradle build context interactively.
- Understanding Gradle #17 – Feature Variants - Understand features in Java projects and see how to use them with variant-aware dependency management
- Understanding Gradle #18 – Configuring Testing - Best practices for all things testing in Gradle.
- Gradle Tutorial - Crash Course - Learn the basics by seeing details of a multi-module build. Good demo on the scope of implementation vs api dependencies.
- Writing Paparazzi Tests for Your Kotlin Multi Platform Projects - This shows an example where they wanted to use
compose-jbbut the plugin was not compatible with Kotlin MultiPlatform. See an easy workaround.
From Gradle Team
We are excited to launch our Mentoring Program to increase diversity inside the Gradle Build Tool community. Gradle Fellowship members volunteer their time and talent to mentor others. Applications for the first round of mentoring close soon; apply now.
Welcome to the Gradle Fellowship to Chris Doré, Cristian Garcia, Ryan Harter, Jendrik Johannes, Aurimas Liutikas. They go above and beyond with a dedicated commitment to sharing knowledge, and we are honored to have them in our community.
Curious about remote and distributed builds? We just published a series of blog posts, Remote and Distributed Build Patterns which explains the differences between remote and distributed builds and variations on each, and General Build Distribution: A Game-Changer or a Gimmick? about the tradeoffs with general build distribution.
Plugin Publish Plugin v1.0
Configuring the publication of Gradle plugins to the Plugin Portal happens with the help of the Plugin-Publish plugin. The recently released version 1.0.0 of the plugin significantly improves the process by introducing stronger conventions and a more straightforward configuration. Read our blog post for more information.
If you share our passion for developer productivity and tooling, consider joining our globally distributed team and check out our job openings at gradle.com/careers. We are looking for new teammates, including software engineers, solutions engineers, SEO & SEM manager, account executives, and developer productivity engineers.
- July 22 12:00 pm - 3:00 pm (US EDT): Virtual Workshop - Gradle Build Cache Deep Dive
- July 26 2:00 pm - 3:00 pm (US EDT): Virtual Training - Gradle Enterprise for Productivity Engineers Training
- July 27 9:00 am - 10:00 am (US EDT): Virtual Training - Gradle Enterprise for Productivity Engineers Training
- July 28 11:30 am - 3:30 pm (US EDT): Virtual Training - Introduction to Developer Productivity Engineering
- August 9 8:30 am - 12:30 pm (US EDT): Virtual Workshop - Introduction to Gradle Build Tool Course
See the Gradle Training webpage for an up-to-date list of all upcoming educational and training events.
If you have some news you’d like us to share in the next issue, use #gradle on Twitter or send us an email with the details to firstname.lastname@example.org.
Until next time!
—The Gradle Build Tool Team