Oops. Sorry for creating confusions.
Doru
On Jul 25, 2013, at 1:55 PM, Igor Stasenko wrote:
> On 25 July 2013 12:05, Tudor Girba wrote:
>> The workaround at the image level was needed only until we got the VM
>> working. The details about the workaround are here:
>> https://pharo.fogbugz.com/
Hi Norbert,
In Moose, the configuration also contains a little package that comes with
development tools. Among these development tools we have a couple of
Moose-specific command lines.
You can see a description here:
http://www.tudorgirba.com/blog/moose-4-8-on-jenkins
Cheers,
Doru
On Jul 25
I meant stable, but given that I thought Norbert needs to update his local
copy, I said "latest stable". Confusing :)
Doru
On Jul 25, 2013, at 2:00 PM, Guillermo Polito wrote:
> Something I do not understand: "Latest stable" means latest or stable ? :).
> More specifically, How did you downl
2013/7/25 Camillo Bruni
>
> On 2013-07-25, at 17:10, Norbert Hartl wrote:
>
> > Cami,
> >
> > thanks for the snippet. The commandline handler for tests is a super
> replacement for one part of my snippet. But how do you do the lint tests?
>
> ah sorry, didn't see that last line. I didn't add sup
On 2013-07-25, at 17:10, Norbert Hartl wrote:
> Cami,
>
> thanks for the snippet. The commandline handler for tests is a super
> replacement for one part of my snippet. But how do you do the lint tests?
ah sorry, didn't see that last line. I didn't add support for that, so I guess
you're st
Cami,
thanks for the snippet. The commandline handler for tests is a super
replacement for one part of my snippet. But how do you do the lint tests?
Norbert
Am 25.07.2013 um 16:54 schrieb Camillo Bruni :
> You use the built-in command line tools and no longer .st files.
>
> Pointers:
> =
You use the built-in command line tools and no longer .st files.
Pointers:
=
curl get.pharo.org | bash
./pharo Pharo.image --help
./pharo Pharo.image --list
./pharo Pharo.image test --help
# everything should be pretty self explaining
A typical script looks like this on jenkins:
I'm close to having ported all of our projects to pharo 2.0. Now I'm asking
myself what would be a proper setup to run my jenkins build scripts. With
RPackage there are more packages in the system then before and in the jenkins
scripts you need to invoke
HDTestReport forPackages: #( …)
In 1.4
>>
>>
>> There was Lukas' repository before, and we just loaded that on the build
>> server
>> Then this was down for some weeks and we put it here:
>>
>> http://www.squeaksource.com/PharoHudson.html
>>
>> then we did put it in the image by default and we changed it for the
>> FilesSyst
When I finish the catalog and the first release of the SystemLogger
I will work on the management of Pharo using Metacello
I will not do anything beside Morph cleaning because I want to make progress on
a
minimal image.
Stef
On Jul 25, 2013, at 2:50 PM, Marcus Denker wrote:
>
> On Jul 25,
Am 25.07.2013 um 14:50 schrieb Marcus Denker :
>
> On Jul 25, 2013, at 12:03 PM, Norbert Hartl wrote:
>
>> I try to figure out where is the home project location of
>>
>> HudsonBuildTools20
>>
>> I can only see it in pharo20/pharoInbox
>>
>>
>
>
>
> There was Lukas' repository before, a
Am 25.07.2013 um 14:50 schrieb Marcus Denker :
>
> On Jul 25, 2013, at 12:03 PM, Norbert Hartl wrote:
>
>> I try to figure out where is the home project location of
>>
>> HudsonBuildTools20
>>
>> I can only see it in pharo20/pharoInbox
>>
>>
>
>
>
> There was Lukas' repository before, a
On Jul 25, 2013, at 12:03 PM, Norbert Hartl wrote:
> I try to figure out where is the home project location of
>
> HudsonBuildTools20
>
> I can only see it in pharo20/pharoInbox
>
>
There was Lukas' repository before, and we just loaded that on the build server
Then this was down for som
Something I do not understand: "Latest stable" means latest or stable ? :).
More specifically, How did you download it?
Because as far as I knew it was not fixed by Esteban in the VM... But maybe
one of the latest merges with Eliot's branch fixed it...
On Thu, Jul 25, 2013 at 1:55 PM, Igor Stase
On 25 July 2013 12:05, Tudor Girba wrote:
> The workaround at the image level was needed only until we got the VM
> working. The details about the workaround are here:
> https://pharo.fogbugz.com/f/cases/10395/
>
> I was sure that in the meantime, the problem was solved in the VM as well,
> but I
The workaround at the image level was needed only until we got the VM
working. The details about the workaround are here:
https://pharo.fogbugz.com/f/cases/10395/
I was sure that in the meantime, the problem was solved in the VM as well,
but I cannot trace that information. Perhaps it is not. Este
I try to figure out where is the home project location of
HudsonBuildTools20
I can only see it in pharo20/pharoInbox
Norbert
Do you know details of the problem. It is always good to now.
Norbert
Am 25.07.2013 um 09:08 schrieb Tudor Girba :
> This was a problem that we also had (when working in Moose), and Esteban
> fixed it (first the workaround in the image, and then in the VM). We are
> using this VM since some m
On Jul 25, 2013, at 9:08 AM, Tudor Girba wrote:
> This was a problem that we also had (when working in Moose), and Esteban
> fixed it (first the workaround in the image, and then in the VM). We are
> using this VM since some months now and the problem did not resurface.
>
> That is why I know
This was a problem that we also had (when working in Moose), and Esteban
fixed it (first the workaround in the image, and then in the VM). We are
using this VM since some months now and the problem did not resurface.
That is why I know it is fixed in the latest stable PharoVM.
Cheers,
Doru
On T
Doru,
I'm sorry but I was mistaken somehow. I tried always to use the newest VM. I
just downloaded a new vm a few minutes ago and now I cannot reproduce the
problem anymore. That doesn't mean it won't appear anymore but I'll work with
the pharo vm and see if it comes back.
thanks,
Norbert
Am
21 matches
Mail list logo
