How to use jenkins to realize android automation

Jenkins must first configure the environment and start Jenkins to do android automation.

The specific steps are as follows:

1. Install jdk recommendation 1.6 or later, and configure environment variables.

2. Whether 2.tomcat is normal after installation and debugging.

3. Install the zip package loaded by ant and configure the environment variables after decompression.

4. Install jenkins to download the war package, name it Jenkins, and copy it to the tomcat/webapps directory.

5. Install the Android SDK, download and install it, and configure the Android_SDK_HOME environment variable after completion. This step is mainly used for android automated testing, and can be skipped if it is not executed.

After the installation is completed, start the tomcat/bin/startup.bat file (startup.sh under linux), enter localhost:8080/jenkins in the browser, and 8080 is the tomcat port to access the jenkins server.

Next, configure Jenkins:

1, JDK configuration adds JDK, and specifies JDK name and JAVA_HOME.

2. Add ANT to the ANT configuration, and specify the ANT name and ANT_HOME.

3.Maven configuration is omitted. Maven is not used in this article. Please refer to Google for specific configuration methods.

4.Subversion selects SVN with version 1.6, and checks and updates the default Subversion credential cache after successful authentication.

5. Fill in the SMTP server, default user email suffix, system administrator email address, Jenkins URL, and select Use SMTP authentication. Fill in the user name, password, SSL, SMTP port, character set (UTF-8), default content type (default) and default recipient. After configuration, you can test the e-mail.

6.Jenkins URL Configure the URL for others to access.

Finally, plug-in management.

1, Hudson subversion plug-in, Jenkins svn plug-in.

2, Android simulator plug-in, Android simulator plug-in.

3.junit attachment plug-in, JUnit test report attachment plug-in.

4. Email-ext plug-in and mail extension plug-in. As explained here, Jenkins will only send emails that fail to build by default, and you need to install this plug-in to customize different scenarios.

5. Deploy the remote publishing plug-in to the container plug-in.