What are the differences between Gradle configuration in Windows and Linux ?, Gradlelinux
My development environment: Windows + Android Studio + Gradle 2.8 all + Jenkins
Company CI server environment: Linux + Gradle 2.10 bin + Jenkins
Linux in the following section only indicates the company's 72 CI server configuration. Based on the Linux server and Mac computer, it is available for reference.
What are the differences between Gradle configuration in Windows and Linux?
1. Different paths
1. the SDK path in the local. properties File
A) In Windows, sdk. dir = D \: \ Android \ sdk. Note the escape characters, which are the same below.
B) Linux sdk. dir =/home/adt-bundle-linux-x86/sdk
2. Gradle path and version in the gradle-wrapper.properties File
A) On Windows, distributionUrl = https \: // services.gradle.org/distributions/gradle-2.8-all.zip
B) on Linux, distributionUrl = https \: // services.gradle.org/distributions/gradle-2.10-bin.zip
3. The path of the signature file in the keystore. properties file is different.
A) storeFile =\\ keys \ JenkinsGradleTest. jks on Windows
B) storeFile =/keys/JenkinsGradleTest. jks on Linux
2. Different compilation versions and tool versions
A) minSdkVersion 14, targetSdkVersion 18, and buildToolsVersion "23.0.2" on Windows"
B) minSdkVersion 14, targetSdkVersion 19, buildToolsVersion "21.0.2" on Linux"
III,GradleDifferent parameters
A) In Windows, C:/Users/Kenny/. gradle/gradle. properties is set as follows: org. gradle. daemon = true
B) Set/home/tester/. gradle/gradle. properties in Linux as follows: org. gradle. daemon = false
Purpose: Enable gradle to run in the background process, so as to avoid frequent start and destruction of gradle instances during development, so as to achieve faster execution of gradle. For more information, see: https://docs.gradle.org/2.10/userguide/gradle_daemon.html