You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
We use jenkins-debian-glue at $work, but because we handle some very large source packages (up to 25 Go) we don't want jenkins to fetch every ref. This could lead to several hundred of Go transiting through the network, while with only need a few Go to build the source package.
How about introducing a new git backend with these 2 parameters ?
repo URI
refspec to build the source package from
This backend would first 'git archive' the given refspec only, then build the source package using dpkg-source instead of gbp.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hi! I'm definitely open for such ideas, I have a similar situation at a customer of mine, who has tons of gerrit reviews in many repositories, we use a customized *-source there, using command lines like git fetch --tags --progress "${GIT_URL}" +"refs/changes/${git_ref_id}:refs/remotes/origin/${git_ref_id}" to get the relevant data.
Hi,
We use jenkins-debian-glue at $work, but because we handle some very large source packages (up to 25 Go) we don't want jenkins to fetch every ref. This could lead to several hundred of Go transiting through the network, while with only need a few Go to build the source package.
How about introducing a new git backend with these 2 parameters ?
This backend would first 'git archive' the given refspec only, then build the source package using dpkg-source instead of gbp.
Thanks in advance.
The text was updated successfully, but these errors were encountered: