deb-build-jobs issueshttps://source.puri.sm/Librem5/deb-build-jobs/-/issues2019-09-07T19:20:49Zhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/14Run and evaluate post build step on Jenkins for package specific tests2019-09-07T19:20:49ZArno BauernoppelRun and evaluate post build step on Jenkins for package specific tests* [x] Use autopkgtest from jobs.groovy
* [x] Extend groovy script to run test as postbuild step
* [x] Evaluate test outcome and present it in jenkins
* [x] Send E-Mail to mailing list if test failed
* [x] Mark package as stable, uns...* [x] Use autopkgtest from jobs.groovy
* [x] Extend groovy script to run test as postbuild step
* [x] Evaluate test outcome and present it in jenkins
* [x] Send E-Mail to mailing list if test failed
* [x] Mark package as stable, unstable or failed (built & tests successful, built & test failed or build failed)Arno BauernoppelArno Bauernoppel2019-08-20https://source.puri.sm/Librem5/deb-build-jobs/-/issues/13Create environments for post build step to run package specific tests2019-08-24T10:21:07ZArno BauernoppelCreate environments for post build step to run package specific tests* [x] Automate recreation of the images on distribution changes in [server script](https://source.puri.sm/Librem5/deb-build-jobs/issues/8)
* [x] Prepare test container environments
* [x] Manually verify that Debian autopkgtest can be ...* [x] Automate recreation of the images on distribution changes in [server script](https://source.puri.sm/Librem5/deb-build-jobs/issues/8)
* [x] Prepare test container environments
* [x] Manually verify that Debian autopkgtest can be run in imageCurrent: Aster (W32-34)Arno BauernoppelArno Bauernoppel2019-08-20https://source.puri.sm/Librem5/deb-build-jobs/-/issues/50blessed-builds: tests not being run on succesuful uploads2020-12-14T10:45:30ZGuido Guntherblessed-builds: tests not being run on succesuful uploadsNote that for all builds passing the 'Upload Debian Packages' stage with success (instead of unstable) the test stage is then not being run, this is due to
https://source.puri.sm/Librem5/deb-build-jobs/blob/master/blessed_build_auto.gro...Note that for all builds passing the 'Upload Debian Packages' stage with success (instead of unstable) the test stage is then not being run, this is due to
https://source.puri.sm/Librem5/deb-build-jobs/blob/master/blessed_build_auto.groovy#L252
checking for `.SUCCESS` but that is not set in the 'Upload Debian Packages' stage (and no other stage before that afaik.
/cc @arno.bauernoppelArno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/37blessed-builds: lintian check always fails2020-01-23T17:14:05ZGuido Guntherblessed-builds: lintian check always failsthe lintian check checks the binary package but that will always fail since the `.dsc` got mangled by our `mergechanges` call:
```
E: mesa changes: bad-distribution-in-changes-file amber-phone
E: mesa changes: file-size-mismatch-in-chan...the lintian check checks the binary package but that will always fail since the `.dsc` got mangled by our `mergechanges` call:
```
E: mesa changes: bad-distribution-in-changes-file amber-phone
E: mesa changes: file-size-mismatch-in-changes-file mesa_19.2.4-1pureos+librem5.2.dsc 4524 != 5233
E: mesa changes: checksum-mismatch-in-changes-file md5 mesa_19.2.4-1pureos+librem5.2.dsc
E: mesa changes: checksum-mismatch-in-changes-file sha1 mesa_19.2.4-1pureos+librem5.2.dsc
E: mesa changes: checksum-mismatch-in-changes-file sha256 mesa_19.2.4-1pureos+librem5.2.dsc
```
@arno.bauernoppel to avoid that you can either change it to check the source changes file or (better) add `--source-only-changes` to `pbuilder-options` and drop the `mergechangelog` call completely.Arno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/16Merge arm01 package list into arm02 yaml2019-09-13T23:04:18ZArno BauernoppelMerge arm01 package list into arm02 yamlAfter the main arm02 build process is tested and verified, all packages should be listed in packages yaml.
* [x] Talk through the process with the developers (signed tags, changes in yaml)
* [x] Merge the yaml lists from arm01 to arm02After the main arm02 build process is tested and verified, all packages should be listed in packages yaml.
* [x] Talk through the process with the developers (signed tags, changes in yaml)
* [x] Merge the yaml lists from arm01 to arm02Arno BauernoppelArno Bauernoppel