Storing build logs outside of .deb packages

[Paul Wise]

On Mon, 2020-06-01 at 11:12 +0200, Mattia Rizzolo wrote:

> I know this has been linked in multiple places, but I'll link it
> again:
>     https://bugs.launchpad.net/launchpad/+bug/1845159
> there has also been a relevant thread in debian-devel a few months
> back, spawned off the debian/.build thread started by Niels Thykier.

Here is the thread you have mentioned:

https://lists.debian.org/msgid-search/5f47b00f-50f0-98b2-776a-28ead95ad6fc@thykier.net

> I'm not quite clear what's the best way forward: I could go and
> implement whatever feels best to me in pbuilder, and then hope the
> rest of the tooling with catch up, copy my idea and adapt, but that
> feels unlikely…

Re-reading the above thread, I now think that debhelper/dpkg-dev is the
wrong layer to be implementing this and that we want it in the hooks or
config for the build system in use; launchpad, sbuild, pbuilder etc.

The reason is that it needs to be able to evolve more rapidly than the
codebases of any of the tools that the builds use, especially in
response to maintainer requests after they notice new build failures.

So, I would suggest buildd.d.o folks and launchpad folks would be the
maintainers of the rules about artefacts to preserve and that the
artefacts be published in the same place as the build logs. Probably
for Debian, DSA would need to add to the buildd puppet module a way for
the buildd admins to specify a set of globs for files to preserve.

Sorry for getting side-tracked by BYHAND stuff.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20200601/d95c334c/attachment.sig>