once via export-image, which generates the (compressed) image we're publishing;
once via export-noobs, which also takes a long time but doesn't seem to produce anything we're actually using.
Depending on the actual goals of the PTS project, focussing on the export-image might be sufficient.
At first glance (I didn't investigate for real), it seems the double export is controlled via those files:
stage2/EXPORT_IMAGE
stage2/EXPORT_NOOBS
so dropping the latter might be sufficient to avoid the double export, sparing roughly 10 minutes for each build (including the releases performed via GitHub Actions, when we're holding our breath for so long).
At the moment we're apparently exporting twice:
export-image, which generates the (compressed) image we're publishing;export-noobs, which also takes a long time but doesn't seem to produce anything we're actually using.Depending on the actual goals of the PTS project, focussing on the
export-imagemight be sufficient.At first glance (I didn't investigate for real), it seems the double export is controlled via those files:
so dropping the latter might be sufficient to avoid the double export, sparing roughly 10 minutes for each build (including the releases performed via GitHub Actions, when we're holding our breath for so long).