Re: Want something like "failonerror" for artifactspublisher

In this case, it's an Ant <exec> task where the program in question 
apparently isn't returning a non-zero exit code. It does for certain 
types of errors, but not for others. <exec> is not forked, although I've 
also tried with forking.

(Probably way more detail than is useful, but it's a TIBCO java program 
which uses the Eclipse framework and logs error details to a log file, 
although which I can control to log a log4j ERROR summary message to 
stdout as well. As you might expect, using the <java> task instead of 
the <exec> one didn't make a difference.)

On 5/26/2010 1:44 AM, Assaf Lavie wrote:
> What sort of build task isn't failing on error? I'm aware of such a 
> problem with Ant, for example, but it's fixable.
>
> On Mon, May 24, 2010 at 8:38 PM, Doug Breaux 
> <[email protected] <mailto:[email protected]>> 
> wrote:
>
>     Is there any way to get CC to consider the build failed if the
>     artifactspublisher fails? It's logging an error about not being
>     able to copy
>     the file in question, but CC still says the build was successful.
>
>     (I have some build-type tasks that are not causing the build to
>     fail when they
>     fail, despite failOnError="true", and it seems one of the simplest
>     ways to
>     catch all of them is to report a failure when the artifact doesn't
>     exist.)
>
>     Doug
>

------------------------------------------------------------------------------

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user