We currently publish a lot of large images for each build and it would be beneficial for our long term storage management and release process if PublishArtifacts published fewer image artefacts. * ext4 images are an intermediate of the live images, but it doesn't make sense to publish those. * we support compression for each image by appending a compression format to the image type in IMAGE_FSTYPES, i.e. IMAGE_FSTYPES += "wic.bz2"
Images QA test are: - beaglebone/ - core-image-sato-sdk-beaglebone.* - u-boot* - zImage* - edgerouter/ - core-image-sato-sdk-edgerouter.* - miodules* - vmlinux* - mpc8315e-rdb/ - core-image-minimal-mpc8315e-rdb.* - genericx86-64-lsb/ - core-image-lsb-sdk-genericx86-64.* - genericx86-64/ - core-image-sato-sdk-genericx86-64.* - core-image-sato-sdk-ptest-genericx86-64.hddimg - core-image-sato-sdk-ptest-genericx86-64.wic - genericx86-lsb/ - core-image-lsb-sdk-genericx86.* - genericx86-64/ - core-image-sato-sdk-genericx86.* - qemu/ - qemux86/ - bzImage-qemux86.bin - core-image-sato-sdk-qemux86.* - qemux86-64/ - bzImage-qemux86-64.bin - core-image-sato-sdk-qemux86-64.* - qemuarm/ && qemuarm64/ && qemumips/ && qemumips64/ && qemuppc/ - *.bin - core-image-sato-sdk*
Some preliminary changes were made but there's certainly more we can do.
Is this part of the autobuilder rework? If not, will it be ready for YP 2.5 M3?
Bulk move from 4.99 or 0.00 to 5.99