Damien: Is there some guide to do the same in a private environment? I is... using an HTTP/FTP/Git server as the monticello repo (SmalltalkHub seems overkill).
Kilon: I guess the main prerequisite is to have all the Monticello packages of your classes properly configured, and also the Metacello stuff in line (ConfigurationOf...). Then it is a matter of setting up a new image through command line loading the needed Metacello versions and then your own. You can do this in the context of a CI server or with a fresh image + cmdline in your own computer. Regards! Esteban A. Maringolo 2013/9/11 Damien Cassou <damien.cas...@gmail.com> > On Wed, Sep 11, 2013 at 10:12 AM, kilon <theki...@yahoo.co.uk> wrote: > > So what the best way to ensure that I have the latest version of pharo ? > > > what many of do is to let a continuous integration server build your > application on top of the latest Pharo everyday. So, you would have > to: > > - push your code somewhere public (e.g., smalltalkhub) > - write a configuration for your application (read the metacello > chapter of this book http://rmod.lille.inria.fr/deepIntoPharo/) > - register at https://ci.inria.fr/ > - ask to be a member of the pharo-contribution project on > https://ci.inria.fr/ > - create a new job by cloning > https://ci.inria.fr/pharo-contribution/view/Helper/job/JobTemplate/ > > And let Jenkins to the job. Everyday, you start your work by > downloading the newest image built by Jenkins. I advise you to use the > Pharo launcher (https://ci.inria.fr/pharo-contribution/job/PharoLauncher) > which downloads images directly from Jenkins. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >
