Re: [MirageOS-devel] Deployment scripts / hack

2015-11-11 Thread Richard Mortier
PRs sent. Probably useful to double-check I didn't get over-enthusiastic... :) I left the `config.ml` files in place so that the `xen/` subdirs remain to make it easy to recover any specific unikernel. On 11 November 2015 at 02:11, Richard Mortier wrote: > Will do unless someone beats me to the

Re: [MirageOS-devel] Deployment scripts / hack

2015-11-10 Thread Richard Mortier
Will do unless someone beats me to the commit :) On 11 Nov 2015 1:53 a.m., "Thomas Gazagnaire" wrote: > > (Aside: Why did we decide we needed all past images in the current > > checkout of the deployment repos anyway?) > > just delete the old images. We certainly don't need to keep all of them in

Re: [MirageOS-devel] Deployment scripts / hack

2015-11-10 Thread Thomas Gazagnaire
> (Aside: Why did we decide we needed all past images in the current > checkout of the deployment repos anyway?) just delete the old images. We certainly don't need to keep all of them in the current checkout. ___ MirageOS-devel mailing list MirageOS

[MirageOS-devel] Deployment scripts / hack

2015-11-10 Thread Richard Mortier
Hi; It has been noticed that one of the issues with the current site deployment process (push Travis built Xen VM images into a GitHub repo, run cron jobs to periodically pull that repo to the deployment machine, have a post-merge.hook that deploys when the deployment repo is determined to have be