[Pharo-project] About a system to build image
Hi all, I would really like that we start to think about a build server. ie a system that starts with an image and a package list and run the test. Here is a list of paths - using Installer - using Sake (I have to have a look at it). - DevImageCreator Do you have other pointers? Stef
On Wed, 2008-07-02 at 11:58 +0200, Stéphane Ducasse wrote:
Hi all,
I would really like that we start to think about a build server. ie a system that starts with an image and a package list and run the test.
Here is a list of paths - using Installer - using Sake (I have to have a look at it). - DevImageCreator
Do you have other pointers?
No, but I use Installer for my stuff. I take an official image, file in patches and Installer. On top of that I load all packages with Installer and save the image. The configuration and the tests are provided as a startup script to the image. That works all quite well. I would like to see that we use a universe to feed a build server. Then we have another reason to maintain a universe :) and we could enhance universe to include information about the combinations that work. Norbert
No, but I use Installer for my stuff. I take an official image, file in patches and Installer.
do you have a script for that?
On top of that I load all packages with Installer and save the image. The configuration and the tests are provided as a startup script to the image. That works all quite well.
could you should us a typical script
I would like to see that we use a universe to feed a build server. Then we have another reason to maintain a universe :) and we could enhance universe to include information about the combinations that work.
Yes this would be good. We will have a look at Sake.
Norbert
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, Jul 2, 2008 at 11:58 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I would really like that we start to think about a build server. ie a system that starts with an image and a package list and run the test.
Here is a list of paths - using Installer - using Sake (I have to have a look at it). - DevImageCreator
Currently, DevImageCreator is a bash script which uses Installer and its Universe back-end. I've already dialoged with Keith about Sake and its use for dev-images. I will let you know. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
On Wed, 2008-07-02 at 12:26 +0200, Stéphane Ducasse wrote:
No, but I use Installer for my stuff. I take an official image, file in patches and Installer.
do you have a script for that?
Yes, I have a handful of scripts but they are rather not very interesting. It's not that magic. If have a repository of all used packages on disk. Then I file in a static version of Installer.st. Then I use Installer to upgrade itself from the repository. After that I have e.g. whooka := Installer monticello directory: ( FileDirectory on: '/opt/whooka/repository/' ). whooka install: 'DynamicBindings-gc.7'. That should use a universe package which then installs the package and its dependents. Multiple entries allow you to install any combination of packages even if they are not combined in the universe that way. Additional information about where to get the test and which to run could be use- ful. You can put information about what to test somewhere and a mechanism creates a file like the snippet above. The files could be numbered so it could act like a queue. I don't think you need much more than that. The hard part is IMHO if a debugger is opened somewhere due an error misconfiguration. Then everything will go stale. I hope there is an easy way to prevent that and make the test fail. The last resort would be to timeout a test and kill the image, marking the test failed.
On top of that I load all packages with Installer and save the image. The configuration and the tests are provided as a startup script to the image. That works all quite well.
could you should us a typical script
I use it to configure seaside (Session class, Root class and database credentials). In the simplest case it would just invoke the test runner and lets all tests run. It doesn't even have to be an extra script. It could be the last lines in the above script. Norbert
I would like to see that we use a universe to feed a build server. Then we have another reason to maintain a universe :) and we could enhance universe to include information about the combinations that work.
Yes this would be good. We will have a look at Sake.
Norbert
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Damien Cassou -
Norbert Hartl -
Stéphane Ducasse