2 ms·
git pull [--rebase] && git push takes a few seconds. Doing it server-side (say, through any off-the-shelf code review system) is even faster. If you're insist
by paulddraper 10y ago
git pull [--rebase] && git push
takes a few seconds. Doing it server-side (say, through any off-the-shelf code review system) is even faster.
If you're insisting on running tests every single change before fast-forwarding into trunk....yes that will get prohibitive very fast. A bot would hardly help though. If you have 4 commits a minute applied and verified serially, you need to build and test in 15 seconds.
- saryant 10y agogit pull doesn't take just a few a seconds on huge repos. Pulling down a ~day's worth of changes takes several minutes in ours.
- JoshTriplett 10y agoEven if you don't run tests, at a bare minimum you always need to build-test. master should always build. With a warm ccache, that shouldn't take excessively long, but long enough that you still want to do it server-side. Assuming you've locally build-tested each commit, the bot only needs to build-test the combination. And some bots even pull in a set of merges at a time, and keep them if they all pass, only falling back to serial testing if they fail.