Skip to content
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.

[gitresolver] Switch from git-go git-clone to use providers API #42

Closed
chmouel opened this issue Apr 29, 2022 · 2 comments · Fixed by tektoncd/pipeline#5450
Closed

[gitresolver] Switch from git-go git-clone to use providers API #42

chmouel opened this issue Apr 29, 2022 · 2 comments · Fixed by tektoncd/pipeline#5450
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale

Comments

@chmouel
Copy link
Member

chmouel commented Apr 29, 2022

Feature request

On large (mono)?repository, a git clone may take times a lot of time, if we need to just checkin a few files.

It would be nice if we could instead use Git providers (i.e: github/gitlab) APIs instead of checking out the full tree just to grab a few files.

We may along the way will be able to support private repository in gitresolver.

Use case

Large repository checking,

Note

  • We can just use go-scm to abstract a lot of the naughty different api implementation but the devil may be in the details of each provider.
  • User may be able to provider access "token" for auth and ratelimit.
  • We can still use anonymous for at least github and maybe other git providers.
@chmouel chmouel added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 29, 2022
@abayer
Copy link
Contributor

abayer commented May 23, 2022

In practice, we'll probably want to keep the git resolver for cases where the user is using a repo that isn't on a supported provider, but it does feel like it'll make sense to add github, gitlab, etc resolvers to explicitly support credentials, API-driven fetching of individual files, etc.

@tekton-robot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants