On Thu, Jan 16, 2020 at 7:41 PM Hormoz Zarnani
wrote:
>
> Hi. I am in a similar situation where I have several very large Git
> repositories, and I want to build multibranch pipelines for each of them,
> and my reference repositories don’t seem to be used for scanning/indexing.
> My issue can’
On Tuesday, July 2, 2019 at 8:38:46 AM UTC-7, Mark Waite wrote:
> That's great news. A git repository that needs more than 10 minutes to clone
> is a really good candidate for reference repositories and all the other
> techniques suggested in the "Git in the Large" video. The first preference
That's great news. A git repository that needs more than 10 minutes to
clone is a really good candidate for reference repositories and all the
other techniques suggested in the "Git in the Large" video. The first
preference with repositories that large is to reduce their size by removing
large fi
Hi Mark - whilst looking for a place to stash my reference repo I
discovered that Jenkins is keeping a cache of git checkouts in the
/var/lib/jenkins/cache folder, and by deleting these files the multibranch
pipeline scan now succeeds, so there was obviously something corrupt in
that cache (pos
Thanks for the responses and the issue link Mark, I've increased the Git
timeout value as described, and confirmed in the log that the 30 minute
timeout is in effect, but I'm still seeing the same failure (i.e. fatal
error in Scan Multibranch Pipeline Now).
I was pretty confident that there's no
Sorry, I didn't read your description thoroughly enough. You said:
I'm getting a fatal error reported when doing a repository scan (Scan
> Multibranch Pipeline Now) which was previously working.
>
The command line git log output indicates that your repository is large
enough that it may be reach
The repository in the workspace on the agent running that build is probably
damaged. Wipe the workspace on the agent and run the job again.
If wiping the workspace and running the job again does not resolve it, you
may also be encountering a timeout while cloning the repository. Increase
the tim
I'm getting a fatal error reported when doing a repository scan (Scan
Multibranch Pipeline Now) which was previously working.
I've run the git commands manually from the command line (copied and
pasted) and they appear to work correctly, so it seems like a problem with
the Jenkins git client plu
