Update Jenkinsfile.* to use shallow clones of meta #96
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We don't need a full (unshallow) clone for any of these -- the jobs don't look at the commit history and we can make new commits without having history locally. This will help on architectures that have been struggling to clone the repository since the move (because a "full" clone is now bigger than it was when we started all this), but is also generally better all around.
Member
Author
|
Hmm, should we go even further and add an explicit refspec and turn on the "honor refspec on clone" setting too so it only clones the single branch we care about? We don't often have more than one upstream branch so it doesn't actually make much functional difference, but it's part of this same data struct. |
Member
I don't think it matters either way since we almost never do branches on the main fork. |
yosifkit
approved these changes
Nov 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We don't need a full (unshallow) clone for any of these -- the jobs don't look at the commit history and we can make new commits without having history locally.
This will help on architectures that have been struggling to clone the repository since the move (because a "full" clone is now bigger than it was when we started all this), but is also generally better all around.
(I've tested this successfully on
mips64le's failingbuildjob: https://doi-janky.infosiftr.net/job/meta/job/mips64le/job/build/10430/console)