On 22/08/2012 10:53, Brett Porter wrote:
> On 22/08/2012, at 6:36 PM, Francesco Chicchiriccò wrote:
>
>> On 20/08/2012 14:47, Francesco Chicchiriccò wrote:
>>> On 20/08/2012 11.21, Brett Porter wrote:
Wait until it runs, then review #93 if it failed for the likely
cause. #92 used the pre
On 22/08/2012, at 6:36 PM, Francesco Chicchiriccò wrote:
> On 20/08/2012 14:47, Francesco Chicchiriccò wrote:
>> On 20/08/2012 11.21, Brett Porter wrote:
>>> Wait until it runs, then review #93 if it failed for the likely
>>> cause. #92 used the previous goals from the parent.
>>
>> Hi,
>> the p
On 20/08/2012 14:47, Francesco Chicchiriccò wrote:
> On 20/08/2012 11.21, Brett Porter wrote:
>> Wait until it runs, then review #93 if it failed for the likely
>> cause. #92 used the previous goals from the parent.
>
> Hi,
> the problem seems to be bound to some rubbish files from former builds
>
On 20/08/2012 11.21, Brett Porter wrote:
Wait until it runs, then review #93 if it failed for the likely cause. #92 used
the previous goals from the parent.
Hi,
the problem seems to be bound to some rubbish files from former builds
[1]: it should be enough to clean up the workspace, as I had
Wait until it runs, then review #93 if it failed for the likely cause. #92 used
the previous goals from the parent.
On 20/08/2012, at 7:03 PM, Francesco Chicchiriccò wrote:
> Hi,
> as reported among INFRA-5159 comments, Syncope was updated by Brett Porter
> but unfortunately it seems to be stu
Hi,
as reported among INFRA-5159 comments, Syncope was updated by Brett
Porter but unfortunately it seems to be stuck to Aug 1st.
By taking a look at related Jenkins job [1], it seems there is some
issue related to the build: how can we fix that?
Thanks for support.
Regards.
[1] https://ana
