September 2014 - Pharo-dev - lists.pharo.org

Rewrite rules doc?

by Yuriy Tymchuk

Hi guys. Is there any doc about rewrite rules besides https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… ? Uko

Sept. 2, 2014

Re: [Pharo-dev] Jenkins builds not properly preserving artifacts?

by Marcus Denker

On 02 Sep 2014, at 11:41, Tim Mackinnon <tim(a)testit.works> wrote: > Marcus - how do you navigate to that view from the Build #890 of PharoLauncher? When I click on the link you show - thats that output I first saw in the console from the list of builds for Pharo Launcher (which is what I was looking for) - and when I click on âBack To Projectâ it takes me to the 890 build results page - however if I was looking at build 889 - where on that page do I click to see that output? > It is not niceâ¦ But something is strange in the setup: it only runs on windows and does not show good names. The Pharo build looks better: https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-A-L/ No idea, needs to be configures somehowâ¦ Jenkins is not that âniceâ from the UI as it targets developers who get used to it somehow. > I think if I understand that - this would give the information we would expect - and then we can either document this, or maybe put some artefact in every build (via a script) that lets people easily navigate to see what a build was composed off (as it seems that the info is there). > > Tim > > On that page, > On 2 Sep 2014, at 09:14, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> The job is a matrix build... the outer job just triggers the matrix builds (see the link "default",), the log is there: >> >> https://ci.inria.fr/pharo-contribution/job/PharoLauncher/890/PHARO=30,VERSI… >> >> >> On Tue, Sep 2, 2014 at 12:41 AM, Tim Mackinnon <tim(a)testit.works> wrote: >> Guys - Iâve noticed that when a build completed on the Inria infrastructure, for a short time the console output correctly shows all the artefacts that were used to create that build - e.g. the slices loaded etc. However after a short time - the output then reverts to something like below (which isnât as useful): >> >> Started by upstream project " [8mha:AAAAqh+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8â¦. >> originally caused by: >> [URLTrigger] A change within the response URL invocation (log) >> Building remotely on pharo-contribution-winxp in workspace C:\builds\workspace\PharoLauncher >> >> Deleting project workspaceâ¦ done >> --- >> >> Iâve looked at a few other jobs (I noticed this for Pharo Launcher) and they seem the same. I think the jobs arenât configured properly? - As normally (at least in other languages like Java), the intent is that the console output reflects what was on the console when the job was run. I have a hunch that something is overwriting these files before they are archived away. >> >> As we donât seem to have other details of what went into a build job (which is another issue - I would expect the changes page for a build to also show this info in a better format). >> >> Do you think this could be fixed? >> >> tim >> >> >> >> >> -- >> -- >> Marcus Denker -- denker(a)acm.org >> http://www.marcusdenker.de >

Sept. 2, 2014

Re: [Pharo-dev] pharo4 ci build queue now has download links on top

by stepharo

good move. On 1/9/14 17:23, Marcus Denker wrote: > Hi, > > I added download links on top of > > https://ci.inria.fr/pharo/ > > (they download from files.pharo.org) > > Marcus > >

Sept. 2, 2014

Re: [Pharo-dev] Pharo Project Catalog Should look at Pharo 3

by stepharo

Yes I should change that. I started to change the code to handle multiple repos but I thought that it was a mistake. Now I propose to students to build a real catalog based on ston-based meta data :) but some smart guys should select this great topic :) On 2/9/14 09:47, Sven Van Caekenberghe wrote: > Hi, > > It seems the Pharo Project Catalog CI job looks at Configurations in MetaRepoForPharo2. Would it not be better if it (also) looked at MetaRepoForPharo3/main ? > > Sven >

Sept. 2, 2014

Re: [Pharo-dev] Jenkins builds not properly preserving artifacts?

by Tim Mackinnon

Marcus - how do you navigate to that view from the Build #890 of PharoLauncher? When I click on the link you show - thats that output I first saw in the console from the list of builds for Pharo Launcher (which is what I was looking for) - and when I click on âBack To Projectâ it takes me to the 890 build results page - however if I was looking at build 889 - where on that page do I click to see that output? I think if I understand that - this would give the information we would expect - and then we can either document this, or maybe put some artefact in every build (via a script) that lets people easily navigate to see what a build was composed off (as it seems that the info is there). Tim On that page, On 2 Sep 2014, at 09:14, Marcus Denker <marcus.denker(a)inria.fr> wrote: > The job is a matrix build... the outer job just triggers the matrix builds (see the link "default",), the log is there: > > https://ci.inria.fr/pharo-contribution/job/PharoLauncher/890/PHARO=30,VERSI… > > > On Tue, Sep 2, 2014 at 12:41 AM, Tim Mackinnon <tim(a)testit.works> wrote: > Guys - Iâve noticed that when a build completed on the Inria infrastructure, for a short time the console output correctly shows all the artefacts that were used to create that build - e.g. the slices loaded etc. However after a short time - the output then reverts to something like below (which isnât as useful): > > Started by upstream project " [8mha:AAAAqh+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8â¦. > originally caused by: > [URLTrigger] A change within the response URL invocation (log) > Building remotely on pharo-contribution-winxp in workspace C:\builds\workspace\PharoLauncher > > Deleting project workspaceâ¦ done > --- > > Iâve looked at a few other jobs (I noticed this for Pharo Launcher) and they seem the same. I think the jobs arenât configured properly? - As normally (at least in other languages like Java), the intent is that the console output reflects what was on the console when the job was run. I have a hunch that something is overwriting these files before they are archived away. > > As we donât seem to have other details of what went into a build job (which is another issue - I would expect the changes page for a build to also show this info in a better format). > > Do you think this could be fixed? > > tim > > > > > -- > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de

Sept. 2, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40196 Home: https://github.com/pharo-project/pharo-core

Sept. 2, 2014

[pharo-project/pharo-core] d45fa4: 40196

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: d45fa418c5b78c474497721b97328f43706c7e4b https://github.com/pharo-project/pharo-core/commit/d45fa418c5b78c474497721b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-02 (Tue, 02 Sep 2014) Changed paths: A OpalCompiler-Core.package/extension/TApplyingOnClassSide/instance/compiler.st A OpalCompiler-Core.package/extension/TApplyingOnClassSide/instance/compilerClass.st A OpalCompiler-Core.package/extension/TClass/instance/classSideCompiler.st A OpalCompiler-Core.package/extension/TClass/instance/classSideCompilerClass.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script196.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40196.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tool-ConfigurationBrowser.package/MetacelloConfigurationBrowserPane.class/class/accessing/availableRepositories.st A Tool-ConfigurationBrowser.package/MetacelloConfigurationBrowserPane.class/class/defaults/defaultAvailableRepositories.st M Tool-ConfigurationBrowser.package/MetacelloConfigurationBrowserPane.class/definition.st A Tool-ConfigurationBrowser.package/MetacelloConfigurationBrowserPane.class/instance/actions/addRepository.st M Tool-ConfigurationBrowser.package/MetacelloConfigurationBrowserPane.class/instance/menu/configurationListMenu_.st M Tool-ConfigurationBrowser.package/MetacelloConfigurationBrowserPane.class/instance/private accessing/availableRepositories.st Log Message: ----------- 40196 13941 [FEATURE]: Configuration Browser: Switch to Any Repository https://pharo.fogbugz.com/f/cases/13941 13938 Opal, custom compilers and class side methods https://pharo.fogbugz.com/f/cases/13938 http://files.pharo.org/image/40/40196.zip

Sept. 2, 2014

Re: [Pharo-dev] Pharo Project Catalog Should look at Pharo 3

by Guillermo Polito

Maybe we should have two ci jobs... On Tue, Sep 2, 2014 at 9:47 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > It seems the Pharo Project Catalog CI job looks at Configurations in > MetaRepoForPharo2. Would it not be better if it (also) looked at > MetaRepoForPharo3/main ? > > Sven >

Sept. 2, 2014

Re: [Pharo-dev] Jenkins builds not properly preserving artifacts?

by Marcus Denker

The job is a matrix build... the outer job just triggers the matrix builds (see the link "default",), the log is there: https://ci.inria.fr/pharo-contribution/job/PharoLauncher/890/PHARO=30,VERSI… On Tue, Sep 2, 2014 at 12:41 AM, Tim Mackinnon <tim(a)testit.works> wrote: > Guys - Iâve noticed that when a build completed on the Inria > infrastructure, for a short time the console output correctly shows all the > artefacts that were used to create that build - e.g. the slices loaded etc. > However after a short time - the output then reverts to something like > below (which isnât as useful): > > Started by upstream project " [8mha:AAAAqh+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8â¦. > originally caused by: > [URLTrigger] A change within the response URL invocation (log <https://ci.inria.fr/pharo-contribution/job/PharoLauncher/884/triggerCauseAc…>) > Building remotely on pharo-contribution-winxp <https://ci.inria.fr/pharo-contribution/computer/pharo-contribution-winxp> in workspace C:\builds\workspace\PharoLauncher > > Deleting project workspaceâ¦ done > > --- > > > Iâve looked at a few other jobs (I noticed this for Pharo Launcher) and they seem the same. I think the jobs arenât configured properly? - As normally (at least in other languages like Java), the intent is that the console output reflects what was on the console when the job was run. I have a hunch that something is overwriting these files before they are archived away. > > > As we donât seem to have other details of what went into a build job (which is another issue - I would expect the changes page for a build to also show this info in a better format). > > > Do you think this could be fixed? > > > tim > > > -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Sept. 2, 2014

Pharo Project Catalog Should look at Pharo 3

by Sven Van Caekenberghe

Hi, It seems the Pharo Project Catalog CI job looks at Configurations in MetaRepoForPharo2. Would it not be better if it (also) looked at MetaRepoForPharo3/main ? Sven

Sept. 2, 2014