Well, no, I meant "tools". <https://lh3.googleusercontent.com/--OEPByS70RM/Vnehuiq2D3I/AAAAAAAAHFc/edJ7YkamoOU/s1600/Screen%2BShot%2B2015-12-21%2Bat%2B09.49.08.png>
Sources https://github.com/travis-ci/travis-ci/issues/5036 and https://github.com/travis-ci/travis-ci/issues/5049 (this one has great point about problem of versioning of "tools" dependency, which creates non-reproducible builds). *So, I tried to reproduce the problem:* If I try to switch to both Android Gradle Plugin 1.5.0 and build tools 23.0.2 build will fail if I won't add "tools" as build dependency even if build-tools-23.0.2 is set as dependency. <https://lh3.googleusercontent.com/-eH7VyQYJLs8/VneihkRiB1I/AAAAAAAAHFk/TJZ_0L_8d_A/s1600/Screen%2BShot%2B2015-12-21%2Bat%2B09.55.02.png> But if I add "tools" as dependency — build will run and then fail only with Lint because Travis CI has platform-tools-21 by default. <https://lh3.googleusercontent.com/-ed29erHBULI/Vnek9tOLDuI/AAAAAAAAHF4/OvvgxjZPlBw/s1600/Screen%2BShot%2B2015-12-21%2Bat%2B10.05.47.png> And then if I add "platform-tools" as dependency — build will pass. That said, both "tools" and "platform-tools" required for successful build. History of changes and builds available here https://travis-ci.org/pushtorefresh/storio/branches (branch "build-tools-23.0.2"). So, I think we've figured out what was wrong, feel free to ask more details if needed! On Saturday, December 19, 2015 at 7:41:56 AM UTC+3, Tor Norbye wrote: > > Aha. > > You mean platform-tools, not tools, right? > > platform-tools has been there all along; it's not a new component, but you > may not have installed it on your build servers; it's the component which > distributes for example "adb". However, it also contains the most recent > platform data; in particular, it's where lint's API database is > distributed. > > When Android M shipped, there was a packaging error such that the API > database didn't include the M APIs, so people using M APIs weren't warned > by lint when accessing APIs with minSdkVersion < 23. Turned out a lot of > people didn't realize they needed to update the platform tools to have the > latest version. So for that reason I added an explicit check to make sure > that you have the API database installed that is at least as high as your > compileSdkVersion. I made this an error, since failing to check for APIs > can lead to runtime crashes, and a lot of users were bitten by this. > > -- Tor > > > On Fri, Dec 18, 2015 at 5:30 PM Artem Zinnatullin <[email protected] > <javascript:>> wrote: > >> Hi, Tor! >> >> Completely forgot about my report here. So, yes we've just printed lint >> xml report as last step of the build and then investigated the problem. >> And unfortunately, found that it was a problem with Android SDK manager. >> Idk why but for some reason you've added a new piece to Android SDK called >> "tools" and it's now required for building projects. So we had to add it >> as CI environment dependency and then got successful build. Also, as far as >> I remember lint message was pretty misleading, something like "You have >> tools 22 but to check api 23 you need to update build tools" so we spent >> some amount of time to figure out that we actually had to download "tools" >> and not only "build-tools". >> >> Problem was resolved, sorry for not mentioning it here and thanks for >> paying attention to it (I understand that you have a lot of work and such >> delays are ok). >> >> // Extra thanks for mentioning textReport option, will use it in all >> projects! >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
