Perform SVN export rather than checkout

Comments

3 comments

  • Avatar
    Yogi Kulkarni

    Hi Ian,


    We could support this, however that would make updates on subsequent runs expensive because Go would end up exporting the whole repo each time instead of only fetching incremental changes.


    If you're using Ant, you could use a filterset to exclude .svn folders zipping directories into artifacts.


    -Yogi

    0
    Comment actions Permalink
  • Avatar
    Ian Bridson

    Hi Yogi


    Our situation is that this build pipeline is for PL/SQL packages, so there is no actual build, just Manually triggered to fetch files from 3 svn folders to a set of artifacts. then subsequent pipelines send these files to a database (ftp from agent on go server). So it is imperative that the artifact is as small as possible so that the ftp is as small as possible and the process as quick as possible (at least faster than manual operation).


    I wouldn't mind the option of exporting the whole of these folders each time, as i think this would be faster than removing the .svn folders after check out, or a built in method of filtering out the .svn folders when creating the artifact. Would an exclude filter on teh artifact process be easier?

    0
    Comment actions Permalink
  • Avatar
    Yogi Kulkarni

    Ian,


    The simplest option would be to have a job in the pipeline which calls a script (Ant, Ruby or whatever you'll usually use) to generate the artifiact as a zip file, and then upload the zip as part of the job. Would this work in your case?


    -Yogi

    0
    Comment actions Permalink

Please sign in to leave a comment.