Re: Building for deployment
Re: Building for deployment
- Subject: Re: Building for deployment
- From: Kieran Kelleher <email@hidden>
- Date: Mon, 14 Dec 2009 09:29:56 -0500
My build.xml installs all dependent frameworks locally. Wonder is
installed locally from the same working copy as the wonder workspace
projects are linked to. A bash script then runs my project's
build.xml, copies the tar.gz's remotely to one relay server, then
executes commands via ssh to copy from remote relay server to other WO
nodes on the remote cluster (usually no more than 3 to 5 machines),
then executes ssh commands to extract and set permissions on those
remote bundles. If there is statis webserver root dir, then the script
will execute svn update in that dir to pull latest static resources.
custom build.app.name property is constructed by the script every time
using the svn version and datetime suffix, example
myapp_1234_200912061323 = my app, svn version 1234, build date/time
12/06/2009 1:23pm.
Then it is a case of going into WOMonitor and update the launch path
for new instances and start launching new instances and refusing
sessions on old version (assuming your database changes, if any, won't
break the old version apps before they die.)
That's it in a nutshell.
HTH, Kieran
On Dec 14, 2009, at 9:15 AM, Henrique Prange wrote:
Hi Mark,
On 13/12/09 20:00, Mark Wardle wrote:
What's the recommended way of creating sane builds - particularly
using PW and your own frameworks from source and making everything
work as automatically as possible?
I used to speak like that before I started using Maven [1]. Have you
ever heard about it? :p
You'll spend some time learning how to add Maven configuration to
your project. But it pays off. You'll get sane builds and better
integration with tools like Hudson.
[1]http://wiki.objectstyle.org/confluence/display/WOL/Quick+Start
Cheers,
Henrique
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden