Tutorial: Continuous delivery of snaps with Circle CI

David Callé

David Callé

on 19 January 2018

Bullet-proof continuous delivery of software is crucial to the health of your community, more than a way to run manual tests, it also enables your early adopters to test code and give feedback on it as soon as it lands. You may be already using build.snapcraft.io to do so for snaps, but in some cases, your existing tooling needs to prevail.

Enabling Circle CI for snaps

In this tutorial, you will learn how to use Circle CI to build a snap and push it automatically to the edge channel of the Snap Store every time you make a change to your master branch in GitHub.

What you’ll learn

  • How to build your snap in Circle CI
  • How to push your snap to the store automatically from Circle CI
  • How to use snapcraft to enable all this, with a few simple commands

Take The Tutorial

Ubuntu desktop

Learn how the Ubuntu desktop operating system powers millions of PCs and laptops around the world.

Newsletter signup

Select topics you’re interested in

In submitting this form, I confirm that I have read and agree to Canonical’s Privacy Notice and Privacy Policy.

Related posts

Open infrastructure, developer desktop and IoT are the focus for Ubuntu 19.04

18th April, 2019: Canonical today announced the release of Ubuntu 19.04, focused on open infrastructure deployments, the developer desktop, IoT, and cloud to edge software distribution. “The open-source-first on Ubuntu movement in telco,…

Industrial & Embedded Linux: Looking Ahead

I recently returned from an extended visit to Germany, where my colleagues and I kept busy attending conferences, visiting customers and partners. We travelled around the country, talking to many, many people at dozens of companies about…

Why the Visual Studio Code team launched a snap

Microsoft’s Visual Studio Code is a popular free code editor with built-in support for debugging, task running, and version control. While available for Linux via tarball, rpm, and debian package options, the Visual Studio Code team had…