Riga Dev Day - Automated Android Continuous Integration
Download as PPTX, PDF1 like12,734 views
This document discusses setting up continuous integration for Android projects. It describes issues with dependencies like Gradle and Robolectric not working properly due to proxy restrictions. It proposes solutions like using a local Maven repository, configuring Gradle properties, and creating a custom Robolectric test runner and dependency resolver. It also addresses problems updating the Android SDK due to needing proxy authentication and license agreements. An Expect script is created to automate providing the credentials and agreeing to licenses during the SDK update process.
![ANDROID SDK --HELP
Action "update sdk":
Updates the SDK by suggesting new platforms to install if available.
Options:
-f --force : Forces replacement of a package or its parts, even if
something has been modified.
-n --dry-mode : Simulates the update but does not download or install
anything.
--proxy-host: HTTP/HTTPS proxy host (overrides settings if defined)
-s --no-https : Uses HTTP instead of HTTPS (the default) for downloads.
-t --filter : A filter that limits the update to the specified types of
packages in the form of a comma-separated list of
[platform, system-image, tool, platform-tool, doc, sample,
source]. This also accepts the identifiers returned by
'list sdk --extended'.
-u --no-ui : Updates from command-line (does not display the GUI)
--proxy-port: HTTP/HTTPS proxy port (overrides settings if defined)
-p --obsolete : Deprecated. Please use --all instead.
-a --all : Includes all packages (such as obsolete and non-dependent
ones.)](https://image.slidesharecdn.com/rigadevday-automatedandroidci-160303064948/85/Riga-Dev-Day-Automated-Android-Continuous-Integration-40-320.jpg)
![THE “REAL” SCRIPT
#!/bin/bash
expect -d -c '
log_file /var/log/update-android.log
set timeout -1
spawn <%= @android_sdk_dir %>/tools/android -v update sdk -a -u -f --proxy-host
<%= @proxy_host %> --proxy-port <%= @proxy_port %> -t <%= @joined_packages %>
while {1} {
expect {
"Login:" {
send "<%= @proxy_user %>r"
}
"Password:" {
send "<%= @proxy_password %>r"
}
"Workstation:" {
send "r"
}
"Domain:" {
send "r"
}
-re ".*[y/n]:" {
send "yr"
}
}
}'
Handles the proxy
Handles license agreements](https://image.slidesharecdn.com/rigadevday-automatedandroidci-160303064948/85/Riga-Dev-Day-Automated-Android-Continuous-Integration-45-320.jpg)
More Related Content
Similar to Riga Dev Day - Automated Android Continuous Integration (20)
More from Nicolas Fränkel (20)
Riga Dev Day - Automated Android Continuous Integration
- 1. AUTOMATED ANDROID CONTINUOUS INTEGRATION: HOW HARD CAN IT BE? @NICOLAS_FRANKEL
- 2. ME, MYSELF AND I @nicolas_frankel #springboot 2 Backend Java Developer • As consultant
- 3. HYBRIS, AN SAP COMPANY 3 @nicolas_frankel #springboot
- 4. THE EXISTING ORGANIZATION Software Factory Mobile Dev Team
- 5. THE REAL ORGANIZATION Software Factory Mobile Dev Team
- 9. JENKINS JOB CONFIGURATION No central registry • Stored in XML • In each job’s folder
- 10. WHAT WE DID Analyzed the config of an existing job Divided it into snippets Created Puppet template for each Assembled and filled in snippets through classes
- 11. WHAT WE DID Creation of a Jenkins DSL in Puppet
- 12. WHY FAIL? Time-consuming Error-prone Fragile • Implementation details Reinventing the wheel
- 13. ALTERNATIVES Jenkins Job Builder • Part of OpenStack • DSL that calls Jenkins API • YAML configuration
- 15. DEPENDENCIES
- 16. THE CHALLENGE
- 17. ISSUES 1. Gradle Wrapper 2. Robolectric 3. Android platforms/extra/add-ons
- 20. GRADLE WRAPPER Made of: • A JAR • A property Downloads the required version from the Internet
- 22. THE ROOT ISSUE The proxy…
- 27. AN ERROR!? Error:Could not HEAD 'http://repo1.maven.org/maven2/org/robolectr ic/robolectric-gradle- plugin/0.12.0/robolectric-gradle-plugin- 0.12.0.jar'. Received status code 407 from server: AuthorizedOnly
- 30. Y U ROBOLECTRIC? public class RobolectricTestRunner { protected DependencyResolver getJarResolver() { if (dependencyResolver == null) { if (Boolean.getBoolean("robolectric.offline")) { String dependencyDir = System.getProperty( "robolectric.dependency.dir", "."); dependencyResolver = new LocalDependencyResolver( new File(dependencyDir)); } else { File cacheDir = new File(new File( System.getProperty("java.io.tmpdir")), "robolectric"); if (cacheDir.exists() || cacheDir.mkdir()) { Logger.info( "Dependency cache location: %s", cacheDir.getAbsolutePath()); dependencyResolver = new CachedDependencyResolver( new MavenDependencyResolver(), cacheDir, 60 * 60 * 24 * 1000); } else { dependencyResolver = new MavenDependencyResolver(); } } } }
- 31. Y U ROBOLECTRIC? <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.robolectric</groupId> <artifactId>robolectric-parent</artifactId> <version>3.1-SNAPSHOT</version> </parent> <artifactId>robolectric</artifactId> <dependencies> ... <dependency> <groupId>org.apache.maven</groupId> <artifactId>maven-ant-tasks</artifactId> <version>2.1.3</version> <exclusions> <exclusion> <groupId>*</groupId> <artifactId>*</artifactId> </exclusion> </exclusions> </dependency> </dependencies> </project>
- 32. Y U ROBOLECTRIC? “Robolectric downloads a version of Android at runtime that's built specifically for running tests. Each API level is ~40mb, so producing a single jar file that includes everything would be prohibitive. All of the artifacts are available on maven central under the coordinates: org.robolectric:android-all. You can grab the API levels from maven central and use them with offline mode.” https://groups.google.com/forum/#!topic/robolectric/nJgHt dbkpi8
- 33. Y U ROBOLECTRIC? Uses a custom class loader Either: • Download dependencies beforehand • Override method • Pass through proxy
- 34. YOUR OWN TEST RUNNER @Override protected DependencyResolver getJarResolver() { if (this.dependencyResolver == null) { if (Boolean.getBoolean("robolectric.offline")) { String cacheDir = System.getProperty( "robolectric.dependency.dir", "."); this.dependencyResolver = new LocalDependencyResolver( new File(cacheDir)); } else { this.dependencyResolver = new MyResolver(); } } return this.dependencyResolver; }
- 35. YOUR OWN RESOLVER public class MyResolver extends MavenDependencyResolver { @Override protected void configureMaven( DependenciesTask task) { RemoteRepository remoteRepository = new RemoteRepository(); remoteRepository.setId("My Maven repo"); remoteRepository.setUrl(BuildConfig.NEXUS_URL); task.addConfiguredRemoteRepository( remoteRepository); } }
- 37. ANDROID SDK ISSUE android update sdk
- 38. ANDROID SDK ISSUE android update sdk -u Non interactive mode
- 39. 2 ISSUES Set the proxy Accept license agreements
- 40. ANDROID SDK --HELP Action "update sdk": Updates the SDK by suggesting new platforms to install if available. Options: -f --force : Forces replacement of a package or its parts, even if something has been modified. -n --dry-mode : Simulates the update but does not download or install anything. --proxy-host: HTTP/HTTPS proxy host (overrides settings if defined) -s --no-https : Uses HTTP instead of HTTPS (the default) for downloads. -t --filter : A filter that limits the update to the specified types of packages in the form of a comma-separated list of [platform, system-image, tool, platform-tool, doc, sample, source]. This also accepts the identifiers returned by 'list sdk --extended'. -u --no-ui : Updates from command-line (does not display the GUI) --proxy-port: HTTP/HTTPS proxy port (overrides settings if defined) -p --obsolete : Deprecated. Please use --all instead. -a --all : Includes all packages (such as obsolete and non-dependent ones.)
- 41. WTF?!!? Accepts proxy parameters But no authentication…
- 42. SOLUTIONS (THANKS GOOGLE FOR NOTHING) Environments variables Specific credential file Local proxy
- 43. A WORKING SOLUTION: EXPECT Linux binary Originally for testing purpose Script input in regard to output
- 44. (VERY) SIMPLE EXPECT SCRIPT #!/usr/bin/expect eval spawn jot -r 1 0 1 expect { "0" { puts "zero" } "1" { puts "one" } }
- 45. THE “REAL” SCRIPT #!/bin/bash expect -d -c ' log_file /var/log/update-android.log set timeout -1 spawn <%= @android_sdk_dir %>/tools/android -v update sdk -a -u -f --proxy-host <%= @proxy_host %> --proxy-port <%= @proxy_port %> -t <%= @joined_packages %> while {1} { expect { "Login:" { send "<%= @proxy_user %>r" } "Password:" { send "<%= @proxy_password %>r" } "Workstation:" { send "r" } "Domain:" { send "r" } -re ".*[y/n]:" { send "yr" } } }' Handles the proxy Handles license agreements
- 46. ANDROID SDK ISSUE android update sdk -u
- 47. ANDROID CONTINUOUS INTEGRATION? Not mature • Lags behind “standard” Java So time-consuming… • But possible!