New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building docs takes >40 minutes on master #557
Comments
Yeah, this is getting very bad. I believe sphinxcontrib-versioning should actually not build old releases if they are already built - however it is clearly not working. |
Is there any advantage to keeping old commits around? I suspect it's |
I think that's one problem - probably solvable with a shallow clone that only fetches master and tags. I don't think sphinxcontrib-versioning is building old commits, I think it is just building all tags. |
But there's no real advantage to keeping history. I would suggest just squashing everything down to a single commit periodically (or even on every build) so that garbage collection can do its work. |
History squashed with #622. Still need to build off of the last commit to save time. |
I just added the I'm not confident the sphinxcontrib-versioning will reuse them (the package is pretty buggy), but, it will certainly will not if they are just not available :D |
This new protocol should give an end to the expensive builds on circle CI, as old versions do not need to be rebuilt with every tag / push to master. After squashing the history again, and probably cleaning up git objects that are not used, this should effectively reduce the checkout time by a lot. Resolves: nipreps#557.
Can we reuse prior builds to avoid building all old versions every time?
The text was updated successfully, but these errors were encountered: