ommand line
> implementation (rather than JGit) and it requires that you are not using
> include regions, exclude users or exclude regions.
>
> Mark Waite
>
>
> On Mon, Dec 16, 2013 at 8:05 PM, David Gayman wrote:
>
>> Sure and I see how using a lot of small git repo
Sure and I see how using a lot of small git repos, as opposed to one large
repo, could be beneficial. But for established code bases this is often not
the case.
On Mon, Dec 16, 2013 at 10:01 PM, David Gayman wrote:
> Nice, I wasn't aware of shallow or reference clones. This could be
Nice, I wasn't aware of shallow or reference clones. This could be helpful.
One more note: The jenkins server is set up as a web server to the outside
world. Our build machines are not exposed as servers. For security reasons
no source code is allowed on the jenkins server; but it would be prefera
Greg,
Thank you for responding, I am somewhat new to git and had no idea about
the --reference option. Your solution looks like basically the best way to
do this.
I still wonder why there are no options out-of-the-box to:
1) Set up only one cloned repository per project, and
2) Refuse to check o
I tried this procedure including running under the correct user, and it
works, but there have been reliability issues. Occasionally the service has
failed to start for no apparent reason. This has not happened since I
uninstalled (sc delete jenkinsservice-C__jenkins), and re-installed the
service.
