Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26383

Determine required SDK versions from gradle builds (without project.properties)

      I just converted our project from Eclipse and maven to Android Studio and gradle. project.properties is no longer the way to specify sdk version. Now there are properties in the build.gradle files. It'd be excellent if this plugin could somehow grab the value from there instead of us storing it in 2 places.

      I suppose a workaround would be to still use project.properties and I can instead read project.properties myself from the gradle scripts and use that for the android compileSdkVersion. Pro: one version, Con: non-standard script.

          [JENKINS-26383] Determine required SDK versions from gradle builds (without project.properties)

          I'm not sure whether I will get around to doing this, as the Android SDK Manager plugin for Gradle does a much better job; it also updates the new local Maven repositories as appropriate:
          https://github.com/JakeWharton/sdk-manager-plugin

          Christopher Orr added a comment - I'm not sure whether I will get around to doing this, as the Android SDK Manager plugin for Gradle does a much better job; it also updates the new local Maven repositories as appropriate: https://github.com/JakeWharton/sdk-manager-plugin

          Matt Mullins added a comment -

          Wow, that looks like a much cleaner solution. From Jake Wharton, too. Thanks for the link!

          Matt Mullins added a comment - Wow, that looks like a much cleaner solution. From Jake Wharton, too. Thanks for the link!

          Unfortunately (Android) SDK Manager Plugin doesn't work anymore (look at the issues, in particular https://github.com/JakeWharton/sdk-manager-plugin/issues/101) and someone is wondering whether it is still maintained or not (https://github.com/JakeWharton/sdk-manager-plugin/issues/84) :/

          Giacomo Boccardo added a comment - Unfortunately (Android) SDK Manager Plugin doesn't work anymore (look at the issues, in particular https://github.com/JakeWharton/sdk-manager-plugin/issues/101 ) and someone is wondering whether it is still maintained or not ( https://github.com/JakeWharton/sdk-manager-plugin/issues/84 ) :/

          I'd rather people use the SDK Manager Plugin, or wait for http://b.android.com/60650 to be implemented, so that it's part of the project, rather than being Jenkins-specific.

          The SDK Manager Plugin still works fine for me, and although there haven't been any recent releases, you can use it via JitPack.

          Christopher Orr added a comment - I'd rather people use the SDK Manager Plugin, or wait for http://b.android.com/60650 to be implemented, so that it's part of the project, rather than being Jenkins-specific. The SDK Manager Plugin still works fine for me, and although there haven't been any recent releases, you can use it via JitPack.

            Unassigned Unassigned
            mttmllns Matt Mullins
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: