Hi builds@,

I'm still not having much luck trying to get the following functionality
sorted out on our CI build. The latest build is here [1], but it would be
great if we could add the functionality of archiving artefacts, publishing
JUnit test result report and publish the Javadocs (which by the looks of it
is already being done!).

Thanks in advance for any pointers or help.

Lewis

BUILD SUCCESSFUL
Total time: 10 minutes 30 seconds
Archiving artifacts
ERROR: No artifacts found that match the file pattern
"trunk/build/*.tar.gz". Configuration error?ERROR
<http://stacktrace.jenkins-ci.org/search?query=ERROR>:
'trunk/build/*.tar.gz' doesn't match anything: 'trunk' exists but not
'trunk/build/*.tar.gz'
Build step 'Archive the artifacts' changed build result to FAILURE
Recording test results
Publishing Javadoc
Sending e-mails to: d...@nutch.apache.org lewis.mcgibb...@gmail.com
doga...@gmail.com markus.jel...@openindex.io mattm...@jpl.nasa.gov
a...@getopt.org apa...@digitalpebble.com
Finished: FAILURE

[1]
https://builds.apache.org/view/M-R/view/Nutch/job/Nutch-trunk/1608/console

On Sun, Sep 18, 2011 at 8:40 PM, lewis john mcgibbney <
lewis.mcgibb...@gmail.com> wrote:

> Good Evening,
>
> I haven't been able to find documentation on any of the above and I am not
> having much luck configuring any of these three within the Nutch-branch-1.4
> nightly build. You can see that build #8 [1] failed as the file pattern was
> consistently incorrect for all of the properties.
>
> It would be great if we configure something along the lines of
>
> Archive the artefacts:
> branch-1.4/build/*.tar.gz
>
> Publish JUnit test result report:
> branch-1.4/build/test/*.xml
>
> Publish Javadoc:
> branch-1.4/build/docs/api
>
> For the time being I've disabled all of tehe above and build #9 is back to
> normal but it would be great if we could get some help to get this
> configured correctly.
>
> Thanks for any help.
>
> [1]
> https://builds.apache.org/view/M-R/view/Nutch/job/Nutch-branch-1.4/8/console
>
> --
> *Lewis*
>
>


-- 
*Lewis*

Reply via email to