deb-build-jobs issueshttps://source.puri.sm/Librem5/deb-build-jobs/-/issues2020-02-26T17:00:16Zhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/55blessed-builds: report success although no artifacts are produced2020-02-26T17:00:16ZGuido Guntherblessed-builds: report success although no artifacts are produced@arno.bauernoppel one more thing i noticed with your current pipeline logic:
if a job does not produce any debs the pipeline is marked as succesfull although it stops, see:
http://localhost:8080/job/Builds/job/debs/job/deb-folks-amber-...@arno.bauernoppel one more thing i noticed with your current pipeline logic:
if a job does not produce any debs the pipeline is marked as succesfull although it stops, see:
http://localhost:8080/job/Builds/job/debs/job/deb-folks-amber-phone-staging-aarch64/
(folks sets export-dir so the debs end up somehwere else but the pipeline must never report success then).Arno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/53blessed-builds: switch build machine to virtio2020-02-07T19:14:41ZGuido Guntherblessed-builds: switch build machine to virtio(filing it here since we don't have a dedicated visible repo for hw stuff):
The vm uses scsi emulation instead of virtio which is way more cpu intensive on I/O. We should switch to virtio.(filing it here since we don't have a dedicated visible repo for hw stuff):
The vm uses scsi emulation instead of virtio which is way more cpu intensive on I/O. We should switch to virtio.https://source.puri.sm/Librem5/deb-build-jobs/-/issues/42blessed builds autopkgtest fail on no available tests2020-12-08T15:15:38ZArno Bauernoppelblessed builds autopkgtest fail on no available testsIf a package has not tests available the package is marked as UNSTABLE. This needs to be discussed.If a package has not tests available the package is marked as UNSTABLE. This needs to be discussed.https://source.puri.sm/Librem5/deb-build-jobs/-/issues/34add a test build package2020-01-07T21:27:08ZGuido Guntheradd a test build packagewe should have a package that gets build every hour to ensure the pipeline is still working as expected.we should have a package that gets build every hour to ensure the pipeline is still working as expected.Arno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/33Better and official docs for blessed builds2019-12-02T16:46:21ZGuido GuntherBetter and official docs for blessed buildsThere was some discussion with @jeremiah.foster on updating the blessed build workflow and there's https://source.puri.sm/snippets/138 but we should have official docs that developers can follow.
see
- https://source.puri.sm/snippets/...There was some discussion with @jeremiah.foster on updating the blessed build workflow and there's https://source.puri.sm/snippets/138 but we should have official docs that developers can follow.
see
- https://source.puri.sm/snippets/138
- https://int.puri.sm/dev/librem-5/arm-64-packagebuildserver
related
- https://source.puri.sm/Librem5/developer.puri.sm/issues/124
- https://source.puri.sm/Librem5/developer.puri.sm/issues/43
parts of this should live on the pureos side (for everything past dput) while other things should live on the phone side (unless pureos proper wants to switch to git based builds soonish too).Jeremiah FosterJeremiah Fosterhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/24evaluate git-debpush2019-10-17T15:32:58ZGuido Guntherevaluate git-debpush(as mentioned previously but to have note) this does similar things than we do so we should reuse that where possible.(as mentioned previously but to have note) this does similar things than we do so we should reuse that where possible.