Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #6832

D

Develocity

Company blog · gradle.com/blogprogrammingproductivity

Develocity is the company blog at gradle.com, writing about programming and productivity. Since 2016, 12 different Hacker News readers have linked it 14 times. No feed was found, so read it on the site itself.

No feed foundVisit the blog
14mentions?
12HN people?
2016–2025first – last linked?
Links on Hacker News per year · peak 3 in 2019

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

HN commenters link Gradle's company site as evidence of Gradle, Inc.'s commercial backing, its customer list, and its product documentation on Build Scans. The posts are referenced, not judged.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Develocity encodes a decade of build and test expertise into a context engineering layer, with agents and engines that govern and accelerate software delivery.

What Hacker News says?

  1. > The only projects I see reliably escaping this trap are ones with commercial backing. Gradle is backed by Gradle, Inc. [1] who provide commercial support and presumably a lot of development as well. [1] https://gradle.com/

    Comment linking /

    on “The Problem with Gradle”
  2. Submitted How to Solve Google’s Billion-Dollar Productivity Problem as a story · 28 points

    HN discussion
  3. Sorry that you feel this way, but this is simply not true. If it were the case, why would all these companies [0] waste their time with Gradle? Bad technologies tend do die out. Not the case here. 0 - https://gradle.com/customers (Edit: Heh, TIL rage downvotes are a thing in HN as well.)

    Comment linking /customers

    on “The Problem with Gradle”
  4. Submitted Apache Maven️ Support Coming to Gradle Enterprise as a story · 6 points

    HN discussion
  5. They transitioned to a product company 5+ years ago. https://gradle.com Gradle's complexity comes from at least two places: 1. The original vision of solving complex multi-technology/language Enterprise builds. 2. Poor early design decisions that they never recovered from.

    Comment linking /

    on “Mill: A fast JVM build tool for Java and Scala”
  6. Submitted Gradle Announces Predictive Test Selection: ML for JVM-Based Tests as a story · 2 points

    HN discussion
  7. At the moment there are two steps if you want to view a Build Scan, one is to add the plugin and the other is to add -DScan to the command line. Data doesn't go anywhere unless you have explicitly done both of those things. If you're curious how this works look here https://gradle.com/whats-new-gradle/

    Comment linking /whats-new-gradle/

    on “Gradle 3.0 Release Notes”
  8. Submitted Why faster coding doesn't mean faster software delivery as a story · 1 points

    HN discussion
  9. Submitted Gradle Reduced Build Scan Storage Costs on AWS by 75% as a story · 1 points

    HN discussion
  10. Submitted Gradle Enterprise is now Develocity as a story · 1 points

    HN discussion
  11. Submitted Reasons You Should Not Ignore Flaky Tests as a story · 1 points

    HN discussion
  12. Submitted Acceleration and Insights for Spring Boot Maven Builds as a story · 1 points

    HN discussion
  13. Submitted Maven Build Cache as a story · 1 points

    HN discussion
  14. Submitted How to calculate the costs of your builds and the return you get on improving it as a story · 1 points

    HN discussion

Search all of HN for gradle.com