Bug#652634: Allow to copy additional files out of the build directory

On Sat, Dec 24, 2011 at 05:22:05PM +0900, Junichi Uekawa wrote:
> Hi,
>
> I'd use a shell array for specifying the values; but yes I think I
> too wanted this feature at one point.

Attached is a patch that uses a shell array and adds some documentation.
Please apply if you see fit.

> Would list of filename (I will imagine there will be requests for all
> sorts of wildcards after release, which is kind of a pain) be useful
> or a directory that a post-build script can write to after build be
> useful?  (I think qemubuilder needed something to do with a specific
> directory that you can write to, but I will need to check how I did
> it).

I'd be great to have this in first and see how others use it. It
wouldn't be a problem to introduce an ADDITIONAL_BUILD_RESULTS_DIR
later.
Cheers,
 -- Guido

>From ad3569e07a9cc64cd5b126193cddf311e48180a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Guido=20G=C3=BCnther?= <agx@sigxcpu.org>
Date: Mon, 19 Dec 2011 13:31:59 +0100
Subject: [PATCH] Add ADDITIONAL_BUILDRESULTS variable

this can be used to copy additional build results out of the build
directory. It's useful to e.g. preserve a xml testresult file when using
a build system like Jenkins.

1 files changed, 6 insertions, 0 deletions

diff --git a/pdebuild b/pdebuild
index 97df19b..a98c253 100644
--- a/pdebuild
+++ b/pdebuild
@@ -63,6 +63,12 @@ if [ "${USE_PDEBUILD_INTERNAL}" = 'yes' ]; then
 	    conditional_cp_a ../"$files" "${BUILDRESULT}"
 	done
 	conditional_cp_a ../${CHANGES} "${BUILDRESULT}"
+	if [ -n "${ADDITIONAL_BUILDRESULTS}" ]; then
+	    echo "Saving additional results ${ADDITIONAL_BUILDRESULTS[*]}"
+	    for FILE in ${ADDITIONAL_BUILDRESULTS[*]}; do
+		conditional_cp_a "${FILE}" "${BUILDRESULT}" || true
+            done
+	fi
     else
 	log "E: BUILDRESULT=[$BUILDRESULT] is not a directory."
 	exit 1