Closed om26er closed 5 years ago
Sounds like a plan. I'm fine with travis or circle-ci. In fact it might be neat to have some projects using one, and some using another, just to make sure we're exercising all the options.
Would that be confusing, mixing things up though?
If admins enable Travis CI
and tell what commands need to be run, then I can send PR to close this,
If provided with an Ubuntu container on Travis, a rough set of commands would look like
apt update
apt install squashfuse git -y
snap install snapcraft
git clone https://github.com/snapcrafters/android-studio.git # tentative, should actually download the PR
cd android-studio
snapcraft
mv *.snap android-studio.snap
snap install android-studio.snap --dangerous
On the second thought, it is better to do
snapcraft enable-ci travis
Apart from making sure the snap builds, the CI process should also ensure that the sha256sum of the executable is the same as the one from upstream.
I am collecting some more scenarios and will propose something over the weekends.
Closing this as the CI is now enabled, thanks @popey
We need CI for this project. The only thing that I have currently in mind is that it will just build the snap before allowing any change to get merged.
Lets use the free Travis CI, so that we don't have any dependency on Canonical. @popey thoughts ?