Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching for git resource #2021

Closed
shiyu-dong opened this issue Feb 7, 2020 · 2 comments
Closed

Caching for git resource #2021

shiyu-dong opened this issue Feb 7, 2020 · 2 comments
Labels
kind/question Issues or PRs that are questions around the project or a particular feature

Comments

@shiyu-dong
Copy link

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

@tekton-robot tekton-robot added the kind/question Issues or PRs that are questions around the project or a particular feature label Feb 7, 2020
@vdemeester
Copy link
Member

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 👼

@shiyu-dong
Copy link
Author

@vdemeester Thanks for the update. I will look into the re-usable git task!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Issues or PRs that are questions around the project or a particular feature
Projects
None yet
Development

No branches or pull requests

3 participants