[Cog] New builds available on Jenkins server

>  
> Hello,
>
> during last couple of weeks i was busy migrating migrating VM jobs
> from Hudson server to more up to date Jenkins server
> and creating a jobs for running tests on newly built VMs.
>
> The new location for built VMs are https://ci.lille.inria.fr/pharo/view/Cog/
>
> I disabled the old jobs on Hudson server
> (https://pharo-ic.lille.inria.fr/hudson/view/Cog/)
> and also put a comment where they moved.
>
>
> So, from now all VMs which are built on Jenkins server will be
> automatically tested.
>
> If you go to jenkins page, you could see that each job , like StackVM-Unix
> has a parallel job named StackVM-Unix Tests , which runs tests after
> successful build of corresponding VM.
>
> The image which is used to run tests is Pharo 1.4. latest build (can
> be found on same server -
> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/)
>
> So, in this way we have a streamlined continuous integration setup,
> which tests every possible combination(s) of VMs and latest Pharo
> image,
> so we can easily track regressions as well as different behavior
> between platforms (ideally, there should be none ;))
>
> Details about new builds:
>  - it is a merge with VMMaker.oscog-eem.115 which contains an
> important fix for #become: primitive
>
> With this fix, i could say that Cog VMs are much stable!
>
> Problems, not yet solved:
>
> Windows:
>  - there is no windows jobs yet, because we're still having problems
> with windows slave (it is inaccessible right now), but once it will
> work, i will add jobs for windows as well.
>
> Mac Cocoa builds:
> - i migrated the cocoa builds to jenkins server as well, but it is not
> yet using an updated verison of sources (we have to wait till Esteban
> will sync sources)
> - also those VMs cannot run tests because command-line interface for
> them is severely broken now :(
>
>
>  

>
> Hi Igor,
>
> The latest Carbon Cog VM fails to run in OS X 10.5.8. Same symptoms I
> reported on thread "About Cocoa VMs" on 8/7. I guess the tweaks done by
> Esteban on the Cocoa VM are needed here too.
>
> Besides, it would be great to have a better filename for the final artifact.
> 'CogVM.zip' and 'CogVM.app' will clash all the time. It would be better to
> include Carbon/Cocoa and a timestamp or version number.
>

> Cheers,
> Juan Vuletich
>
> Igor Stasenko wrote:
>>
>>  Hello,
>>
>> during last couple of weeks i was busy migrating migrating VM jobs
>> from Hudson server to more up to date Jenkins server
>> and creating a jobs for running tests on newly built VMs.
>>
>> The new location for built VMs are
>> https://ci.lille.inria.fr/pharo/view/Cog/
>>
>> I disabled the old jobs on Hudson server
>> (https://pharo-ic.lille.inria.fr/hudson/view/Cog/)
>> and also put a comment where they moved.
>>
>>
>> So, from now all VMs which are built on Jenkins server will be
>> automatically tested.
>>
>> If you go to jenkins page, you could see that each job , like StackVM-Unix
>> has a parallel job named StackVM-Unix Tests , which runs tests after
>> successful build of corresponding VM.
>>
>> The image which is used to run tests is Pharo 1.4. latest build (can
>> be found on same server -
>> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/)
>>
>> So, in this way we have a streamlined continuous integration setup,
>> which tests every possible combination(s) of VMs and latest Pharo
>> image,
>> so we can easily track regressions as well as different behavior
>> between platforms (ideally, there should be none ;))
>>
>> Details about new builds:
>>  - it is a merge with VMMaker.oscog-eem.115 which contains an
>> important fix for #become: primitive
>>
>> With this fix, i could say that Cog VMs are much stable!
>>
>> Problems, not yet solved:
>>
>> Windows:
>>  - there is no windows jobs yet, because we're still having problems
>> with windows slave (it is inaccessible right now), but once it will
>> work, i will add jobs for windows as well.
>>
>> Mac Cocoa builds:
>> - i migrated the cocoa builds to jenkins server as well, but it is not
>> yet using an updated verison of sources (we have to wait till Esteban
>> will sync sources)
>> - also those VMs cannot run tests because command-line interface for
>> them is severely broken now :(
>>
>>
>>
>
>