Re: [Pharo-project] NativeBoost VM on Windows
On 23 October 2012 14:50, dimitris chloupis <thekilon@yahoo.co.uk> wrote:
you mean you will release them outside jenkins ?
no. I mean release on jenkins ;) Anything outside jenkins is not exists.
I already have a macos build back from september i think from jenkins. So I can wait. Windows build is the one I dont have at all and I need it too. Anyway thanks for the effort Igor.
________________________________ From: Igor Stasenko <siguctua@gmail.com> To: Pharo-project@lists.gforge.inria.fr; dimitris chloupis <thekilon@yahoo.co.uk> Sent: Tuesday, 23 October 2012, 15:48
Subject: Re: [Pharo-project] NativeBoost VM on Windows
On 23 October 2012 14:28, dimitris chloupis <thekilon@yahoo.co.uk> wrote:
macos lion builds are welcomed too ;)
yes, that already fixed, but waits for update (after i finish with windows).
________________________________ From: Igor Stasenko <siguctua@gmail.com> To: Pharo-project@lists.gforge.inria.fr Sent: Tuesday, 23 October 2012, 15:17 Subject: Re: [Pharo-project] NativeBoost VM on Windows
On 23 October 2012 13:30, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
Where do I find one? The one in oneclick distribution returns nil from NativeBoost platformId, and the one for win platform in "NativeBoost-Cog-VM" Jenkins platform doesn't seem to have any succesfully built versions...
I going to release new version(s) of win32 VMs very soon.
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
Just to be clear: - i can manually build all VMs with last & best fixes available.. but making those builds to be built automatically is completely different (and crazy/gory story). And this is what i am working on (and looks like i _almost_ nearly to finish it today). Almost, because you never know if it going to work on jenkins before you try .. and because we have crazy complexity with all metacello configs and git.. which also adds own mess to the soup. The point is , that if we cannot build VMs automatically, we dont have any artifact to propose to people: because they will be never able to reproduce it, because manual building process relies on intimate knowledge of a single person. -- Best regards, Igor Stasenko.
you mean you will release them outside jenkins ?
no. I mean release on jenkins ;) Anything outside jenkins is not exists.
Yes I love that statement Automated tasks to team complexity. Free our energy for non stupid tasks robots can do!!!
participants (2)
-
Igor Stasenko -
Stéphane Ducasse