<div dir="ltr">I have spent the last two weeks on a different approach to our CI setup, published the current version of the tools just now and added a document to our website (not linked from the main page yet until I have some feedback).<div><br></div><div>Please have a look at <a href="https://pkg-go.alioth.debian.org/ci.html">https://pkg-go.alioth.debian.org/ci.html</a>, especially the first section (motivation/goals) and the last section (implications/caveats).</div><div><br></div><div>tl;dr: the new approach allows for rebuilding the entire archive (!) in about 1 minute (!) (longer for changes triggering rebuilds/tests of more/more expensive packages, of course), but will require a few changes in a small handful of our packages.</div><div><br></div><div>Curious to hear your thoughts,</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 30, 2018 at 6:05 PM, Michael Stapelberg <span dir="ltr"><<a href="mailto:stapelberg@debian.org" target="_blank">stapelberg@debian.org</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">Status update: I now ran ci.go, i.e. all of our repositories should now be configured.<div><br></div><div>The next step is to bulk-commit debian/gitlab-ci.yml. I’ll let you know more details once I start working on that.</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Tue, Jan 30, 2018 at 2:38 PM, Michael Stapelberg <span dir="ltr"><<a href="mailto:stapelberg@debian.org" target="_blank">stapelberg@debian.org</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>On Tue, Jan 30, 2018 at 2:17 AM, Alexandre Viau <span dir="ltr"><<a href="mailto:aviau@debian.org" target="_blank">aviau@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is great! Good job.<br></blockquote><div><br></div></span><div>Thanks for the feedback :)</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span><br>
> Aside from the GitLab-side, we also need a .gitlab-ci.yml file<br>
> in the repository itself. I can bulk-commit these, along with<br>
> adding them to Files-Excluded in debian/copyright so that<br>
> upstream copies are discarded.<br>
<br>
</span>Please do. (it looks like the d/copyright thing won't be needed if you<br>
can change the path to debian/gitlab-ci)<br></blockquote><div><br></div></span><div>Indeed.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span><br>
> I suggest setting this path to “debian/gitlab-ci.yml” for our<br>
> repositories, so that we don’t need to mangle upstream’s<br>
> .gitlab-ci.yml and have all relevant files within the debian/<br>
<br>
</span>+1<br>
<span><br>
On 2018-01-28 09:35 AM, Michael Stapelberg wrote:<br>
> On Sat, Jan 27, 2018 at 11:21 PM, Michael Stapelberg<br>
</span><span>> <<a href="mailto:stapelberg@debian.org" target="_blank">stapelberg@debian.org</a> <mailto:<a href="mailto:stapelberg@debian.org" target="_blank">stapelberg@debian.org</a>><wbr>> wrote:<br>
> With this feature place, the next step I’d like to implement is<br>
> a speculative package auto-updater: upon noticing the Debian and<br>
> upstream version have diverged, we could import the new version,<br>
> send a Merge Request, have the CI check for breakages and<br>
> (manually) merge and upload if no breakages are introduced.<br>
<br>
<br>
</span>That would be great.<br>
<br>
Did you see the recent devscripts commit? #811565[1] was marked as pending.<br></blockquote><div><br></div></span><div>I saw it, but thanks for the pointer :)</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
We will be ale to use uscan to watch for new upstream versions. The tool<br>
you are building could make use of this.<br>
<br>
<br>
Maybe you want to contribute to this script:<br>
-<br>
<a href="https://salsa.debian.org/pkg-go-team/migrate-pkg-go-to-salsa/blob/master/configure-all-projects.py" rel="noreferrer" target="_blank">https://salsa.debian.org/pkg-g<wbr>o-team/migrate-pkg-go-to-salsa<wbr>/blob/master/configure-all-pro<wbr>jects.py</a><br>
<br>
It protects branches and create webhooks on all repositories in the<br>
"packages" subgroup on salsa. We should add the debian/gitlab-ci.yml<br>
config too so that we can just run the script and have all salsa<br>
projects configured uniformly.<br></blockquote><div><br></div></span><div>The ci tool which I linked to also applies to all repositories. We should definitely join forces here. I’d prefer tooling to be written in Go, because I’m much more familiar with it. Would you be okay with merging configure-all-projects.py into ci.go? I’d be happy to review. If you don’t have the time, I could also contribute the necessary changes.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
By the way, don't forget to update dh-make-golang too, so that new<br>
repositories have the setting.<br></blockquote><div><br></div></span><div>Will do. I wanted to update it to be consistent with ci.go anyway.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
1. <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811565" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bi<wbr>n/bugreport.cgi?bug=811565</a><br>
<br>
<br>
Cheers,<br>
<span class="m_-6843365457071976161m_3682151227293821174HOEnZb"><font color="#888888"><br>
--<br>
Alexandre Viau<br>
<a href="mailto:aviau@debian.org" target="_blank">aviau@debian.org</a><br>
<br>
</font></span></blockquote></span></div><span class="m_-6843365457071976161HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div class="m_-6843365457071976161m_3682151227293821174gmail_signature" data-smartmail="gmail_signature">Best regards,<br>Michael</div>
</font></span></div></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_-6843365457071976161gmail_signature" data-smartmail="gmail_signature">Best regards,<br>Michael</div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Best regards,<br>Michael</div>
</div>