Jenkins + git + gradle-based android continuous integration, jenkinsgradle

Jenkins + git + gradle-based android continuous integration, jenkinsgradle

This article references:

Http://my.oschina.net/uboluo/blog/157483

Http://java.dzone.com/articles/automating-continuous

 

Previously, the apk was manually generated using IDE (eclipse or Android Studio) and sent to the tester via QQ or email for testing. The current Division requires continuous integration of the project, that is to say, the latest code pull in the git library is automatically compiled and packaged at a scheduled time (for example, three o'clock every night). The tester can get the latest code package Apk every morning. Various duniang Google is a little eye-catching, record it, lest you forget

Software environment:

1. 64-bit Windows 7;

2. jdk1.7

3. android sdk

4. gradle2.2.1

Set the environment variable.

Step 1: Download jenkins.Link: http://mirrors.jenkins-ci.org/war/latest/jenkins.war.

Place the downloaded jenkins. war package to the webapps directory under tomcat, start tomcat, and enter 127.0.0.1: 8080/Jenkins in the browser.

Step 2: Go to settings, manage ins, and add git, gradle, and lint

Step 3: System Configuration

Step 4: create new job

Step 5: build

Step 6: detection results

After the Build, check if: C: \ Users \ Administrator \. jenkins \ jobs \ AutoCI \ workspace \ app \ build \ outputs \ apk \

If an Apk similar to the following is generated under the directory, the system is OK.

I am currently deploying this on my own development machine. I should deploy it on the server, and use scripts to move the generated apk to the specified directory, the tester goes down to this directory every day to obtain the latest apk, because he does not have the server operation permission and cannot write this part.

Full text