subsurface.git/scripts/linux, branch v4.8.0

Travis: don't fail Linux build when .zsync is missing

2018-05-20T18:35:28Z

It seems that sometimes the AppImage tooling gets confused and doesn't create a .zsync file. That should cause Travis to fail. Signed-off-by: Dirk Hohndel

Travis: add secondary Linux build target

2018-05-20T04:21:46Z

The goal is to reduce the overall wall clock time of our test builds. This secondary Linux target uses the no-sudo container setup with a Qt 5.10.1 backport and tests the build without BT support as well as the mobile build (but not the full desktop build and doesn't create an AppImage as the pre-built Qt5.10.1 is missing QtWebKit). In exchange we remove the no-bt and mobile build from the existing linux target. Signed-off-by: Dirk Hohndel

smtk-import: Upload .AppImage and .exe files

2018-02-24T21:42:01Z

Upload windows installer and AppImage to Subsurface's repo Signed-off-by: Salvador Cuñat

smtk-import: Add an AppImage for smtk2ssrf

2018-02-24T21:42:01Z

Build an AppImage for smtk2ssrf using previously build binaries. Signed-off-by: Salvador Cuñat

smtk-import: Support SmartTrak import in travis builds

2018-02-24T21:42:01Z

1.- Include needed dependencies (glib-2.0 and mdbtools) in .travis.yml 2.- Call smtk2ssrf-build.sh script *after* subsurface is done and AppImage is built, as the script will override subsurface's binary. Signed-off-by: Salvador Cuñat

Use our fork of uploadtool

2017-12-30T19:10:40Z

And use the 'correct' URL to obtain the actual file. Signed-off-by: Dirk Hohndel

Travis: no longer test Subsurface-mobile without BT

2017-12-06T03:29:59Z

Signed-off-by: Dirk Hohndel

Travis: try to make sure failing builds fail

2017-11-25T00:58:55Z

In some situations Travis CI doesn't seem to notice that a build failed and give us a green check mark even though the build didn't succeed. Signed-off-by: Dirk Hohndel

Switch back to upstream uploadtool

2017-11-18T16:05:50Z

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

Travis: setup up the desired release message right away

2017-11-18T15:17:40Z

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