[Building Sakai] Jenkins deployment issue

[David Haines]

At Michigan we use Jenkins to run a build script that compiles Sakai and
then creates a customized tarball we can expand over an empty tomcat.  We
use these builds for all installs to our test / production clusters.  The
actual install is done by Ops with their own tool.  It doesn't take long.

- Dave

On Fri, Apr 25, 2014 at 4:55 AM, Matthew Buckett <
matthew.buckett at oucs.ox.ac.uk> wrote:

> On 24 April 2014 18:42, Liu, Peter <peter.liu at yale.edu> wrote:
> >
> > 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)?
>
> Locally we take the Sakai .zip and put it into a debian package. Then
> when we come todo the upgrade we just upgrade the version of the
> debian package. You can have the debian package upgrade scripts also
> do the service restarting as well although I don't believe we use
> this.
>
> > Any suggestion (or how your institution does the deployment via Jenkins)
> > will be highly appreciated.
>
> We do use jenkins todo continuous  integration, but we don't have it
> make our final builds or package them.
>
> --
>   Matthew Buckett, VLE Developer, LTG, Oxford University Computing Services
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140425/7358bc6e/attachment.html