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
I udnerstand that deis builder will throw away all git checkouts it has on a reboot / node movement.
Problem is when pushing a branch with rather some history, this might take a while every time.
I think deis builder should do a best (better than currently) to keep a quick checkout of branches.
I am thinking of a new container / volume that has all repos, that can be fetched.
Ofcourse in case that is down, or the repo isn't available there it must keep current behaviour to just repush the branch from scratch..
This will be even more important when deis builder is scalable (I hope there are plans for this) in large clusters
Hreoku displays "fetching branch" when pushign to an existing app, so I assume they push branches to a central (but distributed) location, fetch it locally from the datacenter (which should be fast), and then accepts new pushes from there on.
I hope we can achieve something similar...
I think this could be achieved by having builder consume a deis-store-volume mount. This is an optimization that we could see being optional for users who want this performance improvement.
From @nathansamson on March 22, 2015 15:0
I udnerstand that deis builder will throw away all git checkouts it has on a reboot / node movement.
Problem is when pushing a branch with rather some history, this might take a while every time.
I think deis builder should do a best (better than currently) to keep a quick checkout of branches.
I am thinking of a new container / volume that has all repos, that can be fetched.
Ofcourse in case that is down, or the repo isn't available there it must keep current behaviour to just repush the branch from scratch..
This will be even more important when deis builder is scalable (I hope there are plans for this) in large clusters
Hreoku displays "fetching branch" when pushign to an existing app, so I assume they push branches to a central (but distributed) location, fetch it locally from the datacenter (which should be fast), and then accepts new pushes from there on.
I hope we can achieve something similar...
Copied from original issue: deis/deis#3355
The text was updated successfully, but these errors were encountered: