This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
build:jenkins [2018/10/18 23:42] mjallison [Web Application Builds] |
build:jenkins [2018/10/25 17:50] (current) mjallison [Web Application Builds] |
||
---|---|---|---|
Line 33: | Line 33: | ||
(manually) to /var/www/html/build/SmartDirt (btw: historical reasons for the name, nothing fancy). | (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. | Old release copies should then be copied to /var/www/html/build/SmartDirt/old. | ||
+ | |||
+ | Building an Android app for release on the Play store takes a couple of more steps. Each play store | ||
+ | version is identified by an integer (variously called a "build number" or "release number"). This integer | ||
+ | is only loosely related to the versions string (e.g. 1.5.2) in that the build number must always be larger | ||
+ | than the previously release. | ||
+ | |||
+ | These release numbers are constants defined inside the Manifest (example from TrackManager, release == 11): | ||
+ | |||
+ | ''<manifest xmlns:android="http://schemas.android.com/apk/res/android"\\ | ||
+ | package="com.agtek.trackmanager"\\ | ||
+ | android:versionCode="11"\\ | ||
+ | android:versionName="1.4.1" >\\ | ||
+ | |||
+ | '' | ||
====== Server Builds ====== | ====== Server Builds ====== | ||
Line 61: | Line 75: | ||
''ssh -P 23456 build@dev.agtek.com\\ | ''ssh -P 23456 build@dev.agtek.com\\ | ||
# after completing the log-in\\ | # after completing the log-in\\ | ||
- | snap\\ | + | wsnap\\ |
''\\ | ''\\ | ||