<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 23/11/2016 à 18:19, Celso Providelo
a écrit :<br>
</div>
<blockquote
cite="mid:CAOBZGR07y5BcaJwMXJrfz4w-ft5UWqaCRVbhNrG-SCaRiQ3x0g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Wed, Nov 23, 2016 at 2:52 PM Leo Arias <<a
moz-do-not-send="true"
href="mailto:leo.arias@canonical.com">leo.arias@canonical.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr" class="gmail_msg">Hello,
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">I know a bunch of people here use
quassel. There's a new snap for you:</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">$ sudo snap install
quassel-webserver --edge</div>
<div class="gmail_msg">$ sensible-browser <a
moz-do-not-send="true" href="https://localhost:64443"
class="gmail_msg" target="_blank">https://localhost:64443</a></div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">The main developer, Joël Charles,
has been amazing. For a couple of weeks we have been
experimenting with his project. First, we had to solve
an issue with the less-middleware module because it
wanted to use the install directory instead of SNAP_DATA
[1], then we got travis to build the snap on every PR
[2], and finally he agreed to beta test the new
enable-ci command of snapcraft that Celso is working on.</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">When I asked about feedback or
feature requests, he said: "Not that I think of, it just
went very smoothly" :_)</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Of course, a few seconds later
travis broke and we found a bug in Celso's PR, just to
keep us grounded. It was a quick fix, and now every
change on master will build and push the snap to edge
[3].</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">I really want to thank Joël because
we now have a set of scripts tested in real live, that
we can just apply to new projects. Also Celso because
without the enable-ci command, this would never have
been a smooth experience.</div>
<div class="gmail_msg"><br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Amazing work Leo! Thanks for jumping in so quickly (it's
not even landed in master) and experimenting with this
feature in real circumstances.</div>
<div><br>
</div>
<div>Until it lands and 2.23 gets SRU-ed in xenial we have to
cope with the lack of support for local store credentials
(`.snapcraft.cfg`). There are other less-intrusive
alternatives like [1], but once the transition is gone
`enable-ci` will do the right thing for the majority of
projects (simple ones).</div>
<div><br>
</div>
<div>We hope this initiative along with <a
moz-do-not-send="true" href="http://build.snapcraft.io">build.snapcraft.io</a>
(down the road) will considerably increase the number of
revisions released in edge, like we already see for core and
lxd. That's why we are also working on metrics to capture
how developers are pushing/releasing their snaps (webui,
snapcraft, travis, LP, etc). It will be nice to observe
these trending as we offer easier ways to do CI with snaps.</div>
<div><br>
</div>
</div>
</div>
</blockquote>
Great work guys!<br>
<br>
It would be nice of you guys to blog about your experience for
integrating CI from master and push to the store on a edge channel
as a step by step recipe. Maybe something worth posting on
<a class="moz-txt-link-freetext" href="https://insights.ubuntu.com">https://insights.ubuntu.com</a>?<br>
<br>
Cheers,<br>
Didier
</body>
</html>