Reprint: http://www.android100.org/html/201506/22/156680.html
Jenkins+git+gradle-based Android continuous integration, Jenkinsgradle
This article refers to the following:
http://my.oschina.net/uboluo/blog/157483
Http://java.dzone.com/articles/automating-continuous
Previously, the APK was manually generated via the IDE (Eclipse or Android Studio) and sent to testers via QQ or email, and now the Division requires continuous integration of the project, that is, in some way timed (e.g. three o'clock in the morning per night) Automatically pull down the latest code from the Git library to compile and package, and testers get the latest code-packed apk for work every morning. All kinds of degrees Niang Google is to make a point, record a bit, lest forget
Software Environment:
1, Windows7 64bit;
2, jdk1.7
3. Android SDK
4, gradle2.2.1
Setting up environment variables is a cinch.
The first step is to download Jenkins. Link: Http://mirrors.jenkins-ci.org/war/latest/jenkins.war.
Put the downloaded Jenkins.war package directly into the WebApps directory under Tomcat, launch Tomcat, enter in the browser: 127.0.0.1:8080/jenkins
Step two, go to settings, manage plugins, add Git,gradle,lint
Step Three: System configuration
Fourth step: Create New Job
Fifth Step: Build
Sixth step: Test results
After the build is checked, if: C:\Users\Administrator\.jenkins\jobs\AutoCI\workspace\app\build\outputs\apk\
An apk similar to the following is generated in the directory, indicating that the system is OK
I have this temporary deployment on my own development machine, supposedly should be deployed to the server, with a script will be generated by the APK move to the specified directory, the tester to the directory every day to get the latest apk, because there is no server operation permissions, this part is not able to write.
End of full text
Jenkins+git+gradle-based Android continuous integration, Jenkinsgradle