Skip to content

Unnecessary configuration cache invalidation #34

Description

@tg-freigmbh

With enabled configuration cache executing dotnetBuild mutliple times without any changes will cause
Calculating task graph as configuration cache cannot be reused because output of the external process 'dotnet' has changed.
There are (at least) 2 culprits here

  1. Executing dotnet restore at configuration time with normal verbosity (default settings) will cause dotnet to print the exact durations like Restore succeeded with 2 warning(s) in 0,5s which are not reprodicble. This could be worked around by setting beforeBuild true or by setting the verbositvity to quiet
  2. The Order of the Project Properties printed by the ProjectFileParser is not stable. This requires changes to the codebase, either the ProjectFileParser needs to produce stable output, or this needs to be handled on gradle side using https://docs.gradle.org/current/javadoc/org/gradle/api/provider/ValueSource.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions