CI snapcraft installation

[dawidd6]

No description provided.

[codecov-io]

Codecov Report

Merging #96 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #96   +/-   ##
=======================================
  Coverage   23.61%   23.61%           
=======================================
  Files          13       13           
  Lines        1080     1080           
=======================================
  Hits          255      255           
  Misses        813      813           
  Partials       12       12

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 88dca3f...f84c36c. Read the comment docs.

[dawidd6]

Should work, tested it in Docker on image that is used by CI.

# testing procedure in Docker container based on circleci/golang:1.12 image
# while being in lazydocker source code dir
./.circleci/install_snapcraft.sh
curl -sL https://git.io/goreleaser | bash -s -- --skip-publish --snapshot --rm-dist --skip-sign

Installation is a bit hacky from different sources, but the only official method of installing snapcraft is doing it via snap and to be able to use snap, one has to have snapd daemon running, which is problematic in Docker containers. We could use snapcore/snapcraft Docker image for whole CI process, but then we would need to install go every time CI is fired up and installing snapcraft happens only when there is a new release.

[jesseduffield]

tested and it works :)

I would like this to be baked into its own image but as you said this will only happen on release which will be infrequent so it should be fine.

Merge away :)

[dawidd6]

Hmm. We can always make our own image and push it to Docker Hub with everything needed already in it. Or try to contribute to goreleaser directly by adding snapcraft to their Dockerfile.

But for now this solution may be enough.