77536af43b
Right now the worst case chain of events for building an ISO on Hydra is - copy everything to squashfs builder - run squashfs builder - download squashfs from builder - compress squashfs - upload squashfs to S3 - copy squashfs to ISO builder - run ISO builder - download ISO from builder - compress ISO - upload ISO to S3 This inlines the squashfs build into the ISO build, which makes it - copy everything to ISO builder - run ISO builder - download ISO from builder - compress ISO - upload ISO to S3 Which should reduce queue runner load by $alot per ISO, which we have four of on small channels (one release, one test per arch) and a lot more than four of on large channels (with various desktops) |
||
---|---|---|
.. | ||
make-options-doc | ||
test-driver | ||
testing | ||
default.nix | ||
eval-cacheable-options.nix | ||
eval-config-minimal.nix | ||
eval-config.nix | ||
from-env.nix | ||
make-btrfs-fs.nix | ||
make-channel.nix | ||
make-disk-image.nix | ||
make-ext4-fs.nix | ||
make-iso9660-image.nix | ||
make-iso9660-image.sh | ||
make-multi-disk-zfs-image.nix | ||
make-single-disk-zfs-image.nix | ||
make-squashfs.nix | ||
make-system-tarball.nix | ||
make-system-tarball.sh | ||
qemu-common.nix | ||
systemd-lib.nix | ||
systemd-network-units.nix | ||
systemd-types.nix | ||
systemd-unit-options.nix | ||
test-script-prepend.py | ||
testing-python.nix | ||
utils.nix |