This is an old revision of the document!
Table of Contents
Introduction
The Jenkins build system is installed on dev.agtek.com. It's a Java application running within the Tomcat application environment. The build system for Agtek will perform continuous integration builds for Android components, as follows:
- AGTEKBaseSetup
- SimpleTrack
- SmartBlade
- SmartDirt
- SmartGrade
- SmartPlan
- SmartTrack
and Server components as follows:
- AgtekNet (the Access server itself)
- AccesWeb (the web application)
Jenkins will kick off a build (usually within 15 minutes, configuration time) when new code is checked into the associated repository.
Android Builds
Each Android project will checkout two repositories; AGTEK_Lib and the associate application repository. A script, AGTEK_Lib/jenkins.sh, does the heavy lifting of running the build for each part of the application. For most part, jenkins.sh will set build numbers (from Jenkins itself), and runs the Android “assemble” task. The build fails if no APK is produced.
Once the build succeeds, the corresponding APK and mapping file are copied to /var/www/html/build/SmartSuite-nightly.
When the product has been tested and is accepted for distribution, the APK and mapping files are copied (manually) to /var/www/html/build/SmartDirt (btw: historical reasons for the name, nothing fancy). Old release copies should then be copied to /var/www/html/build/SmartDirt/old.
Server Builds
