Pharo 3.0 is now properly tracked on github - https://github.com/pharo-project/pharo-core - the update messages are properly shown - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf...
Hi, Nice. Is there a way to use this infrastructure for other projects? Cheers, Doru On May 18, 2013, at 2:31 AM, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
- https://github.com/pharo-project/pharo-core - the update messages are properly shown - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf...
-- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."
Cool. On 18 May 2013, at 02:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
- https://github.com/pharo-project/pharo-core - the update messages are properly shown - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf...
Thanks for all this work. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
On 18 May 2013 01:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
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. frank
On 2013-05-18, at 10:53, Frank Shearar <frank.shearar@gmail.com> wrote:
On 18 May 2013 01:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
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.
On 18 May 2013 10:04, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-05-18, at 10:53, Frank Shearar <frank.shearar@gmail.com> wrote:
On 18 May 2013 01:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
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
On 18 May 2013 09:53, Frank Shearar <frank.shearar@gmail.com> wrote:
On 18 May 2013 01:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
Nice! How do you track the changes? From Jenkins as a build step?
What fileout format are you using? It looks like a custom job. (It's not chunk format or Filetree or gst style.) Although I'm not necessarily complaining here, since I have every intention of developing yet another fileout format. It turns out that Monticello can easily paper over the details of your fileout format - I have a (currently stalled because of unrelated issues) project that can load both fileout and Filetree formatted code from a GitHub repository, and from the perspective of the user, it's just Monticello. One request though - make a means of identifying the format please? At the moment FileTree puts a .filetree file in the repo, for instance. Perhaps if there are enough different filesystem formats we'll need to gather round and settle on a common identifier (.fileout-format, containing a symbol describing the format, or something), but at least today having a marker file means that a loader can easily figure out how to load the code. frank frank
On 18 May 2013 02:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
- https://github.com/pharo-project/pharo-core - the update messages are properly shown - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf...
You are my hero! Now can we have same for VM sources? I would really love to simplify a process of changing VM by simply modifying file either on disk (in platform sources) or in image (VMMaker & friends) and then do git ci -m "new fix/feature integrated" :) -- Best regards, Igor Stasenko.
On 2013-05-19, at 03:23, Igor Stasenko <siguctua@gmail.com> wrote:
On 18 May 2013 02:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
- https://github.com/pharo-project/pharo-core - the update messages are properly shown - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf...
You are my hero! Now can we have same for VM sources? I would really love to simplify a process of changing VM by simply modifying file either on disk (in platform sources) or in image (VMMaker & friends) and then do
git ci -m "new fix/feature integrated"
well it works only 1 way right now. I have not implemented any mapping from my fileformat to monticello (even though it shouldn't be that hard).
On 22 May 2013 10:11, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-05-19, at 03:23, Igor Stasenko <siguctua@gmail.com> wrote:
On 18 May 2013 02:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
- https://github.com/pharo-project/pharo-core - the update messages are properly shown - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf... - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf...
You are my hero! Now can we have same for VM sources? I would really love to simplify a process of changing VM by simply modifying file either on disk (in platform sources) or in image (VMMaker & friends) and then do
git ci -m "new fix/feature integrated"
well it works only 1 way right now. I have not implemented any mapping from my fileformat to monticello (even though it shouldn't be that hard).
You could take a look at Filetree's reader (MCFileTreeStReader, IIRC). Your fileout format's pretty similar. frank
participants (5)
-
Camillo Bruni -
Frank Shearar -
Igor Stasenko -
Sven Van Caekenberghe -
Tudor Girba