[Building Sakai] Jenkins deployment issue

Liu, Peter peter.liu at yale.edu
Thu Apr 24 11:38:07 PDT 2014


Thanks Sam and this is valuable information.

-Peter

From: Sam Ottenhoff [mailto:ottenhoff at longsight.com]
Sent: Thursday, April 24, 2014 2:00 PM
To: Liu, Peter
Cc: sakai-dev; Matthew Buckett
Subject: Re: [Building Sakai] Jenkins deployment issue



Should we just to pre-build the entire sakai-binary tar file and then un-tar it instead to run the sakai:deploy (take too long)?

Any suggestion (or how your institution does the deployment via Jenkins) will be highly appreciated.


Yes, this is effectively what we do.  Build the entire source checkout from msub (with tests), validate that everything built cleanly, tar it all up, store it somewhere centrally accessible, and then schedule a series of rolling restarts to all nodes.  Take the first node down, clean out all JARs, clean out Tomcat work directories, then unroll the tarball, then start that node back up.  Rinse, repeat.

--Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140424/c96f55d8/attachment.html 


More information about the sakai-dev mailing list