Thanks for your suggestions Les. I'm trying them 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 jenkinsci-users+unsubscr...@googlegroups.com.
For more opt
On Wed, Apr 24, 2013 at 10:50 AM, Les Mikesell wrote:
>>>
>> Alright. So there just is no way to have a multi configuration job reuse the
>> same checkout?
>
> No, in the general case, the jobs will run on different slaves and may
> be checked out with different native line endings. And they may
On Wed, Apr 24, 2013 at 8:14 AM, wrote:
>>> 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
I have what I take to be problem related to Fernando's. And I think the
solution should be the same. So here is my explanation.
I have essentially one svn repository. Its checkout is used for a multi
configuration job. The user axes provide variants of my Ant build. The
build is part of the che
On Wed, Feb 6, 2013 at 8:46 AM, Fernando Cerezal 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.
>
2013/2/6 nicolas de loof :
>
> 2013/2/6 Fernando Cerezal
>>
>> 2013/2/5 Les Mikesell :
>> > On Tue, Feb 5, 2013 at 6:33 AM, Fernando Cerezal
>> > wrote:
>> >> Is there any way to perform an unique checkout to workspace?
>> >
>> > Multi-configuration jobs are generally used to build in parallel
>>
2013/2/6 Les Mikesell :
> On Wed, Feb 6, 2013 at 6:44 AM, Fernando Cerezal 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
>
On Wed, Feb 6, 2013 at 6:44 AM, Fernando Cerezal 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 st
2013/2/6 Fernando Cerezal
> 2013/2/5 Les Mikesell :
> > On Tue, Feb 5, 2013 at 6:33 AM, Fernando Cerezal
> 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
2013/2/5 Les Mikesell :
> On Tue, Feb 5, 2013 at 6:33 AM, Fernando Cerezal 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 s
On Tue, Feb 5, 2013 at 6:33 AM, Fernando Cerezal 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.
>
> S
Hello,
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 nam
12 matches
Mail list logo
