On 18 May 2013 10:04, Camillo Bruni <[email protected]> wrote: > > On 2013-05-18, at 10:53, Frank Shearar <[email protected]> wrote: > >> On 18 May 2013 01:31, Camillo Bruni <[email protected]> wrote: >>> Pharo 3.0 is now properly tracked on github >>> >>> - https://github.com/pharo-project/pharo-core >> >> Nice! How do you track the changes? From Jenkins as a build step? >> >> Squeak doesn't do this yet, mainly because I've not got around to >> doing it. Because we don't use slices (maybe we should...) I'd >> pondered using a webhook off the squeaksource installation. > > It uses the FileSystem-ST that maps packages/classes/methods to an internal > FileSystem which can be easily written to disk: > > Gofer new > smalltalkhubUser: 'dh83' project: 'FileSystemST'; > package: 'ConfigurationOfFileSystemST'; > load. > > (Smalltalk at: #ConfigurationOfFileSystemST) loadDevelopment. > > FileSystem st root copyAllTo: 'pharo-core' asFileReference.
OK, so you could do have a job that did something like * take base image * check out pharo-core * update it * save updated image * run that script to change pharo-core * commit and push * run tests (Maybe with a slightly different ordering in the steps.) You don't even need to make Jenkins do anything that way! (You just have to store the GitHub API tokens somewhere, maybe in an environment variable.) frank
