[JIRA] (JENKINS-44729) Optimize git clones via shared reference repo for multi branch builds of same repository

3 views
Skip to first unread message

tristan@techsoft3d.com (JIRA)

unread,
Feb 26, 2018, 7:41:03 PM2/26/18
to jenkinsc...@googlegroups.com
Tristan Lewis commented on Improvement JENKINS-44729
 
Re: Optimize git clones via shared reference repo for multi branch builds of same repository

Any update on the PR that Chris Williams linked? My team would love to have the git plugin handle managing reference repos on each node for us to keep disk usage down as well as speed up clones of newly-created branches.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

bitwiseman@gmail.com (JIRA)

unread,
Feb 22, 2019, 4:34:03 PM2/22/19
to jenkinsc...@googlegroups.com

No update yet, but I'm starting to do some work in this area.  I'll provide a more detailed update shortly. 

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

bitwiseman@gmail.com (JIRA)

unread,
May 6, 2019, 2:56:03 PM5/6/19
to jenkinsc...@googlegroups.com

Tristan Lewis Chris Williams
The submitted PR has been postponed by Mark Waite. If you are interested in making it happen, please say so and we'll figure out a way to loop you with folks working on the git plugin.

tristan@techsoft3d.com (JIRA)

unread,
May 6, 2019, 3:37:04 PM5/6/19
to jenkinsc...@googlegroups.com

Liam Newman - I've hackily enabled this functionality to some degree via a shared pipeline plugin, but we've considered it a workaround until it was supported in the plugin itself. So yes, we're still interested in getting the PR moved forward and eventually integrated if possible. Let me know if I can do anything to help on that front. Thanks!

bitwiseman@gmail.com (JIRA)

unread,
May 29, 2019, 12:48:03 PM5/29/19
to jenkinsc...@googlegroups.com

Tristan Lewis
Is that shared library available for people to look at?
Also, Jenkins is participatory. I'd be happy to help if you want to revive that PR - grab the source and continue working on it. You should check with the git-plugin maintainers first before sinking effort into it though. Note, you might be able to use the environment variable expansion from JENKINS-43894 to make this work.

Reply all
Reply to author
Forward
0 new messages