July 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How are you doing your jenkins build scripts?

by Norbert Hartl

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 <camillobruni(a)gmail.com>: > 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: > ========================================================================== > wget --quiet -O - get.pharo.org/20+vm | bash > > ./pharo Pharo.image save $JOB_NAME --delete-old > ./pharo $JOB_NAME.image --version > version.txt > > REPO=http://www.squeaksource.com/MetacelloRepository > ./pharo $JOB_NAME.image config $REPO ConfigurationOf$JOB_NAME --install=$VERSION --groups='All OS',Tests > ./pharo $JOB_NAME.image test --junit-xml-output "$JOB_NAME.*" > > zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes > ========================================================================== > > > On 2013-07-25, at 16:36, Norbert Hartl <norbert(a)hartl.name> wrote: > >> 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 I just added them manually. Using 2.0 makes this too cumbersome to deal with. So I need to figure out the amount of tests programmatically. The first I came up with (and that would solve my common use case) is something like >> >> >> myPrefix := 'Emcee-' >> myPackages := RPackage organizer packages select: [:each| each name beginsWith: myPrefix ]. >> packagesWithTests := myPackages select: [ :package| package classes anySatisfy: [ :cls| cls includesBehavior: TestCase ] ]. >> packagesNamedTest := myPackages select: [ :each| each name includesSubstring: '-Tests-' ]. >> testPackages := packagesWithTests union: packagesNamedTest. >> packages := myPackages difference: packagesNamedTest. >> >> HDTestReport runPackages: (testPackages collect: #name). >> HDLintReport runPackages: (packages collect: #name) >> >> So I like to ask how you guys are doing it. Thanks in advance for your answers. >> >> Norbert > >

July 25, 2013

Re: [Pharo-users] How are you doing your jenkins build scripts?

by Camillo Bruni

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: ========================================================================== wget --quiet -O - get.pharo.org/20+vm | bash ./pharo Pharo.image save $JOB_NAME --delete-old ./pharo $JOB_NAME.image --version > version.txt REPO=http://www.squeaksource.com/MetacelloRepository ./pharo $JOB_NAME.image config $REPO ConfigurationOf$JOB_NAME --install=$VERSION --groups='All OS',Tests ./pharo $JOB_NAME.image test --junit-xml-output "$JOB_NAME.*" zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes ========================================================================== On 2013-07-25, at 16:36, Norbert Hartl <norbert(a)hartl.name> wrote: > 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 I just added them manually. Using 2.0 makes this too cumbersome to deal with. So I need to figure out the amount of tests programmatically. The first I came up with (and that would solve my common use case) is something like > > > myPrefix := 'Emcee-' > myPackages := RPackage organizer packages select: [:each| each name beginsWith: myPrefix ]. > packagesWithTests := myPackages select: [ :package| package classes anySatisfy: [ :cls| cls includesBehavior: TestCase ] ]. > packagesNamedTest := myPackages select: [ :each| each name includesSubstring: '-Tests-' ]. > testPackages := packagesWithTests union: packagesNamedTest. > packages := myPackages difference: packagesNamedTest. > > HDTestReport runPackages: (testPackages collect: #name). > HDLintReport runPackages: (packages collect: #name) > > So I like to ask how you guys are doing it. Thanks in advance for your answers. > > Norbert

July 25, 2013

How are you doing your jenkins build scripts?

by Norbert Hartl

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 I just added them manually. Using 2.0 makes this too cumbersome to deal with. So I need to figure out the amount of tests programmatically. The first I came up with (and that would solve my common use case) is something like myPrefix := 'Emcee-' myPackages := RPackage organizer packages select: [:each| each name beginsWith: myPrefix ]. packagesWithTests := myPackages select: [ :package| package classes anySatisfy: [ :cls| cls includesBehavior: TestCase ] ]. packagesNamedTest := myPackages select: [ :each| each name includesSubstring: '-Tests-' ]. testPackages := packagesWithTests union: packagesNamedTest. packages := myPackages difference: packagesNamedTest. HDTestReport runPackages: (testPackages collect: #name). HDLintReport runPackages: (packages collect: #name) So I like to ask how you guys are doing it. Thanks in advance for your answers. Norbert

July 25, 2013

Re: [Pharo-users] What is the project repository for ci build tools

by StÃ©phane Ducasse

>> >> >> 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

July 25, 2013

Re: [Pharo-users] What is the project repository for ci build tools

by StÃ©phane Ducasse

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 <marcus.denker(a)inria.fr> wrote: > > On Jul 25, 2013, at 12:03 PM, Norbert Hartl <norbert(a)hartl.name> 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 > >

July 25, 2013

Re: [Pharo-users] What is the project repository for ci build tools

by Norbert Hartl

Am 25.07.2013 um 14:50 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > On Jul 25, 2013, at 12:03 PM, Norbert Hartl <norbert(a)hartl.name> 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. 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

July 25, 2013

Re: [Pharo-users] What is the project repository for ci build tools

by Norbert Hartl

Am 25.07.2013 um 14:50 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > On Jul 25, 2013, at 12:03 PM, Norbert Hartl <norbert(a)hartl.name> 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

July 25, 2013

Re: [Pharo-users] What is the project repository for ci build tools

by Marcus Denker

On Jul 25, 2013, at 12:03 PM, Norbert Hartl <norbert(a)hartl.name> 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

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Guillermo Polito

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 Stasenko <siguctua(a)gmail.com> wrote: > On 25 July 2013 12:05, Tudor Girba <tudor(a)tudorgirba.com> 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 cannot trace that information. Perhaps it is not. Esteban? > > > > Last time i discussed with Esteban about it, he said that he don't > knows where the problem in VM, > neither me. > > > > Cheers, > > Doru > > > > > > On Thu, Jul 25, 2013 at 9:13 AM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > >> > >> > >> On Jul 25, 2013, at 9:08 AM, Tudor Girba <tudor(a)tudorgirba.com> 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 it is fixed in the latest stable PharoVM. > >> > >> > >> Ok what igor is probably meaning is that we would prefer to get the > system > >> running without having to have a workaround at the image level. > >> > >> > >> Cheers, > >> Doru > >> > >> > >> On Thu, Jul 25, 2013 at 9:03 AM, Norbert Hartl <norbert(a)hartl.name> > wrote: > >>> > >>> 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 24.07.2013 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > >>> > >>> > Use the latest stable VM. It should solve the problem. > >>> > > >>> > Doru > >>> > > >>> > > >>> > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> > wrote: > >>> > > >>> >> > >>> >> > >>> >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse > >>> >> <stephane.ducasse(a)inria.fr>: > >>> >> > >>> >>> > >>> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> > >>> >>> wrote: > >>> >>> > >>> >>>> As I cannot work with the pharo VM right now > >>> >>> > >>> >>> what is the problem? > >>> >> > >>> >> I get the DNU SmallInteger>>add: all the time especially when using > >>> >> metacello (Using Versionner I get it nearly every attempt to > validate the > >>> >> configuration). This occurred already a few times on the list. > >>> >> > >>> >> > >>> >>> > >>> >>>> I'm back to use Eliots Cog. But If I open a more recent image it > >>> >>>> complains about my vm being to old. What does it really check in > order to > >>> >>>> complain? Some just version string/number parsing? Is it always > sever? > >>> >>>> > >>> >>>> Norbert > >>> >>> > >>> >>> > >>> >> > >>> > > >>> > -- > >>> > www.tudorgirba.com > >>> > > >>> > "Quality cannot be an afterthought." > >>> > > >>> > > >>> > >>> > >> > >> > >> > >> -- > >> www.tudorgirba.com > >> > >> "Every thing has its own flow" > >> > >> > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > > -- > Best regards, > Igor Stasenko. > >

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Igor Stasenko

On 25 July 2013 12:05, Tudor Girba <tudor(a)tudorgirba.com> 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 cannot trace that information. Perhaps it is not. Esteban? > Last time i discussed with Esteban about it, he said that he don't knows where the problem in VM, neither me. > Cheers, > Doru > > > On Thu, Jul 25, 2013 at 9:13 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> >> On Jul 25, 2013, at 9:08 AM, Tudor Girba <tudor(a)tudorgirba.com> 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 it is fixed in the latest stable PharoVM. >> >> >> Ok what igor is probably meaning is that we would prefer to get the system >> running without having to have a workaround at the image level. >> >> >> Cheers, >> Doru >> >> >> On Thu, Jul 25, 2013 at 9:03 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> 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 24.07.2013 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>> >>> > Use the latest stable VM. It should solve the problem. >>> > >>> > Doru >>> > >>> > >>> > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> > >>> >> >>> >> >>> >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse >>> >> <stephane.ducasse(a)inria.fr>: >>> >> >>> >>> >>> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)hartl.name> >>> >>> wrote: >>> >>> >>> >>>> As I cannot work with the pharo VM right now >>> >>> >>> >>> what is the problem? >>> >> >>> >> I get the DNU SmallInteger>>add: all the time especially when using >>> >> metacello (Using Versionner I get it nearly every attempt to validate the >>> >> configuration). This occurred already a few times on the list. >>> >> >>> >> >>> >>> >>> >>>> I'm back to use Eliots Cog. But If I open a more recent image it >>> >>>> complains about my vm being to old. What does it really check in order to >>> >>>> complain? Some just version string/number parsing? Is it always sever? >>> >>>> >>> >>>> Norbert >>> >>> >>> >>> >>> >> >>> > >>> > -- >>> > www.tudorgirba.com >>> > >>> > "Quality cannot be an afterthought." >>> > >>> > >>> >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- Best regards, Igor Stasenko.

July 25, 2013