Every time I go to run tests, IntelliJ wants to re...
# contributing-to-airbyte
m
Every time I go to run tests, IntelliJ wants to rebuild the entire Docker ecosystem. Gradle is intelligent enough to know that the Java projects are "UP-TO-DATE", but it completely fails at doing so on the Python side of things, wasting several minutes rebuilding stuff that I haven't even touched, over and over again. The task
:airbyte-integrations:bases:airbyte-protocol:airbyteDocker
seems to be a particularly egregious offender, spending a ton of time rebuilding Docker containers and downloading stuff from Pip. Anyone know of any way to fix this?
u
I'm not familiar with that specific task, but I've solved a similar issue with a JS/npm build task, by adding a
upToDateWhen
in the task.
Copy code
Adds a predicate to determine whether previous outputs of this task can be reused.
https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/TaskOutputs.html?_ga=2.173773027.1359962839.1620878184-1893457966.1615647882#upT[…]ure)