3 ms·

Considering the build host does this hundreds of times every day, a better solution would be to simply have a git repo cache locally, should be secure and relia

Considering the build host does this hundreds of times every day, a better solution would be to simply have a git repo cache locally, should be secure and reliable given git’s object store design? Any simple wrappers for git that can do this transparently?

manojlds 6y ago
Build servers don't git clone everytime though. They do a git clean if needed followed a git fetch / git pull equivalent. GoCD for example maintains a single copy of the repo on the server for every pipeline that refers to it and the agents have the repos that they work on checked out. Any local changes or untracked files are by default cleaned. There are settings to force reclone etc, but it's not the default.
- dagmx 6y ago
  That depends very heavily on the build infrastructure being used however
- robjan 6y ago
  In many cases the build agent is a stateless container which is destroyed as soon as the build is finished. In cases like this the repo needs to be (shallow) cloned each time.