Hello people,

just now at DebConf we had a small BOF to discuss this problem, that has
several times come up.

Lastly I think https://lists.debian.org/debian-devel/2022/02/msg00216.html
to which Simon had a quite nice answer.


This is what we came up with:
https://wiki.debian.org/BuildArtifacts#Design_proposal

I'm copying it here for reference:

 * decide on a directory name (`./debian/export_artifacts/`?)
 * the build process will dump any files that could be interesting to
   export in there (no decision if/how to define the structure within
   this directory)
   * potentially, all `dh_*` could copy there whatever is relevant to
     them (i.e., `dh_auto_configure` could export configure logs,
     `dh_auto_test` the various test logs, ..)
 * the containering tool (sbuild, pbuilder, ...) at the end of the
   build, regardless of the result of the build:
   * check if the directory exists, and it's non-empty
   * if true, tar it up
   * place the tar'ed-up artifacts in the usual results directory, with
     a predictive name (`$srcpkg_$ver_$arch.artifacts.tar.xz`?)
   * tbd if this should happen always or opt-in by the build caller
 * `buildd`/`pybuildd` will check if such file has been exported, if it
    is, then it will be uploaded to some service
   * something as simple as an authenticate HTTP POST somewhere will
     do - no strong auth needed (right?)
 * this new service will simply just accept whatever upload and store it
 * possibly define an expiry rule for these artifacts to not hog all
   space needlessly


Matthias Klose would like to find a way to do something that at the end
of a build will look for and collect all the relevant files that are
produced during an ICE (for example all the pre-processor inputs, etc).
I'm not sure how to best solve it, but he was imagining a hook somewhere
(in dpkg?) that would look for them and copy them into the directory.




Looking for inputs!


-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature

Reply via email to