[Building Sakai] Jenkins deployment issue

[Matthew Buckett]

We do have some local changes to make a maven artifact out of the
build. This allowed us to "easily" trigger jenkins jobs that would run
the built artifact and it provides a easy way to get the zip passed
between the jobs.

https://github.com/ox-it/wl-sakai/tree/master/pack-build

The better way would be to have the sakai plugin work as an aggregator
and creating an artifact as then it would require the hack of the
antrun plugin, but this is more work.

On 25 April 2014 15:49, Liu, Peter <peter.liu at yale.edu> wrote:
> Hi Mathew,
>
> Thanks a lot for your comment. At Yale, we try to set up a Jenkin's Build/deployment with artiFactory in a fully automatically way. Currently, we have encountered quiet few obstacles since the Size of Sakai are so big.
>
> Now, I am just wondering which institution has set up such a fully Jenkin's build/deploy environment.
>
> Thanks,
> Peter
>
> -----Original Message-----
> From: Matthew Buckett [mailto:matthew.buckett at oucs.ox.ac.uk]
> Sent: Friday, April 25, 2014 4:55 AM
> To: Liu, Peter
> Cc: sakai-dev; Neal Caidin
> Subject: Re: Jenkins deployment issue
>
> 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



-- 
  Matthew Buckett, VLE Developer, IT Services, University of Oxford