-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.19.1
Git client plugin 2.0.0
Git plugin 3.0.0
Pipeline: Multibranch: 2.9
I am having an issue cloning a large repo for use in a multi-branch pipeline project.
My goal is to run pipeline jobs against certain branches within my repository. However, the initial fetch seems to timeout. As you can see from the attached log, the issue appears to arise from a 10 minute timeout issue. However, if you see the below screen shots, I have all of my timeouts set to 180minutes.
In the attached tickets there were known issues with the 10 minute git timeout that were fixed by allowing users access to overrides as I have shown in the attached images. It appears as though these overrides are not being honored for some reason within the MultibranchPipeline project.
I have used the settings described here on a smaller repo and it was able to properly index the branches.
As a work around, I also tried only using the overrides as advanced settings for checkout/fetch behavior. This did not work either, unfortunately.
- is duplicated by
-
JENKINS-58349 Initial lightweight checkout of Jenkinsfile much slower on huge repos
- Open
-
JENKINS-39173 Multibranch Pipeline does not respect GIT timeout on branch indexing
- Closed
-
JENKINS-57617 Setting git timeout other than 10 minutes while scanning multibranch pipeline during indexing(for first time)
- Closed
- is related to
-
JENKINS-20445 Git plugin timeout is too small
- Closed
-
JENKINS-29164 Can't set timeout for git clone
- Closed
-
JENKINS-33631 Git plugin - timeout after 10 minutes never sends credentials (401 observed on git repo)
- Closed
-
JENKINS-23476 git-client plugin timeout default is not configurable in a standard manner
- Open