On 26.02.2014, at 17:47, b...@openinworld.com wrote: > Thanks for that info Max. I can see "Files to archive" in the PharoLauncher > configuration that I have access to. I don't have access to the > configuration of Pharo-3.0-Issue-Validator to check, but I guess it should > have an entry... > **/*/*.fuel > to gather fuel files from the subdirectories of the workspace.
That’s right. Althoug I think that one “/*” is enough (the double asterisk should take care of subdirectories. see http://ant.apache.org/manual/Types/fileset.html) > > I have observed from running Pharo-3.0-Issue-Tracker-Image locally that Fuel > files are created, that on the build server would located as follows... > > /builds/workspace/Pharo-3.0-Issue-Validator/3570607022163494/Pharo-3.-2.0.fuel Cool that they are being generated, not so cool that nobody knew :) > > cheers -ben > > Max Leske wrote: >> >> Take a look at the Fuel job. Just put the file into the working directory >> (same directory as the image is in) and add a rule to archive Fuel files: >> **/*.fuel >> >> >> On 25.02.2014, at 17:35, b...@openinworld.com wrote: >> >>> b...@openinworld.com wrote: >>>> >>>> b...@openinworld.com wrote: >>>>> >>>>> Marcus Denker wrote: >>>>>> >>>>>> >>>>>> On the ci server this is already done: failing tests are serialise with >>>>>> Fuel for debugging. In addition, the image is save and can be downloaded >>>>>> (in the state after the test run). >>>>> >>>> How do I find the fuel files and saved image for this validation report? >>>> https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/11185//artifact/validationReport.html >>> >>> Hi Camillo, >>> >>> I am interested by your comment on Case 12957 that "I think we can/should >>> add this code to the standard CI project" >>> regarding my ImageWorker hack to try getting hold of the test failure fuel >>> file. What was it you liked? >>> >>> Its not suitable for integration in its current form since its a very >>> specific hack hardcoding the target folder, that would leave rubbish on the >>> CI server if I didn't pay attention to manually clean up afterward. Also >>> getting the fuel file back to my local machine is awkward using scp to >>> bounce a copy through the inria ssh gateway. Ideally the fuel file would >>> just end up as an artifact of the Jenkins job. What needs doing? I'd be >>> interested in helping out - though I wouldn't want to risk breaking >>> anything prior to Pharo 3 release. >>> >>> cheers -ben >> >
