-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[ci] Do not clone all the history of the repo #20814
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
base: master
Are you sure you want to change the base?
Conversation
Test Results 19 files 19 suites 3d 6h 29m 49s ⏱️ Results for commit 29dbc50. ♻️ This comment has been updated with latest results. |
guitargeek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
| else: | ||
| returncode = subprocess_with_log(f""" | ||
| git clone --branch {branch} --single-branch {repository} "{targetdir}" | ||
| git clone --depth 1 --branch {branch} --single-branch {repository} "{targetdir}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ponder if 1 is the right number. If I remember correctly, we need some history to find the merging point between PR and the master in some circumstances.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe as a two-step process? If the search fails, then we clone fully?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is indeed what one can see in the incremental builds. I wonder whether it's an optimisation worth the complication in the code...
Should shave off 1-2 minutes from every build.