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
At the moment when 2 task template uses a repository with a specific bash file and specific semaphore folder, the entire repository is pulled twice causing significant waste of disk space :
Note this is an extreme example - obviously this repository has more than scripts used for semaphore currently... But at scale I'm looking at few hundreds users (one project per user so every user can create and delete GCE/GKE instances/cluster using terraform||opentofu including some ansible scripts) - multiplied by potentially tens of task templates... If I am only using one bash script in a task template the idea is we don't need to clone the entire repository parse checkout only that file would be enough
Implementation
Use sparse checkout to only pull the information in the path mentioned in task template
Design
add the directory path or filename from task template for go-git sparse checkout (example shows the library supports sparse checkout)
The text was updated successfully, but these errors were encountered:
Related to
Database
Impact
nice to have
Missing Feature
At the moment when 2 task template uses a repository with a specific bash file and specific semaphore folder, the entire repository is pulled twice causing significant waste of disk space :
Note this is an extreme example - obviously this repository has more than scripts used for semaphore currently... But at scale I'm looking at few hundreds users (one project per user so every user can create and delete GCE/GKE instances/cluster using terraform||opentofu including some ansible scripts) - multiplied by potentially tens of task templates... If I am only using one bash script in a task template the idea is we don't need to clone the entire repository parse checkout only that file would be enough
Implementation
Use sparse checkout to only pull the information in the path mentioned in task template
Design
The text was updated successfully, but these errors were encountered: