Re: [Pharo-project] jenkins mac cogvm misses os process?
On Sep 8, 2011, at 3:57 PM, Sean P. DeNigris wrote:
Esteban Lorenzano wrote:
yeah... but you should be using https://ci.lille.inria.fr/pharo/view/Cog/job/Cog-Mac-Cocoa-blessed/
Ha ha, okay I'm glad I know now, but do we need both? It seems confusing.
There are a lot of things that are very confusing. We need to simplify, radically. (and yes, even discontinue things that used to work. Just because someone once did a Plugin (Klatt comes to mind...), does not mean that we need to support if forever.
I am reporting cocoa problems *and* using Carbon until the plugin issues are worked out. Last I checked OSP and TestOSA were not working in Cog Cocoa. In fact, TestOSA
I do not even know what TestOSA is. Do we really need it? Marcus -- Marcus Denker -- http://marcusdenker.de
Marcus Denker-4 wrote:
I do not even know what TestOSA is. Do we really need it?
It is for Applescript. I use it all the time, but may be the only one :) -- View this message in context: http://forum.world.st/jenkins-mac-cogvm-misses-os-process-tp3798359p3798935.... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
El 08/09/2011, a las 11:08a.m., Marcus Denker escribió:
On Sep 8, 2011, at 3:57 PM, Sean P. DeNigris wrote:
Esteban Lorenzano wrote:
yeah... but you should be using https://ci.lille.inria.fr/pharo/view/Cog/job/Cog-Mac-Cocoa-blessed/
Ha ha, okay I'm glad I know now, but do we need both? It seems confusing.
There are a lot of things that are very confusing. We need to simplify, radically. (and yes, even discontinue things that used to work. Just because someone once did a Plugin (Klatt comes to mind...), does not mean that we need to support if forever.
yes... the "blessed" cocoa jenkins branch was born because I did not bring with me my computer to esug, and, the fixes Igor and I made then needed to be commited and built... so, Igor created that set of builds. But now, I think that set of jobs are a positive thing, because I use the continuous integration service (jenkings) as a "integration" step. That means: I use Cog-Mac-Cocoa, etc. to test the integration of my changes with others (that's how I discover the BYTES_PER_WORLD problem we have been discussing, for instance). Jenkings is a development tool, so it is understandable if is a little confusing for non-developers, but we also can improve (a little bit) understanding there, by adding some explanation to experimental/nonstable jobs (I already added one to Cog Mac Cocoa) What we really need is to provide (in pharo page) a UNIQUE link to the stable VM we are going to promote. cheers, Esteban
participants (3)
-
Esteban Lorenzano -
Marcus Denker -
Sean P. DeNigris