Promu does not fail if expected directories are not present for `crossbuild tarballs`

[bwplotka]

Version: 9583e5a6448f97c6294dca72dd1d173e28f8d4a4

Output:

make tarballs-release
>> Publishing tarballs
/go/bin/promu-9583e5a6448f97c6294dca72dd1d173e28f8d4a4 crossbuild -v tarballs
Using config file: .promu.yml
Running command: crossbuild [-v tarballs]
>> building release tarballs
 +  cp -a .build/darwin-amd64/thanos .release/thanos-0.13.0-rc.0.darwin-amd64
cp: cannot stat '.build/darwin-amd64/thanos': No such file or directory
 >   thanos-0.13.0-rc.0.darwin-amd64.tar.gz
 +  tar zcf .tarballs/thanos-0.13.0-rc.0.darwin-amd64.tar.gz -C .release thanos-0.13.0-rc.0.darwin-amd64
 +  rm -rf .release
 +  cp -a .build/freebsd-amd64/thanos .release/thanos-0.13.0-rc.0.freebsd-amd64
cp: cannot stat '.build/freebsd-amd64/thanos': No such file or directory
 >   thanos-0.13.0-rc.0.freebsd-amd64.tar.gz
 +  tar zcf .tarballs/thanos-0.13.0-rc.0.freebsd-amd64.tar.gz -C .release thanos-0.13.0-rc.0.freebsd-amd64
 +  rm -rf .release
 +  cp -a .build/linux-amd64/thanos .release/thanos-0.13.0-rc.0.linux-amd64
cp: cannot stat '.build/linux-amd64/thanos': No such file or directory
 >   thanos-0.13.0-rc.0.linux-amd64.tar.gz
 +  tar zcf .tarballs/thanos-0.13.0-rc.0.linux-amd64.tar.gz -C .release thanos-0.13.0-rc.0.linux-amd64
 +  rm -rf .release
 +  cp -a .build/linux-arm64/thanos .release/thanos-0.13.0-rc.0.linux-arm64
cp: cannot stat '.build/linux-arm64/thanos': No such file or directory
 >   thanos-0.13.0-rc.0.linux-arm64.tar.gz
 +  tar zcf .tarballs/thanos-0.13.0-rc.0.linux-arm64.tar.gz -C .release thanos-0.13.0-rc.0.linux-arm64
 +  rm -rf .release
 +  cp -a .build/windows-amd64/thanos.exe .release/thanos-0.13.0-rc.0.windows-amd64
cp: cannot stat '.build/windows-amd64/thanos.exe': No such file or directory
 >   thanos-0.13.0-rc.0.windows-amd64.tar.gz
 +  tar zcf .tarballs/thanos-0.13.0-rc.0.windows-amd64.tar.gz -C .release thanos-0.13.0-rc.0.windows-amd64
 +  rm -rf .release
/go/bin/promu-9583e5a6448f97c6294dca72dd1d173e28f8d4a4 checksum -v .tarballs
Using config file: .promu.yml
Running command: checksum [-v .tarballs]
/go/bin/promu-9583e5a6448f97c6294dca72dd1d173e28f8d4a4 release -v .tarballs
Using config file: .promu.yml
Running command: release [-v .tarballs]
 > uploaded sha256sums.txt
 > uploaded thanos-0.13.0-rc.0.darwin-amd64.tar.gz
 > uploaded thanos-0.13.0-rc.0.freebsd-amd64.tar.gz
 > uploaded thanos-0.13.0-rc.0.linux-amd64.tar.gz
 > uploaded thanos-0.13.0-rc.0.linux-arm64.tar.gz
 > uploaded thanos-0.13.0-rc.0.windows-amd64.tar.gz

[bwplotka]

This causes Thanos release to produce empty tarballs without any notification

[bwplotka]

https://circleci.com/gh/thanos-io/thanos/9295