make CI build faster #635
make CI build faster #635
Conversation
|
Why not |
|
If there exist error and you want to rebuild it after new commits was pushed, the old one may be invisible, it depends on the workflow, if everything will send by pull request, then no this problem, and if you can accept to ignore the error CI build, just build on newer commit, then 1 will be fine. I can update it if you want :) |
|
@PeterDaveHello as with any optimisation I always like to know what we gain. Did you measure time before / after this change? Looking at the recent PRs on travis the timing seems to be around 1min30s: I'm definitively not saying that this change is bad or anything, just curious here. |
|
Yeah, in fact, I think the time of cloning repo to CI server has a large deviation range. Shallow clone really help to save the time and bandwidth because drop the useless revisions, that's for sure, and the depth's default value is 50 on travis CI, I think we usually don't need so many revisions, decrease this value can help save more time then 50. |
|
Why don't they do this by default? Seems like a waste of time and bandwidth to clone shit thats not being tested |
|
don't know |
No description provided.