I cherry picked the change to the 2.2.x, it should be available in 2.2.8
when it is released.
On Sat, Oct 25, 2014 at 11:41 AM, Mark Waite
wrote:
> Sorry for the long delay in the reply. The change to enable submodule
> timeout has only been applied to the master branch on the git-plugin. The
Sorry for the long delay in the reply. The change to enable submodule
timeout has only been applied to the master branch on the git-plugin. The
master branch is currently targeted for version 2.3. A version of the
plugin is available from the beta update center as 2.3-beta-3.
The 2.2.x branch h
Mark:
As best I can determine that timeout is not flowing through to submodules.
In the console output of my build job I see:
> git init /jenkins_root/workspace/pylint_0_dev # timeout=10
Fetching upstream changes from g...@github.com:domain/project.git
> git --version # timeout=10
> git fetch
Thanks. You're correct. If the timeout= value shows 10, then the timeout
is not being passed to the submodule fetch.
Since there is code in the plugin to configure a timeout, there must be
something missing which is preventing that option from displaying in the
submodule config options of the pl
I believe the clone timeout value specified in the "Additional Behaviours"
section "Advanced clone opitions" is also applied to submodules fetch
operations.
Mark Waite
On Tue, Sep 30, 2014 at 6:31 AM, abierbaum wrote:
> We have a Jenkins install that we have been using for years for running
> a
We have a Jenkins install that we have been using for years for running all
of our build jobs. Recently we ran into an issue with one of our git
repositories where the initial submodules update would take longer than the
10 minute limit and would timeout. I started looking for a solution and
