On Tue, Feb 5, 2013 at 6:33 AM, Fernando Cerezal <[email protected]> wrote:
> I am configuring a Jenkins server and I dont know, if possible, how to
> configure correctly svn checkout.
>
> I have a multiexecutable project. Building steps are:
> Checkout entire repository
> Build per project
> Test per project.
>
> So, I configured a multi-configuration project with an user-axis named
> "project" for iterating. However, instead of a single entire svn
> checkout, Jenkins performs a checkout in workspace, it creates a
> "project" directory, it creates a directory for each project and,
> inside each project directory, checkout again entire directory.
> I can't perform checkout iteratively because are interrelated
> projects, I need the code of two or three projects at the same time
> before I could build any of them.
>
> 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.
--
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.
