From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

image.png

Screenshot 2026-07-07 at 11.21.48.png

How the _critical path_ search works ?

On this scan <https://scans.gradle.com/s/jllbgu5bf5u7e/timeline?show-only-critical-path|scans.gradle.com/s/jllbgu5bf5u7e/timeline?…> I would have expected to see these tasks to be in critical path, so I'm quite surprised they weren't.

These tasks have the particularity of using a shared service, that is deliberately using `maxParallelUsage = 1` in CI.

*EDIT:* I should have read the question mark, _determination of the critical path do not consider the build services_.

Ooh, I should have read that bit, it's not very visible until you click _show search_ icon. Then on the critical path toggle there's a question mark

>  NOTE: The determination of the critical path does not consider implicit dependencies imposed when Gradle work units of the same project cannot be executed concurrently, or dependencies imposed by the use of build services.

Hi Brice
Yes, the heuristic is not perfect, as pointed by the question mark. I agree it could be more visible.
We would need to capture more information to make that truly more correct and it's not planned at the moment.

Yeah I was surprised that tasks that were depending on "non parallel" service were not accounted. Maybe that's something that can be contributed in the OSS part of gradle?