[Hudson] 1.2 build
Locked
 
|
Hi,
- the pharo 1.2 (and 1.1) full builds are now triggered by a successful build of the core images (failing tests are ok, failing builds do not trigger) - One-Click of full is now build automatically: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/20/artifact/PharoOneClick1.2.zip - just image and sources are available at this link https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/artifact/dev1.2.zip - tests are now run on 1.2 full. 24 are failing, of which 12 are from core: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/testReport/ Next step: - re-use the core images in the full image builds, do not update again. (saves 5 minutes build time) Later: - build all VMs from source automatically - run tests on MacOS and Windows in addition to linux (to validate the VM and to check that image side is working on all plattforms) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
Thank you Marcus.
Is it hard / possible to add test coverage ? Laurent
On Thu, Dec 16, 2010 at 12:11 PM, Marcus Denker <[hidden email]> wrote: Hi, |
|
|
In reply to this post by Marcus Denker-4
On Dec 16, 2010, at 1:06 PM, laurent laffont wrote: Thank you Marcus. problematic... when testing system level code, you soon run into meta-recursion (e.g. Array is used by the code used for doing test coverage). (we should really fix reflection as a concept... but that's more research and not engineering... I should continue with that). So this would only make sense on a package by package case. But there it can make sense, yes. What I want to add before test coverage is code-critique style checking. Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
On Dec 16, 2010, at 1:37 PM, Marcus Denker wrote:
And Camillo suggested we should set up this nice system for Pharo: (but this requires fully automated build of the VM from the source repository) Toon and Camillo are using this for Pinoccio. Which reminds me that the paper is finally available online: Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
In reply to this post by Marcus Denker-4
Great news!
I already updated the Moose build to be based on the current 1.2: http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuccessfulBuild/artifact/moose-on-pharo12/ Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. Cheers, Doru On 16 Dec 2010, at 12:11, Marcus Denker wrote: > Hi, > > - the pharo 1.2 (and 1.1) full builds are now triggered by a successful build of the core images (failing tests are ok, failing builds do not trigger) > - One-Click of full is now build automatically: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/20/artifact/PharoOneClick1.2.zip > - just image and sources are available at this link https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/artifact/dev1.2.zip > - tests are now run on 1.2 full. 24 are failing, of which 12 are from core: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/testReport/ > > > Next step: > > - re-use the core images in the full image builds, do not update again. (saves 5 minutes build time) > > Later: > - build all VMs from source automatically > - run tests on MacOS and Windows in addition to linux (to validate the VM and to check that image side is working on all plattforms) > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "Speaking louder won't make the point worthier." |
|
|
On 16 December 2010 17:25, Tudor Girba <[hidden email]> wrote:
> Great news! > > I already updated the Moose build to be based on the current 1.2: > http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuccessfulBuild/artifact/moose-on-pharo12/ > > > Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. > +1 > Cheers, > Doru > > > On 16 Dec 2010, at 12:11, Marcus Denker wrote: > >> Hi, >> >> - the pharo 1.2 (and 1.1) full builds are now triggered by a successful build of the core images (failing tests are ok, failing builds do not trigger) >> - One-Click of full is now build automatically: >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/20/artifact/PharoOneClick1.2.zip >> - just image and sources are available at this link https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/artifact/dev1.2.zip >> - tests are now run on 1.2 full. 24 are failing, of which 12 are from core: >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/testReport/ >> >> >> Next step: >> >> - re-use the core images in the full image builds, do not update again. (saves 5 minutes build time) >> >> Later: >> - build all VMs from source automatically >> - run tests on MacOS and Windows in addition to linux (to validate the VM and to check that image side is working on all plattforms) >> >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > > > -- Best regards, Igor Stasenko AKA sig. |
|
|
In reply to this post by Marcus Denker-4
On Dec 16, 2010, at 5:26 PM, Tudor Girba wrote: > Great news! > > I already updated the Moose build to be based on the current 1.2: > http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuccessfulBuild/artifact/moose-on-pharo12/ > > > Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. Ok, I will do that. In addition, it would be nice if the zip would contain inside some version number or date or something. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
Is the server building 1.1 or 1.1.1?
________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Marcus Denker [[hidden email]] Sent: Thursday, December 16, 2010 12:55 PM To: [hidden email] Cc: Moose-dev Moose Dev Subject: Re: [Pharo-project] [Hudson] 1.2 build On Dec 16, 2010, at 5:26 PM, Tudor Girba wrote: > Great news! > > I already updated the Moose build to be based on the current 1.2: > http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuccessfulBuild/artifact/moose-on-pharo12/ > > > Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. Ok, I will do that. In addition, it would be nice if the zip would contain inside some version number or date or something. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
In reply to this post by Marcus Denker-4
On Dec 16, 2010, at 7:06 PM, Schwab,Wilhelm K wrote: > Is the server building 1.1 or 1.1.1? 1.1.1 But I don't want to have that in the name of the Build Target, as this then would need to be renamed for 1.1.2 (and doing such point releases now has virtualy an overhead of 0, I should add). This will be better as soon as we add the version and update number as Adrian suggested. > > > ________________________________________ > From: [hidden email] [[hidden email]] On Behalf Of Marcus Denker [[hidden email]] > Sent: Thursday, December 16, 2010 12:55 PM > To: [hidden email] > Cc: Moose-dev Moose Dev > Subject: Re: [Pharo-project] [Hudson] 1.2 build > > On Dec 16, 2010, at 5:26 PM, Tudor Girba wrote: > >> Great news! >> >> I already updated the Moose build to be based on the current 1.2: >> http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuccessfulBuild/artifact/moose-on-pharo12/ >> >> >> Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. > > Ok, I will do that. In addition, it would be nice if the zip would contain inside some version number or date or something. > > Marcus > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
On Dec 16, 2010, at 7:17 PM, Marcus Denker wrote: > > On Dec 16, 2010, at 7:06 PM, Schwab,Wilhelm K wrote: > >> Is the server building 1.1 or 1.1.1? > > 1.1.1 > > But I don't want to have that in the name of the Build Target, as this then would need to be renamed for 1.1.2 > (and doing such point releases now has virtualy an overhead of 0, I should add). > The .zip should have an un-changing name for 1.1, too, so people can just download and get the latest *even* if we do a 1.1.2. But *inside* the zip, I would like to have more infos... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
Marcus,
What about an archive of previous releases? Is there any way to come back a year from now to get 1.1.1 or 1.2 as they were originally released? 1.1.1 might be unfair because it came long before you set up the server, but hopefully you see where I am going. It might be nice if the various releases were named in a way that someone could find them for use in debugging, etc. Bill ________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Marcus Denker [[hidden email]] Sent: Thursday, December 16, 2010 1:20 PM To: [hidden email] Development Subject: Re: [Pharo-project] [Hudson] 1.2 build On Dec 16, 2010, at 7:17 PM, Marcus Denker wrote: > > On Dec 16, 2010, at 7:06 PM, Schwab,Wilhelm K wrote: > >> Is the server building 1.1 or 1.1.1? > > 1.1.1 > > But I don't want to have that in the name of the Build Target, as this then would need to be renamed for 1.1.2 > (and doing such point releases now has virtualy an overhead of 0, I should add). > The .zip should have an un-changing name for 1.1, too, so people can just download and get the latest *even* if we do a 1.1.2. But *inside* the zip, I would like to have more infos... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
In reply to this post by Marcus Denker-4
On Dec 16, 2010, at 9:12 PM, Schwab,Wilhelm K wrote: > Marcus, > > What about an archive of previous releases? Yes, of course. We will continue to use gforge for keeping a copy of every official release *and* a core all 10-20 updates. These zip files will of course have the full version number in the file name. e.g. for 1.2, I will put the one-click beta on gforge this weekend (with a link on pharo-project.org) > Is there any way to come back a year from now to get 1.1.1 or 1.2 as they were originally released? 1.1.1 might be unfair because it came long before you set up the server, but hopefully you see where I am going. It might be nice if the various releases were named in a way that someone could find them for use in debugging, etc. > > Bill > > > > > ________________________________________ > From: [hidden email] [[hidden email]] On Behalf Of Marcus Denker [[hidden email]] > Sent: Thursday, December 16, 2010 1:20 PM > To: [hidden email] Development > Subject: Re: [Pharo-project] [Hudson] 1.2 build > > On Dec 16, 2010, at 7:17 PM, Marcus Denker wrote: > >> >> On Dec 16, 2010, at 7:06 PM, Schwab,Wilhelm K wrote: >> >>> Is the server building 1.1 or 1.1.1? >> >> 1.1.1 >> >> But I don't want to have that in the name of the Build Target, as this then would need to be renamed for 1.1.2 >> (and doing such point releases now has virtualy an overhead of 0, I should add). >> > > The .zip should have an un-changing name for 1.1, too, so people can just download and get the latest *even* > if we do a 1.1.2. > > But *inside* the zip, I would like to have more infos... > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
ok, I'm sold. Do you have a plan to advertise the Hudson server on the download page?
________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Marcus Denker [[hidden email]] Sent: Thursday, December 16, 2010 3:23 PM To: [hidden email] Subject: Re: [Pharo-project] [Hudson] 1.2 build On Dec 16, 2010, at 9:12 PM, Schwab,Wilhelm K wrote: > Marcus, > > What about an archive of previous releases? Yes, of course. We will continue to use gforge for keeping a copy of every official release *and* a core all 10-20 updates. These zip files will of course have the full version number in the file name. e.g. for 1.2, I will put the one-click beta on gforge this weekend (with a link on pharo-project.org) |
|
|
In reply to this post by Marcus Denker-4
On Dec 16, 2010, at 10:03 PM, Schwab,Wilhelm K wrote: > ok, I'm sold. Do you have a plan to advertise the Hudson server on the download page? Yes, I think as "daily build". So we have 1. Release 2. Latest unstable. That one lags ca. 10 updates to 3. daily build Where 1 and 2 are archived, 3 not (and can actually change even multiple times a day). > ________________________________________ > From: [hidden email] [[hidden email]] On Behalf Of Marcus Denker [[hidden email]] > Sent: Thursday, December 16, 2010 3:23 PM > To: [hidden email] > Subject: Re: [Pharo-project] [Hudson] 1.2 build > > On Dec 16, 2010, at 9:12 PM, Schwab,Wilhelm K wrote: > >> Marcus, >> >> What about an archive of previous releases? > > Yes, of course. We will continue to use gforge for keeping a copy of every official release *and* a core all 10-20 updates. > > These zip files will of course have the full version number in the file name. > > e.g. for 1.2, I will put the one-click beta on gforge this weekend (with a link on pharo-project.org) > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
|
|
Great!!
________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Marcus Denker [[hidden email]] Sent: Thursday, December 16, 2010 4:20 PM To: [hidden email] Subject: Re: [Pharo-project] [Hudson] 1.2 build On Dec 16, 2010, at 10:03 PM, Schwab,Wilhelm K wrote: > ok, I'm sold. Do you have a plan to advertise the Hudson server on the download page? Yes, I think as "daily build". So we have 1. Release 2. Latest unstable. That one lags ca. 10 updates to 3. daily build Where 1 and 2 are archived, 3 not (and can actually change even multiple times a day). |
|
|
In reply to this post by Marcus Denker-4
On 16/12/10 12:55 PM, Marcus Denker wrote:
> > Ok, I will do that. In addition, it would be nice if the zip would contain inside some version number or date or something. There's a link "See the list of available environment variables" in the configuration of each Hudson job. Part of the list is: ==== The following variables are available to shell scripts BUILD_NUMBER- The current build number, such as "153" BUILD_ID - The current build id, such as "2005-08-22_23-59-59" (YYYY-MM-DD_hh-mm-ss) JOB_NAME - Name of the project of this build, such as "foo" BUILD_TAG - String of "hudson-${JOBNAME}-${BUILD_NUMBER}". Convenient to put into a resource file, a jar file, etc for easier identification. WORKSPACE - The absolute path of the workspace. ==== |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |