On 02.09.2014, at 00:41, Tim Mackinnon <[email protected]> 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 > —
Not entirely sure but I think that’s the fingerprint of the specific build that triggered the build you’re looking at. Fingerprints allow builds to reference other builds explicitly and to use artifacts from those builds (if configured correctly). That being said, I agree that the output doesn’t help a human reader much... > > 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). That would require either - to write a dedicated log from within the image (which could probably be done with a dedicated package that you could load) or - saving all artifacts (like packages, configurations etc.) in the workspace (taks up a huge amount of space). I’m not sure that there’s a simple general solution at this time… Cheers, Max > > Do you think this could be fixed? > > tim >
