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
According to the Git Resource document, seems that a git clone is needed every time this resource is used.
We have monorepos with hundreds of services in each, and the commit volume is high. It will be an expensive operation to clone every time (both for load to git server and the time for git clone itself).
Does Tekton support caching the git repo and reuse it for future task runs natively? If not, is it recommended for us to host our own git cache using Storage Resource or something similar?
Thanks,
Shiyu
/kind question
The text was updated successfully, but these errors were encountered:
Hey @shiyu-dong, thanks for the issue.
This is a shortcoming of the current PipelineResource design, hence our redesign work (see here) in progress. As the beta will not include PipelineResource (still usable but not supported per-se), we will tell the user to prefer using re-usable tasks (like the git one) with workspace instead of using PipelineResource.
We need to start documenting that better (and quicker), see #1369 👼
Hello,
According to the Git Resource document, seems that a
git clone
is needed every time this resource is used.We have monorepos with hundreds of services in each, and the commit volume is high. It will be an expensive operation to clone every time (both for load to git server and the time for git clone itself).
Does Tekton support caching the git repo and reuse it for future task runs natively? If not, is it recommended for us to host our own git cache using Storage Resource or something similar?
Thanks,
Shiyu
/kind question
The text was updated successfully, but these errors were encountered: