solvespace/.travis/build-snap.sh

#!/bin/sh -xe

sudo apt-get update
sudo ./pkg/snap/build.sh --destructive-mode
snap: build snaps on Travis via remote-build. We invoke builds on Launchpad in stage "deploy" and release it into the edge channel of the Snap Store. The deploy stage is blocked on fails of the test stage, so we don't release snaps with failing tests. 2019-11-23 20:45:32 +00:00			`#!/bin/sh -xe`

snap: Build snaps on Travis without remote-build & drop i386 + armhf Snapcraft's remote-build does not fit the requirements of CI, so replace it with builds running directly on Travis: 1. Builds on Travis can run independently, whereas remote-build competes for the same resource (Launchpad) and will potentially block if multiple commits require building in succession. 2. Snapcrafts CLI for remote-build is not designed to be easily scriptable. 3. Travis recently introduced building on arm64, so builds for arm64 are now very fast and don't require emulation. We do not build for armhf and i386 any more because they are of little relevance on the desktop. 2020-02-08 14:42:01 +00:00			`sudo apt-get update`
			`sudo ./pkg/snap/build.sh --destructive-mode`