It seems that we have a lot of flakiness on the Build and Test Java > Build with Gradle step, and there's some suspicion that it might come from caching intermediate results and Jabel.
Adding --rerun-tasks seems like a good balance -- we don't disable cache completely (so we keep Maven artifacts) but we rebuild any unchanged dependencies to prevent such problems.
It seems that we have a lot of flakiness on the
Build and Test Java > Build with Gradlestep, and there's some suspicion that it might come from caching intermediate results and Jabel.Adding
--rerun-tasksseems like a good balance -- we don't disable cache completely (so we keep Maven artifacts) but we rebuild any unchanged dependencies to prevent such problems.