Thanks all - everything is working fine now. The problem was
fundamentally not realizing that Jenkins pulls over a copy of
everything (including build.xml) into the Jenkins workspace.
RB
On Mar 29, 4:25 am, Didier Durand wrote:
> Hi Richard,
>
> Generally speaking, you should never check-in resu
Hi Richard,
Generally speaking, you should never check-in results of tools produced
elsewhere for use on Jenkins. You should rather implement those tools on
your Jenkins server, run them there to obtain the results that you need in
further steps of your Jenkins jobs.
regards
didier
Le jeudi
I think you are on the right way. You don't need to check in the
output.xml files, just check in the build.xml file and create the
findbugs or checkstyle results while running the build (with your
build.xml file) in the Jenkins workspace.
Ulli
On 03/29/2012 09:21 AM, Richard Berger wrote:
> OK, I
OK, I think I figured it out... the key was that in the Advanced
settings for the "Invoke Ant" task, for the "Build File" I had put the
path to my eclipsestuff/workspace/project/build.xml - so all the
references inside that build.xml where being interpreted as relative
to "eclipsestuff".
Realizing
I am playing with Jenkins (which seems really cool) and have a
question on coordinating Post-build actions, for example "Publish
FindBugs analysis results".
I started this project in Eclipse and the code resides in the
directory eclipsestuff/workspace/project (not the real name). The
code is also
