it's probably something else, but not sure…is there a 10 minutes timeout somewhere?
On Feb 25, 2014, at 16:59 , David Caro <dcaroest(a)redhat.com> wrote:
El mar 25 feb 2014 16:41:53 CET, Eyal Edri escribió:
> latest jenkins upgrade (+ git plugin upgrade) introduced hardcoded timeout of 10 min
to fetch from git.
> fixed in latest plugin version , so we'll schdule an update this week to
> can you re-trigger the job for now? i see other patches have completed succesfully.
> Version 2.0.2 (Feb 20, 2014)
> --> option to configure timeout on major git operations (clone, fetch)
> locks are considered a retryable failure
> notifyCommit now accept a sha1 - make commit hook design simpler and more efficient
(no poll required)
> extend branch specifier (issue #17417) and git repository URL
> Better support for branches with "/" in name (issue #14026)
> Improve backward compatibility (issue #20861)
> ----- Original Message -----
>> From: "Michal Skrivanek" <michal.skrivanek(a)redhat.com>
>> To: infra(a)ovirt.org
>> Sent: Tuesday, February 25, 2014 5:25:40 PM
>> Subject: problem with jenkins slave?
>> another one…not sure what it is…doesn't look like git
>> Infra mailing list
I don't think it's that issue, I already applied a workaround that
(modifying the jenkins startup options), the error seems to be that the
remote directory got deleted before the clone finished:
fatal: Unable to read current working directory: No such file or
If this happened more than once is worth taking a look at.
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
RHT Global #: 82-62605