Re: [Treebase-devel] re-build and deploy

[Vladimir G. <vga...@ne...>]

On Feb 24, 2010, at 11:14 AM, Hilmar Lapp wrote:

> How far are we from shutting that down?

I think 6666 should stay running, as a reference: I am not confident  
that treebase-dev:8080 has all installation glitches ironed out, so  
when something odd comes up, it is useful to first check whether 6666  
exhibits that as well.   Though, there is no need to keep 6666 up-to- 
date all the time.


> I.e., can everyone deploy to treebase-dev and does it have the same  
> working features as the port 6666 instance?

Only Jon can redeploy to treebase-dev.

Ideally, we'd want an automated re-build and re-deploy triggered by  
commits to SVN, but since setting up a build environment on the server  
was expected to take some up-front time, we decided that the following  
was satisfactory:

  (1) Vladimir checks out new version and builds a WAR on his laptop
  (2) Passes the WAR to Jon
  (3) Jon deploys the WAR on the server

I'd prefer to go through this dance when someone (a non-developer)  
actually needs to see new changes on the server, rather than after  
each SVN commit.

For passing WARs in (2), Jon has set up an SVN, into which I commit  
the WARs.   Other developers should be able to commit there, too  
(perhaps, after asking Jon for credentials). The repository is at   svn 
+ssh://you...@sv.../repos/treebase

For a half-ideal solution, we could consider some upfront effort to  
set up automatic re-deployments triggered by commits into this WAR  
repository.

--Vladimir