Cache Git repository contents
acknowledged
Adam Talbot
Seqera Platform makes repeated requests to remote Git providers. This may require the Nextflow head node to access the external provider to retrieve pipeline code and repository metadata.
This creates several potential failure modes: the head node may not have public internet access, the Git provider may be unavailable, or API rate limits may be reached. Many of these requests retrieve information that Seqera Platform has already fetched.
Seqera Platform could cache previously queried Git repositories and reuse the cached data until the upstream repository changes. This would reduce API calls to Git providers, lower latency when browsing pipeline settings, and reduce reliance on the provider’s real-time availability.
Reducing this external dependency could improve the resilience and business continuity of bioinformatics pipelines during Git hosting outages or temporary repository unavailability.
Rob Newman
updated the status to
acknowledged
Adam Talbot
Related posts: