Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/bin/build-packages
diff options
context:
space:
mode:
authorErich Eckner <git@eckner.net>2017-06-21 09:51:06 +0200
committerErich Eckner <git@eckner.net>2017-06-21 09:51:46 +0200
commit20c43882cc767155c01459dad10eb717c9dcafb8 (patch)
tree079b7530cf930fc8fc10c9daaa6869c1d8887055 /bin/build-packages
parent98143c23a08fba04eee84667c1c9b8895dd65da8 (diff)
bin/build-packages: save and upload build log if build fails
Diffstat (limited to 'bin/build-packages')
-rwxr-xr-xbin/build-packages16
1 files changed, 11 insertions, 5 deletions
diff --git a/bin/build-packages b/bin/build-packages
index 5420f56..3d9853e 100755
--- a/bin/build-packages
+++ b/bin/build-packages
@@ -9,8 +9,6 @@
# use different build commands for different repositories - do we need
# this actually?
-# send logs of failed builds
-
# handle if build fails due to "local issues" (e.g. unclean
# build environment, wrong mirror, ...)
@@ -190,8 +188,13 @@ while [ ${count} -ne 0 ]; do
for parameters in '' '-c'; do
rm -f *".pkg.tar.xz" *".pkg.tar.xz.sig"
- if staging-i686-build ${parameters} -- archlinux32-keyring; then
- # build successful
+
+ if staging-i686-build ${parameters} -- archlinux32-keyring 2>&1 > \
+ "$(
+ date -u --iso-8601=seconds | \
+ cut -d+ -f1
+ ).build-log"; then
+ # build successful
ls -1 *.pkg.tar.xz | \
xargs -rn1 gpg --local-user="${package_key}" --detach-sign
tar -cf 'package.tar' $(
@@ -244,11 +247,14 @@ while [ ${count} -ne 0 ]; do
done
if ! ${success}; then
+ tar -czf 'build-logs.tar.gz' \
+ *'.build-log'
while ! ssh \
-i "${master_build_server_identity}" \
-p "${master_build_server_port}" \
"${master_build_server_user}@${master_build_server}" \
- 'return-assignment' "${package}" "${git_revision}" "${mod_git_revision}" "${repository}" 'ERROR'; do
+ 'return-assignment' "${package}" "${git_revision}" "${mod_git_revision}" "${repository}" 'ERROR' < \
+ 'build-logs.tar.gz'; do
wait_some_time 15
done
if ${exit_after_failure}; then