2013/2/6 Fernando Cerezal <[email protected]>

> 2013/2/5 Les Mikesell <[email protected]>:
> > On Tue, Feb 5, 2013 at 6:33 AM, Fernando Cerezal <[email protected]>
> 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. 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.
>

You mean, cloning "head" workspace for axe builds ? Would this really be
more efficient than a fresh checkout ?




>
> Regards.
>
> >
> > --
> >    Les Mikesell
> >      [email protected]
> >
> > --
> > 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 [email protected].
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
> --
> 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 [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to