Sure, we don't commit `local.properties` to VCS. But we do need to run few scripts locally with ability to ignore `local.properties`.
If you curious in what I'm talking about in details: I'm setting up remote build when you as a developer work on project in AS on your local machine, but build it on a remote machine (with much better hardware) and results are transparently available on your local AS, it works, but we have to ignore `local.properties` from "local" machine during the build on "remote" machine which is currently only possible via renaming `local.properties`. On Wednesday, November 30, 2016 at 1:18:00 PM UTC+3, Michal Bendowski wrote: > > What scripts are you talking about? local.properties are not meant to be > checked-in to your VCS, hence we don't expect them to exist in a CI > environment for instance. > > Michal > > On Tuesday, November 29, 2016 at 11:45:57 PM UTC, Artem Zinnatullin wrote: >> >> At the moment Android Gradle Plugin looks for `local.properties` >> <https://android.googlesource.com/platform/tools/build/+/69c4b95102b4b9862bfba68b3eaf5b7537a705ee/gradle/src/main/groovy/com/android/build/gradle/internal/Sdk.groovy#169> >> >> and if it finds one, it grabs things like path to Android SDK from it. Even >> though required environment variables may be present. >> >> AS kinda forces you to create `local.properties` (or it autocreates it), >> but we need to ignore them to run some scripts. >> >> Would be very helpful if there would be an option that we could pass via >> Gradle paramets to disable `local.properties` lookup because currently we >> have to rename this file before running our scripts and then restore it >> back after which looks very awful from many points. >> >> Thanks! >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
