Closed duncdrum closed 5 years ago
You could use a smaller depth. Travis for example uses 50 For CI
yes but travis doesn t promise build by COMMIT. Since the docker file covers all minor and patch releases, and potentially even major relases i went big. If you don't build by commit you don't notice the difference anyways.
This uses shallow clones depth=1 in the builder stage for branch and tag based builds, which makes them faster, leads to less congested airwaves, and about 600mb smaller builder images on disk.
commit based builds are depth=2000 which is i think the maximum of what we can sensibly expect to work and still better than having 14000 commits and counting in the builder. If git in the future supports cloning via commitish we can further simplify the logic.
readme changes
hotfix for 4.7.0 changes which are on develop, will require a second PR from
develop
intomaster
along the release of 4.7.0.