On Sun, Jan 20, 2013 at 8:57 AM, Tudor Girba <tudor@tudorgirba.com> wrote:

Hi Usman,

The script is not so dramatic.

Of course, it shouldn't be dramatic but since I was trying to clone the integration server, a clone of the current configuration would have helped a lot.

There were some issues regarding the use of CogVM and literals, so I had to use the latest version of NBCog (http://pharo.gforge.inria.fr/ci/vm/nbcog/linux/NBCog-linux-latest.zip).

So I have job that builds a Moose image on INRIA server...

https://ci.inria.fr/moose/

FAMIX tests are green, there are three failing tests in package names with Moose keyword.

Let me know if you find any errors.

The next step is to be able to build a one-click image of Moose and a job for the unit test report.

Usman

The more critical thing is to have the builder code locally (https://github.com/renggli/builder). But, before going there, I want to look into what Camillo has done to have essentially only Smalltalk code in the scripts.

Cheers,
Doru

On Jan 16, 2013, at 7:05 PM, Usman Bhatti <usman.bhatti@gmail.com> wrote:

> Hello Doru,
>
> I am in the process of configuring a jenkins job for Moose on the server at INRIA. I was wondering if I could simply import the job that you created on ci.moosetechnology.org instead of constructing a new job from scratch, like that I wont need to understand the intricacies of manipulating one-click images on the jenkins server. Apparently, there is a way to copy/clone jenkins jobs through a config.xml file. So, if you could provide me this file for latest-moose-dev job on the moose ci, I should be able to replicate the job on the INRIA server.
>
> Otherwise, you can provide me the text for the job and I will try to manually fit in the elements in the server.
>
> regards,
> Usman

--
www.tudorgirba.com

"To lead is not to demand things, it is to make them happen."