Thanks guys. Rebase fixed the issue
On Wed, Sep 27, 2017 at 10:14 AM, Eyal Edri wrote:
> In the past, we had similar issues when jobs didn't clean up after their
> run, if we're using shared maven cache per slave, it might be the same
> issue.
> So, if a previous job run on
In the past, we had similar issues when jobs didn't clean up after their
run, if we're using shared maven cache per slave, it might be the same
issue.
So, if a previous job run on the same slave and left artifacts there, it
might affect another job.
What we did in the old job is to remove any
On Wed, Sep 27, 2017 at 9:10 AM, Barak Korren wrote:
>
>
> On 26 September 2017 at 23:22, Ala Hino wrote:
>
>> Hi,
>>
>> In the following build, I see that the build passes on Fedora but is
>> unstable on RHEL. However, checking CI console, I see that the
On 26 September 2017 at 23:22, Ala Hino wrote:
> Hi,
>
> In the following build, I see that the build passes on Fedora but is
> unstable on RHEL. However, checking CI console, I see that the build
> succeeded.
>
> Links to builds:
>
>