The build is down to 8 minutes, which is awesome! @s is this from your change? or should we be worried 😉

dammit, pretty sure this is unintended. If you look at a build scan for integration tests in one of these 8m CI jobs: https://scans.gradle.com/s/e4ef5ioju4eyc you’ll notice that we skipped running integration tests. This is pretty surprising, because all interation tests have an explicit

dependsOn

building the docker image task, which is explicitly blocked from caching its results. So I would have expected the integrations modules to effectively never get cached. Turns out that

dependsOn

alone is not enough to tell Gradle that caching should be impacted by this. We explicitly need to add the output of that task as an input to the dependent task via

inputs

and

outputs

. Gonna disable caching for now until we make a way around this. On the upside, this is a glimpse of the kind of performance we can expect if we wire up caching correctly. Thanks for pointing this out, and apologies for the issue. I’ve put up a PR to disable caching for now: https://github.com/airbytehq/airbyte/pull/692

We explicitly need to add the output of that task as an input to the dependent task via 

inputs

 and 

outputs

.

is this hard to do?

didn’t get a chance to look into it yet

disabled caching to be safe