subsurface/scripts/android/after_success.sh

#!/bin/bash

if [ ! -z $TRAVIS_BRANCH ] && [ "$TRAVIS_BRANCH" != "master" ] ; then
	export UPLOADTOOL_SUFFIX=$TRAVIS_BRANCH
fi

# set up the release message to use
source ${TRAVIS_BUILD_DIR}/scripts/release-message.sh

echo "Submitting the folloing apk for continuous build release:"
ls -lh $TRAVIS_BUILD_DIR/apk/*.apk

# get and run the upload script
wget -c https://github.com/probonopd/uploadtool/raw/master/upload.sh
bash ./upload.sh $TRAVIS_BUILD_DIR/apk/*.apk
android: Add android build on travis-ci This adds a android-apk-build which runs on travis-ci. This is using a quite ugly trick, building in a docker container, basically just to get a newer cmake. The cmake in trusty is way to old to work with android builds. A good side-effect is that this is a complete copy-paste for anyone who would like to build android-binaries them self on Linux. All the uglyness is hidden away in a docker container. Signed-off-by: Anton Lundin <glance@acc.umu.se> 2017-02-06 07:06:55 +00:00			`#!/bin/bash`

			`if [ ! -z $TRAVIS_BRANCH ] && [ "$TRAVIS_BRANCH" != "master" ] ; then`
			`export UPLOADTOOL_SUFFIX=$TRAVIS_BRANCH`
			`fi`

Travis: setup up the desired release message right away Instead of using the default release message and then trying to fix it up in the after_success section of one of the builds that we test, let's just always use the message that we want, regardless which build finishes first. This currently requires my fork of the uploadtool - the changes have been submitted upstream and I hope they'll get merged there so we can switch back to the upstream version of uploadtool. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-11-18 00:40:35 +00:00			`# set up the release message to use`
			`source ${TRAVIS_BUILD_DIR}/scripts/release-message.sh`

android: Add android build on travis-ci This adds a android-apk-build which runs on travis-ci. This is using a quite ugly trick, building in a docker container, basically just to get a newer cmake. The cmake in trusty is way to old to work with android builds. A good side-effect is that this is a complete copy-paste for anyone who would like to build android-binaries them self on Linux. All the uglyness is hidden away in a docker container. Signed-off-by: Anton Lundin <glance@acc.umu.se> 2017-02-06 07:06:55 +00:00			`echo "Submitting the folloing apk for continuous build release:"`
			`ls -lh $TRAVIS_BUILD_DIR/apk/*.apk`

			`# get and run the upload script`
Switch back to upstream uploadtool In commit e643589233 ("Travis: setup up the desired release message right away") we temproarily switched to my fork of uploadtool to take advantage of a new feature that I had implemented there. This has already been merged upstream, so let's switch back to upstream. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-11-18 16:05:50 +00:00			`wget -c https://github.com/probonopd/uploadtool/raw/master/upload.sh`
android: Add android build on travis-ci This adds a android-apk-build which runs on travis-ci. This is using a quite ugly trick, building in a docker container, basically just to get a newer cmake. The cmake in trusty is way to old to work with android builds. A good side-effect is that this is a complete copy-paste for anyone who would like to build android-binaries them self on Linux. All the uglyness is hidden away in a docker container. Signed-off-by: Anton Lundin <glance@acc.umu.se> 2017-02-06 07:06:55 +00:00			`bash ./upload.sh $TRAVIS_BUILD_DIR/apk/*.apk`