search

MovingBlocks / DestinationSol

Official continuation of Destination Sol, the great fun little arcade space shooter from http://sourceforge.net/projects/destinationsol/ Modules live at https://github.com/DestinationSol/
Apache License 2.0
330 stars 122 forks source link

Set up Android build in Jenkins #45

Open Cervator opened 9 years ago

Cervator commented 9 years ago

Got the Gradle in place but I expect it'll take some effort both to prepare the Android SDK setup as well as finding a nice way to actually run the build without a multi-project workspace.

Terasology builds the applet (also a separated out "facade") by copying in a set of files from the main (engine) build in Jenkins then fetching other dependencies via Artifactory. Likewise for modules.

We'll need to make / update a gradle.properties for the Jenkins server to hold keystore info

Some related doc: http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Tasks

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Cervator commented 8 years ago

Future note: the v2.0.0 branch tweaks the gradle.properties for way increased memory settings, and the Jack compiler for Java 8 on Android sure puts it to use as well. Peak usage hit the full 4 GB and the process didn't exit cleanly locally either. Without the increased memory the compilation can appear to hang but as per other users just can take forever (as much as 30 minutes or worse)

While that's in theory only needed for the Android build the gradle.properties is at present in this repo. More notes in #92.

Also still need to move some of the docs around like taking the Android build instructions from docs here and moving it to the Android repo. There's also a Steam instructions thread in the forum we should perhaps put in docs here or in a Steam facade repo as we add more Steam stuff (achievements?)

BenjaminAmos commented 3 years ago

Debug engine builds have been built on Jenkins since https://github.com/MovingBlocks/DestinationSol/commit/ca0dc74c9d4ed2a3bd8c1f0fa0013c66c917ff2a, so this issue is partially fixed. Release builds are not handled though and neither are builds with non-core modules.