Hey friends. Is there a concrete timeline to expos...
# develocity
r
Hey friends. Is there a concrete timeline to expose gradle build scans
performance/configuration
data via develocity api? In addition to our weekly build cache validation I want to add a configuration cache validation ci job to verify our build keeps being configuration cache compatible and hits the configuration cache. We're in the process of migrating but its a longer complex journey so I would like to have sanity checks in ci until we can enable it by default and not having incompatibilities creeping back into our build over time. Seems for now I need to parse the build output till that api is available?
w
Hey René! So what you want to have is a Develocity API endpoint that allows you to know whether a build was a configuration cache hit or not? Do you need something else? We are planning to expose information about the configuration cache on the Develocity API soon. We probably won’t be exposing the remaining information on the
performance/configuration
page in the first step.
r
yeah exactly that. for starters it would be good just to know if configuration cache was reused or not
w
The API in Develocity 2024.2 will look like this:
Copy code
"gradleConfigurationCache": {
      "model": {
        "result": {
          "outcome": "MISS",
          "entrySize": 21541550,
          "store": {
            "duration": 4860,
            "hasFailed": false
          },
          "load": {
            "duration": 3413,
            "hasFailed": false
          },
          "missReasons": [
            "file 'some/build.gradle.kts' has changed"
          ]
        }
      }
You can use the
outcome
to understand whether the configuration cache entry has been re-used or not.
r
great!