On Wed, Feb 6, 2013 at 6:44 AM, Fernando Cerezal <krypto...@gmail.com> wrote:
>
>>> Is there any way to perform an unique checkout to workspace?
>>
>> Multi-configuration jobs are generally used to build in parallel
>> across a different set of platforms or environments. If your job is
>> just one set of serialized steps why can't you just use a job with
>> several build steps or your own build script that does them all -
>> perhaps using svn externals to get all the code components? Or
>> organize things so the artifacts from one build are available to the
>> next.
>
>
> Thank you for answering.
>
> 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.
> For a multipart
> project, jenkins generate reports automatically for every subproject.
> The problem is it downloads n+1 times the entire repository for n
> projects.
>
> Solution can be so simple as don't use axis on checkout, if it is possible.
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.
--
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.
