On Fri, Oct 24, 2014 at 12:50 AM, Luc Fabresse <luc.fabre...@gmail.com> wrote:
> Hi, > > >> Note that zeroconf handlers allow you to build images incrementally (the >> image is saved after each build), which is way faster than always starting >> from scratch. >> > > what are zeroconf "handlers"? > the things you get in the list when you do ./pharo someimage.image --list So "save" is one. There is one in here if you like a sample. https://github.com/philippeback/Bubble > because I use zeroconf to rebuild images and it is slow because it > downloads the vm, the image, the mcz then installing, ... > did I missed something? > No, but as my full build takes half an hour on a powerful box, this is not practical to do like that. So: CI JOB 1 (half an hour, every once in a while) ----------- - get pharo - get image - build "baseworker" image with standard packages etc CI JOB2 (whenever a commit is done in git, lasts a minute max) ---------- - take baseworker - pull from repo - build user code upon the base worker HTH Phil > > thx, Sven and Esteban, I like reading development and deployment processes > from experienced people! > > #Luc > > >> >> > After a year o Pharo development I think I'm ready to embrace a CI >> > server (I already use scripts to build images), but I think I will >> > move all my repositories to git before. >> >> These are orthogonal decisions, most CI jobs on the Pharo contribution >> server run against StHub. >> >> > However, my remote server provisioning is still manual, and too >> > rudimentary even for my own taste. If I could speed up this, I would >> > deliver features faster to my customers. Now everything runs inside a >> > two week sprint window. >> >> I am not into provisioning myself, but more automation is always good, >> though sometimes setting up and maintaining all these things takes a lot of >> time as well. >> >> > Regards, >> > >> > Esteban A. Maringolo >> > <filelocator.png> >> >> >> >
