svn export would take less disk space, but switching to another VCS alltogether may be what you want for speed.
While I personally believe that svn forces you to get the governance of a code base right, I think git dodges that entirely (thats why linux kernel developers like it). However, git considerably outperforms svn in checkout speed and space needed on disk. Its your call - if you are going for speed or space, is the minor step up from check out to export really helping that? Terry Rankine ________________________________________ From: jenkinsci-users@googlegroups.com [jenkinsci-users@googlegroups.com] On Behalf Of Jim McCaskey [jim.mccas...@pervasive.com] Sent: Friday, 24 February 2012 3:00 AM To: 'jenkinsci-users@googlegroups.com' Subject: RE: Using svn export instead of svn checkout FWIW: This request has been open for a few years: https://issues.jenkins-ci.org/browse/JENKINS-1304 Your concerns is disk space, my concern is speed of checkout. Export can be much faster on a very large tree. Like you I do clean checkouts so any of the other concerns don't apply for me. Maybe make it an option only when clean checkouts are done? -Jim -----Original Message----- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Asmann, Roland Sent: Thursday, February 23, 2012 6:53 AM To: jenkinsci-users@googlegroups.com Subject: Re: Using svn export instead of svn checkout Since we already use the clean checkout option, I don't see where the performance can be gained. As for tracing changes, I don't care about those on a build-server! The only purpose of a build-server is to check out the code, build it and report on that. If your build-server is making changes and checking those in, you are not using it in the right way! Disk space is cheap? I don't know in what company YOU work and if YOU can decide on buying more space, I have to fight for every MB of extra space I need and it takes months before it is finally decided IF I will even get it. I am not asking for the export option as the default or for getting rid of the checkout, I am just asking to add it as an alternative -- just like the other options that are already in the list! Roland On 23.02.2012 13:37, Didier Durand wrote: > Hi, > > Even if checkout was possible, I don't think that it is a good idea > from a perf standpoint: if you export a file, it gets out of svn > control and the changes cannot be tracked. > > So, next time your run the job, you have to do a full export again > even if the file didn't change inbetween: can take a long time for a > big file. > > So, as disk space is cheap, I would prefer several copies rather than > the network burden (and corresponding delay to start) of a big file > > regards > > didier > > On Feb 23, 12:40 pm, "Asmann, Roland" <roland.asm...@adesso.at> wrote: > > Hi all, > > > > Would it be possible to use 'svn export' instead of 'svn checkout'? > > We have a couple of projects that contain very large files, which are > > then obviously saved twice on the Server -- once as the actual file and > > once as the bas-version for SVN. > > > > Since we don't check-in stuff from Jenkins, we would definitely benefit > > in both performance and disc usage when getting our project using 'svn > > export'. Can this be added to the svn-plugin as one of the options? > > > > Thanks, > > > > Roland > > > > -- > > Roland Asmann > > Senior Software Engineer > > > > adesso Austria GmbH > > Floridotower 26. Stock T +43 1 2198790-27 > > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 > > A-1210 Wien M +43 664 88657566 > > E roland.asm...@adesso.at > > Wwww.adesso.at > > > > ------------------------------------------------------------- > > >>> business. people. technology. <<< > > ------------------------------------------------------------- > -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at ------------------------------------------------------------- >>> business. people. technology. <<< -------------------------------------------------------------
