On 2014-02-26, 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...
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...
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
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 Den
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 th
