Re: Re: Ivy + hudson CI - problems downloading artifacts, please, help

[Eu...@gmail.com]

Thank you for the hint. I gotta see if this approach will work for us.


Eugene

On Feb 24, 2010 12:09pm, Willem Verstraeten <wi...@luciad.com>  
wrote:






> Hi,



> The problem is due to concurrent access to the Ivy cache. I was unable
> to get that working, so I simply configured each Hudson job to have its
> own cache directory.



> I did that by adding following line to the settings file used by the
> Hudson job :



> ivycache" useOrigin="true"/>



> This assumes that you invoke Ivy through the ant tasks, in which case
> the ${basedir} attribute is expanded to the ant build's basedir.



> Hope this helps,

> Willem





> Euguess@gmail.com wrote:
> Hi,




> I'm not subscribed to the list, so, please, make sure you have my
> address in CC for replies.




> We are having more than 150 projects in hudson CI with dependencies
> tracked by Ivy (2.1.0).




> Lately we are having more and more problems with it because ivy cannot
> copy/download artifacts correctly.




> There are two main errors we are getting:


> 1. size of source file differs from the size of dest file


> 2. impossible to move part file to definitive one




> In mailing list i found this answer from Xavier Hanin:


> When Ivy downloads ivy files from a repository, it first download them
> to a


> temporary file (used to be in temp directory until 2.0 beta 1, where
> the ivy


> file is downloaded to the cache). Then it moves the temporary file to
> the


> final location in the cache, and this is what seems to be failing for
> your


> user. Cleaning the cache should fix the problem, if it happens
> frequently


> you should try to investigate the issue. Maybe it is due to the use of
> the


> same cache by multiple processes concurrently. This use case is
> supported


> only with 2.0 beta 1, with the repository cache locking to avoid such


> concurrency issues.




> As i mentioned above our version is 2.1.0, but we still have this issue




> I also saw the same problem reported before, but there was no answer


> http://www.mail-archive.com/ivy-user@ant.apache.org/msg03152.html




> Thanks,


> Eugene

Re: Re: Re: Ivy + hudson CI - problems downloading artifacts, please, help

[Eu...@gmail.com]

Hi,

Here is another variant we found:

<caches useOrigin="true" lockstrategy="artifact-lock"/>

Apparently, the default set up is no-lock, therefore in continuous  
integration environment it might cause those issues.

see http://ant.apache.org/ivy/history/2.1.0/settings/lock-strategies.html

Artifact-lock seems to be very good for CI env.

We are going to try it out as it seems to be much less intrusive for our  
environment.

Did you try it?


Thanks,
Eugene




On Feb 24, 2010 12:29pm, Euguess@gmail.com wrote:
> Thank you for the hint. I gotta see if this approach will work for us.


> Eugene

> On Feb 24, 2010 12:09pm, Willem Verstraeten  
> willem.verstraeten@luciad.com> wrote:
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> >
> >
> > The problem is due to concurrent access to the Ivy cache. I was unable
> > to get that working, so I simply configured each Hudson job to have its
> > own cache directory.
> >
> >
> >
> > I did that by adding following line to the settings file used by the
> > Hudson job :
> >
> >
> >
> > ivycache" useOrigin="true"/>
> >
> >
> >
> > This assumes that you invoke Ivy through the ant tasks, in which case
> > the ${basedir} attribute is expanded to the ant build's basedir.
> >
> >
> >
> > Hope this helps,
> >
> > Willem
> >
> >
> >
> >
> >
> > Euguess@gmail.com wrote:
> > Hi,
> >
> >
> >
> >
> > I'm not subscribed to the list, so, please, make sure you have my
> > address in CC for replies.
> >
> >
> >
> >
> > We are having more than 150 projects in hudson CI with dependencies
> > tracked by Ivy (2.1.0).
> >
> >
> >
> >
> > Lately we are having more and more problems with it because ivy cannot
> > copy/download artifacts correctly.
> >
> >
> >
> >
> > There are two main errors we are getting:
> >
> >
> > 1. size of source file differs from the size of dest file
> >
> >
> > 2. impossible to move part file to definitive one
> >
> >
> >
> >
> > In mailing list i found this answer from Xavier Hanin:
> >
> >
> > When Ivy downloads ivy files from a repository, it first download them
> > to a
> >
> >
> > temporary file (used to be in temp directory until 2.0 beta 1, where
> > the ivy
> >
> >
> > file is downloaded to the cache). Then it moves the temporary file to
> > the
> >
> >
> > final location in the cache, and this is what seems to be failing for
> > your
> >
> >
> > user. Cleaning the cache should fix the problem, if it happens
> > frequently
> >
> >
> > you should try to investigate the issue. Maybe it is due to the use of
> > the
> >
> >
> > same cache by multiple processes concurrently. This use case is
> > supported
> >
> >
> > only with 2.0 beta 1, with the repository cache locking to avoid such
> >
> >
> > concurrency issues.
> >
> >
> >
> >
> > As i mentioned above our version is 2.1.0, but we still have this issue
> >
> >
> >
> >
> > I also saw the same problem reported before, but there was no answer
> >
> >
> > http://www.mail-archive.com/ivy-user@ant.apache.org/msg03152.html
> >
> >
> >
> >
> > Thanks,
> >
> >
> > Eugene
> >
> >
> >
> >
> >
> >
> >