On Wed, Feb 6, 2013 at 8:46 AM, Fernando Cerezal <krypto...@gmail.com> wrote:
>>>
>>> Really, there are several projects, with their own tests each one, but
>>> all of them are folders of the same svn repository.
>>
>> That doesn't quite mesh with the description of each one needing
>> access to the others contents.
>
> All of them are libraries, with executables for testing. Several of
> them uses each other.
I think the typical way to handle this in subversion is to make each
project that builds separately have its own trunk/branches/tags tree
and every part that needs to include components from a separate area
would use svn externals to pull them into a checkout. That (a) lets
you either float the external references on the trunk for coordinated
development or pin them to tested/released versions as components
diverge and the project using them nears a release - and (b) minimizes
each checkout to the parts that are actually needed, whether by
jenkins or a developer.
>>
>> Assuming you have enough disk space, if your job check-out strategy is
>> 'use svn update', after the first run it will just download the
>> changes. Perhaps not ideal, but it shouldn't take a lot of bandwidth
>> between runs unless you are making huge changes or checking in
>> binaries.
>
> This is not present behaviour. It creates a directory in workspace
> named like user-axis, inside ir creates a directory for every axis
> value and inside each of them it performs a svn checkout. I only want
> a checkout in workspace.
Yes, that is the layout your job requests. But what I meant was that
on the 2nd and subsequent runs of this job, jenkins should be doing
an 'svn update' into those existing workspaces which should not be an
expensive operation even if you have to repeat it a few times. And,
if you ever want to version your components independently you really
will want separate copies for each build - so there is a reason for
jenkins' behavior.
--
Les Mikesell
lesmikes...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
