<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Mark<br>
<br>
On 17/02/17 03:20, Manik Taneja wrote:<br>
</div>
<blockquote
cite="mid:CAEQrNmvk6H-gFsUQa9vGZDfkmRH1=NiAQukjg+dpRv1KrRsG2g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Feb 16, 2017 at 12:15 PM, Max
Brustkern <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:max.brustkern@canonical.com"
target="_blank">max.brustkern@canonical.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">On Thu, Feb
16, 2017 at 9:55 AM, Michael Vogt <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:michael.vogt@canonical.com"
target="_blank">michael.vogt@canonical.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">Hello,<br>
<br>
The Snappy team is happy to announce the
promotion of snapd 2.22.2<br>
from the candidate channel to stable in both the
"core" and<br>
"ubuntu-core" snaps. It will also be available
via the regular apt<br>
update mechanism in Ubuntu 14.04, 16.04 and
16.10. Other distributions<br>
will follow on their own schedule.<br>
<br>
</blockquote>
<div><br>
</div>
</span>
<div>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?<br>
</div>
</div>
</div>
</div>
</blockquote>
<div>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<br>
</div>
<div>best option is to poll the store for a newer revision.
once available, update the device explicitly using snap
refresh <snap-name> and than<br>
</div>
<div>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.
<br>
</div>
<div>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<br>
</div>
<div>the capability to install it immediately, instead of
waiting for the next update-timer to kick in.<br>
<br>
</div>
<div>/manik<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>