Open
Bug 1938598
Opened 2 months ago
Updated 1 month ago
Repos should be cloned asynchronously and not block the landing worker
Categories
(Conduit :: Lando, enhancement)
Conduit
Lando
Tracking
(Not tracked)
NEW
People
(Reporter: zeid, Assigned: zeid)
References
(Blocks 1 open bug)
Details
When a new repo is added, it is cloned during the startup of the landing worker. This needlessly blocks the landing worker from continuing on and processing other jobs while the cloning is in process. The same situation could arise if the repos need to be recreated for any reason.
Instead, a separate command should run on the same pod as the landing worker, that periodically checks that all enabled repos are in a "cloned" state. This would necessitate adding a more robust status to the repo, so that the landing worker does not use a repo until it is fully cloned.
Assignee | ||
Updated•1 month ago
|
Assignee: nobody → zeid
You need to log in
before you can comment on or make changes to this bug.
Description
•