Hilaire What we do and it is working for a lot of projects. I used the launcher to grab an image built from a CI based on a release Pharo image and a configuration of my project so that I do not have to wait. Pharo50 + ConfigurationOf/BaselineOf + jenkins => image PharoLauncher + click => download image For example for Pillar Jenkins builds 40 stable / dev 50 stable / dev 60 stable / dev based on my configuration and I pick the ones I want to work. When I commit..... bingo the CI sees it and create a new ones with the tests run :) Stef
Building the image from the shell is what I do for DrGeo release. For development environment it is more in flux but likely should be done. Any recommended reading on that specific point?
Hilaire
Le 18/02/2017 à 12:54, Pierce Ng a écrit :
Nowadays we are encouraging building images from configs from the CLI or programmatically, no? Some have mentioned starting with a freshly baked image every day. In my case, I took a fresh image, into which GitFileTree loaded cleanly, then loaded my working stuff through their configs that I've been maintaining.
-- Using Opera's mail client: http://www.opera.com/mail/