-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/03/2012 11:44 PM, Michael Pailloncy wrote:
[...]
> In the meantime, I found out that there's an issue for this in JIRA
> already:
> https://issues.jenkins-ci.org/browse/JENKINS-14157
> Unfortunately, it's still unassigned.
>
>
So you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/04/2012 12:00 AM, Qazwart wrote:
> I'm a bit confused by this. All Subversion 1.1 to 1.7 clients should work
> with all Subversion servers from 1.1 and up.
>
> Besides Jenkins doesn't use the command line clients. It uses SvnKit.
>
> Why is t
I'm a bit confused by this. All Subversion 1.1 to 1.7 clients should work with
all Subversion servers from 1.1 and up.
Besides Jenkins doesn't use the command line clients. It uses SvnKit.
Why is the version of the Subversion client so important? Are you shipping or
sharing working directories
Le 03/08/2012 22:44, Fritz Elfert a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael,
On 08/03/2012 10:00 PM, Michael Pailloncy wrote:
Le 03/08/2012 21:30, Fritz Elfert a écrit :
I can't find any way to select the workspace
version per slave
Hi,
I'm not sure to clearly unders
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael,
On 08/03/2012 10:00 PM, Michael Pailloncy wrote:
> Le 03/08/2012 21:30, Fritz Elfert a écrit :
>> I can't find any way to select the workspace
>> version per slave
> Hi,
> I'm not sure to clearly understand what you want.
> If you have sla
Le 03/08/2012 21:30, Fritz Elfert a écrit :
I can't find any way to select the workspace
version per slave
Hi,
I'm not sure to clearly understand what you want.
If you have slaves with SVN 1.7 and slaves with 1.6 natively, you can
add labels like "svn1-6" to nodes with 1.6 version and "svn1-7"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
In the global config, the SVN workspace version can be selected. However
I have a mix of older/newer slave where some use 1.7 natively and some
others use still 1.6. I can't find any way to select the workspace
version per slave - which is a prere
