Managing Android's dependencies with Gradle is done in a weird way. They have to be downloaded differently into a local repo. This is a pain when setting up CI build as there are multiple nodes this could run on. As such I'm using the sdk-manager-plugin to have the Android dependencies downloaded at build time. There seems to be an old bug that I'm experiencing with the sdk-manager-plugin though in that it will download the dependencies at build time, but they won't be available on that command.
The next time the command is run everything works fine (as everything is already downloaded), but I need to find a way to ignore the build failure of the first gradle command so that everything is downloaded and good to go for the second. I realize this is hacky, but I'm done messing with this.
Ideally something like this would work:
./gradlew clean --ignoreBuildFailures
./gradlew distributeCIBuild
The closest thing I could find in the Gradle documentation is --quite but that doesn't look like it'd work.
Any creative solutions welcome.
--continue
? – Telesis--continue
. – Snavely./gradlew --help
or looking at [1]. The description is "Continues task execution after a task failure". [1]: gradle.org/docs/current/userguide/gradle_command_line.html – Telesis--ignoreBuildFailures
, do you think it'd work if I replace that with--continue
? It sounds like it'd still fail the build after the clean was run. It just saves it till the end. – Snavely