Guilherme Lima Pereira
tasks that each extract files an archive into a directory. Each task has a different archive as input and a different output directory, so they should be completely independent, but they’re running sequentially, rather than in parallel. Is this expected? 🧵
for my project it succeeds. If I run
it fails on varying "could not resolve" or "could not download" artifact exceptions. The project in question is configured to exclusively use an internal Nexus proxy repo via a
gradle-profiler --project-dir . --benchmark build
block in settings.gradle.kts, which notably is incubating. Trying gradle-profiler on a different project, one that is configured to use Maven Central directly, works without issue. Could it be that gradle-profiler doesn't yet support
configuration, or is there something else I should do to troubleshoot this issue?
. I see heapdump option only for profiling case.
Andrea Di Menna
into ram disk? 🤔
with gradle profiler? I want to avoid hitting remote build cache.