Thanks Ryan...i thought using export would be a bad idea...but using
update was something I thought about later. Plus, i'll take a look at
notify mirror.
Dna
On Jan 9, 12:53 pm, Ryan Schmidt <subversion-20..._at_ryandesign.com>
wrote:
> On Jan 9, 2012, at 07:40,fmdanowrote:
>
> > Ok, so CI is the best approach, but is there a way or an approach that
> > just uses SVN? can you use a tag and update a test server via an
> > update, or do you have to use export and export over the existing
> > code? Is there an easy way to do this where the test server code can
> > be a working copy checked out of SVN, or does it need to be just code
> > and use an export?
>
> Sure, either way. Actually I'd be skeptical about exporting on top of an existing directory, and would recommend updating a working copy instead. You haven't said what kind of dev and test servers these are -- I've been assuming so far you're talking about web site development. That may affect your choice of script. But another script to look into is SVN::Notify::Mirror.
>
> http://search.cpan.org/perldoc?SVN::Notify::Mirror
>
> The idea of this script is that by just creating tags in your repository that follow a certain naming pattern (that you define), code gets promoted to the dev or test or live environments. Developers never need (and never get) passwords or access to the dev or test or live environment servers.
Received on 2012-01-09 19:09:32 CET