Instead, I chose to own the responsibility of the version of tools needed on my build nodes for the types of projects I intend to compile on them. Thanks Google, you really know how to break my build. I have 'build-tools-24.0.1' in there because the app I'm working with has not been upgraded to the latest version of Gradle, but it's worth noting too because not everyone has the luxury of changing code/compile settings just because Google ships new binaries. Not complicated, really, but worth documenting for others out there.īackwards-compatibility for Build Tools in Jenkins RUN ( sleep 5 & while do sleep 1 echo y done ) | /opt/android-sdk-linux/tools/android update sdk -no-ui -filter platform-tools,android-24,build-tools-24.0.1,tools,extra-android-support,extra-android-m2repository RUN sed -i '$ a\export PATH="$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools:$PATH"' /etc/profile.d/android.sh RUN sed -i '$ a\export ANDROID_HOME="/opt/android-sdk-linux"' /etc/profile.d/android.sh RUN tar zxvf /opt/android-sdk.tgz -C /opt/ RUN apt-get update & apt-get install -y apt-transport-https RUN chown -R jenkins:jenkins /var/cache/jenkins RUN chown -R jenkins:jenkins /var/log/jenkins Here's what my Dockerfile looks like: FROM jenkinsci/jenkins:2.0-beta-1 With Google installers come license agreements, and I needed a way to reliably accept the terms and conditions of the installer and it's dependencies automatically. For a recent project, I had to include the Android SDK build tools as part of a Jenkins Dockerfile.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |