On 02 Jan 2014, at 11:49, Norbert Hartl <norb...@hartl.name> wrote: > > Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaring...@gmail.com>: > >> Pharo as a community has support to use its CI server, among other >> goodies such as SmalltalkHub. >> >> But what if your code is not public and you want to have a central >> repository and continuous builds? >> >> Has anybody ever wrote a guide to develop with Pharo in the context of >> private development? >> >> So far I managed to work with a file based repo and a set of >> workspaces to create a new working image or to prepare it for >> deployment. But I want to automate it as much as I can. >> > I do what you want to do. I have a central server that I use for code storage > and for the CI builds. Have a look at [1]. There you can read how you can > easily create a http repository for monticello. I just create sub directories > for every project on my server and the rest just works. > The next step would be to install jenkins and add [2]. The jenkins server > then just uses the http repository you created before. > If you need help on this just ask.
I use filetree and bitbucket for my private projects, and I use also metacello to build with them. if you do not want to use file tree format, you can use ftp or even dropbox :) there is no need to make anything different on your private development than you do in your public ones. ah, and scripts from Lukas are very outdated (I mean, a LOT). is a lot easier to take http://ci.inria.fr/pharo-contribution (any job there) as an example on how to configure a jenkins job in few lines. > > Norbert > > [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ > [2] https://github.com/renggli/builder >
