ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From glenn opdycke-hansen <>
Subject Re: svnant - deploying from Subversion
Date Fri, 05 Nov 2010 05:46:13 GMT
I "deploy" ant scripts from svn to different servers.  The configuration
information is stored in directories.  The ant script knows which
environment it is in and processes the appropriate directory to find the
correct config files.  This has been very helpful.


On Thu, Nov 4, 2010 at 15:44, Michael Ludwig <> wrote:

> Hello Antoine,
> Antoine Levy Lambert schrieb am 04.11.2010 um 13:53 (-0400):
> >
> > I would personnally not want to deploy the webapp directly from
> > subversion, although this can certainly work.
> > I would rather setup a build process and continuous integration and
> > create a zip file or a war file from the sources in subversion.
> > You would need to use a continuous integration server
> > (CruiseControl, Hudson, ...) and a repository to store the various
> > versions of your war or zip file.
> Thanks for your feedback. Our application is not Java, it's a script
> app. There's currently lots of stuff in Subversion including lots of
> static content, most of which never changes. A typical update means
> replacing ten to thirty files and possibly deleting some. Which is
> why I don't want to deploy the full app, just the diff.
> It could be zipped, of course; but it would have to be unzipped again,
> and we don't have shell access to the server (just RDP, but I don't know
> how to automate that), so we're dealing with network share access here,
> and thus zipping/unzipping is even counter-productive.
> We do have a Hudson server, but given the state of our app, there is not
> much we can use it for at the moment.
> > Ideally your web application should load the environment (server)
> > dependent data from property files.
> > On my project we are generating the environment dependent property
> > files from data stored in a LDAP server.
> > We have a custom schema with the property keys defined as
> > attributes, and we create one entry (or one subtree) for each
> > environment.
> > The script which generates the properties for one given environment
> > uses property files templates and replaces the tokens in these
> > templates with the values contained in LDAP.
> We're planning to do something very similar; to have a simple config
> preprocessor involving property files for environment data to adapt the
> configuration our scripts can read for various environments.
>  your LDAP                     = our property files
>  your property file templates  = our script config templates
>  your property files           = our script config
> --
> Michael Ludwig
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message