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,VERSION=bleedingEdge,VM=vm/console


On Tue, Sep 2, 2014 at 12:41 AM, Tim Mackinnon <tim@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@acm.org
http://www.marcusdenker.de