Smalltalk › Pharo › Pharo Smalltalk Users

What is the project repository for ci build tools

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

NorbertHartl

What is the project repository for ci build tools

I try to figure out where is the home project location of

HudsonBuildTools20

I can only see it in pharo20/pharoInbox

Norbert

Marcus Denker-4

Re: What is the project repository for ci build tools

On Jul 25, 2013, at 12:03 PM, Norbert Hartl <[hidden email]> 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 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 FilesSystem refactoring
(maybe other changes?) that where specific to Pharo.

We need to improve how to merge to and from external repositories, we now use a lot
(Opal, Athens, Nativboost, SpecDebuggers) and it gets quite hard to manage.

Marcus

NorbertHartl

Re: What is the project repository for ci build tools

Am 25.07.2013 um 14:50 schrieb Marcus Denker <[hidden email]>:

>
> On Jul 25, 2013, at 12:03 PM, Norbert Hartl <[hidden email]> 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 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 FilesSystem refactoring
> (maybe other changes?) that where specific to Pharo.
>

OMG I was just too stupid to see that it is already in the image and my older jenkins setup just overwrote it with an older/inappropriate version.

> We need to improve how to merge to and from external repositories, we now use a lot
> (Opal, Athens, Nativboost, SpecDebuggers) and it gets quite hard to manage.

Agreed. What annoys me most is the chaos in repositories we got from Lukas server instability then squeaksource instability then short time usage of squeaksource3 and now smalltalkhub. There are so much repositories out there that look nearly the same. So, everyone of you which knows some of the repositories should either shut the obsolete ones down or where possible add a comment with a pointer to the actual repository.

Norbert

NorbertHartl

Re: What is the project repository for ci build tools

In reply to this post by Marcus Denker-4

Am 25.07.2013 um 14:50 schrieb Marcus Denker <[hidden email]>:

btw. what is pharo on the ci using in the script. HDTestReport works for me. HDLintReport invoked this way

HDLintReport runPackages: #( 'PKG1' ….)

produces files without any issues but the entries for each source file are included in the produced file. Any ideas? Do you use coverage report on the ci. I didn't noticed any. And last but not least the change in using RPackage one needs to add _every_ package to the tools. What process do you use to collect the package names for tests, lint,…

thanks,

Norbert

Stéphane Ducasse

Re: What is the project repository for ci build tools

In reply to this post by Marcus Denker-4

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 <[hidden email]> wrote:

Stéphane Ducasse

Re: What is the project repository for ci build tools

In reply to this post by NorbertHartl

>>
>>
>> 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 FilesSystem refactoring
>> (maybe other changes?) that where specific to Pharo.
>>
> OMG I was just too stupid to see that it is already in the image and my older jenkins setup just overwrote it with an older/inappropriate version.
>
>> We need to improve how to merge to and from external repositories, we now use a lot
>> (Opal, Athens, Nativboost, SpecDebuggers) and it gets quite hard to manage.
>
> Agreed. What annoys me most is the chaos in repositories we got from Lukas server instability then squeaksource instability then short time usage of squeaksource3 and now smalltalkhub. There are so much repositories out there that look nearly the same. So, everyone of you which knows some of the repositories should either shut the obsolete ones down or where possible add a comment with a pointer to the actual repository.

Yes I started to do that systematically.
And we should all continue. Each time you need something from Squeaksource.
We should migrate it to SmalltalkHub.

>
> Norbert