Hi,

Lets say I had a directory "foo" within my build system which has
output files that get created a build time (logs, metrics, coverage
output etc) called "foo/build_output".

To collect those files and to place them each under a sub-directory
based on the build number I did this :

<publishers>
                        <buildpublisher>
                                <sourceDir>/home/ci/src/foo/
build_output/</sourceDir>
                                <publishDir>/home/ci/www/builds</
publishDir>
                                <useLabelSubDirectory>true</
useLabelSubDirectory>
                                <alwaysPublish>true</alwaysPublish>
                        </buildpublisher>
</publishers>

Note that I used useLabelSubDirectory to collect each build output
under a sub-directory named by the build number.

That works great.  For build 1234, all the files form foo//
build_output/* will go into /home/ci/www/builds/1234/.

However, lets say I now have 2 additional source directories called
"bar" and "baz" each of which has a build_output folder I would also
like to collect.

What I would like to do is create the hierarchy :

    foo/build_output will get published to /home/ci/www/builds/1234/
foo/.
    bar/build_output will get published to /home/ci/www/builds/1234/
bar/.
    baz/build_output will get published to /home/ci/www/builds/1234/
baz/.

However, I can't see any way to accomplish that with the config
parameters that exist.  Am I missing something?

What I think this would require is some kind of placeholder within the
publish folder for the build number, e.g. :

   <publishDir>/home/ci/www/builds/%B/foo</publishDir>

Hopefully this can be done with existing functionality in a way that
I've missed.

Thanks,
Colm

Reply via email to