On Sat, Apr 24, 2010 at 07:23:20PM +0300, anatoly techtonik wrote:
> On Sat, Apr 24, 2010 at 4:59 PM, Stefan Sperling wrote:
> > On Sat, Apr 24, 2010 at 04:05:04PM +0300, anatoly techtonik wrote:
> >> Hello,
> >>
> >> We have an issue in Bitten [1] continuous integration system that if
> >> SVN fa
On Sat, Apr 24, 2010 at 4:59 PM, Stefan Sperling wrote:
> On Sat, Apr 24, 2010 at 04:05:04PM +0300, anatoly techtonik wrote:
>> Hello,
>>
>> We have an issue in Bitten [1] continuous integration system that if
>> SVN fails when checking out externals, we can't detect this. Therefore
>> build proce
Stefan Sperling elego.de> writes:
>
> On Sat, Apr 24, 2010 at 04:05:04PM +0300, anatoly techtonik wrote:
> > Please, CC.
> >
> > [1] http://bitten.edgewall.org/ticket/552
>
> I guess the easiest fix would be to make svn use an exit code of 1
> if updating externals failed. Would that solve you
On Sat, Apr 24, 2010 at 04:05:04PM +0300, anatoly techtonik wrote:
> Hello,
>
> We have an issue in Bitten [1] continuous integration system that if
> SVN fails when checking out externals, we can't detect this. Therefore
> build process, where "svn" is essential chain link continues when it
> sho
Hello,
We have an issue in Bitten [1] continuous integration system that if
SVN fails when checking out externals, we can't detect this. Therefore
build process, where "svn" is essential chain link continues when it
should fail. Please advise, what should be done in this case. Maybe it
could be fi
