We do anticipate being able to send a message to devices that want to know when a new version of a snap is available in a particular channel. We call it 'real-time refresh' because it would enable the subscribing devices to refresh themselves the instant a new version of the snap was released.
In this case, what's interesting is that you want to KNOW that the new version is released, but then drive a process which is not simplistically "refresh this device". Still, the message could serve as the trigger - you have a device which is getting these real-time notifications, and you hook into the event to then trigger your test suites. Essentially, you would have a canary device which gets the real-time refresh, and then triggers your test suites. I think it's appropriate that we have an interface to snapd which is a stream of events, like "I just refreshed this snap". You could tap that stream for the new snap notice, and then trigger your test suites. Mark On 17/02/17 03:20, Manik Taneja wrote: > > > On Thu, Feb 16, 2017 at 12:15 PM, Max Brustkern > <max.brustk...@canonical.com <mailto:max.brustk...@canonical.com>> wrote: > > > > On Thu, Feb 16, 2017 at 9:55 AM, Michael Vogt > <michael.v...@canonical.com <mailto:michael.v...@canonical.com>> > wrote: > > Hello, > > The Snappy team is happy to announce the promotion of snapd 2.22.2 > from the candidate channel to stable in both the "core" and > "ubuntu-core" snaps. It will also be available via the regular apt > update mechanism in Ubuntu 14.04, 16.04 and 16.10. Other > distributions > will follow on their own schedule. > > > I'd like to trigger tests to run when new core snaps are available > in the stable and candidate channels. What's the best way to check > that? > > i suspect that you will like to run tests after installing a newer rev > of a snap from the candidate/stable channels. at the moment, i believe > your > best option is to poll the store for a newer revision. once available, > update the device explicitly using snap refresh <snap-name> and than > run whatever tests you like. if its a snap that you published > yourself, you could run hooks on install automatically that can > trigger whatever tests you like. > moving forward, we will need to work on a better approach via > push-notifications (perhaps) that will tell a device about a new > revision and also allow > the capability to install it immediately, instead of waiting for the > next update-timer to kick in. > > /manik > >
-- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
