aboutsummaryrefslogtreecommitdiff
path: root/pbuilder-updatebuildenv
diff options
context:
space:
mode:
authorGuido Günther <agx@sigxcpu.org>2012-03-09 16:57:47 +0100
committerJunichi Uekawa <dancer@netfort.gr.jp>2012-03-13 17:11:43 +0900
commit21fd0ff9341f4ec3c51421158a3ea796474e4ded (patch)
treef74284c9c03b07447d1f957ef22aa03c83b7a808 /pbuilder-updatebuildenv
parent0cdf8473e542ca6e54c7afe6d68e85e3727f0e88 (diff)
downloadpbuilder-21fd0ff9341f4ec3c51421158a3ea796474e4ded.tar
pbuilder-21fd0ff9341f4ec3c51421158a3ea796474e4ded.tar.gz
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.
Diffstat (limited to 'pbuilder-updatebuildenv')
0 files changed, 0 insertions, 0 deletions