-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[JENKINS-63539] Use additional repo URL variants to find cache #947
Closed
Closed
Changes from 1 commit
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
cfed0dd
Use JGit for caching decision
MarkEWaite 410f70e
[JENKINS-63539] Use additional repo URL variants to find cache
MarkEWaite be4edc4
Move array initialization inside method
MarkEWaite 1b11caf
Log early exit from alternatives generator
MarkEWaite 9fd24bb
Use size estimate from largest cache
MarkEWaite abe2421
Use random sizes within range
MarkEWaite 31ecea6
Mention repo URL is git tool log message
MarkEWaite c87d025
No benefit from initial capacity of LinkedHashSet
MarkEWaite afb270f
Cache variants were not handling URLs that ended with '/'
MarkEWaite ff84573
Cache repository size in memory
MarkEWaite 9cc9dc7
Check the remoteAlternatives empty string case
MarkEWaite e3af88b
Do not include credentials in checkout unless required
MarkEWaite 7176254
[JENKINS-63572] Test for NPE if no remote configs are defined
MarkEWaite ea58c75
[JENKINS-63572] Avoid NPE if remote configs is empty
MarkEWaite d2cd2d7
Add GitToolChooser logging to diagnose test failures
MarkEWaite ae3f031
Use unique project name in GitToolChooserTest
MarkEWaite 1ec4598
Fix compilation error from prior check
MarkEWaite 7a13a85
Fix workflow syntax error from merge
MarkEWaite da79822
Better formatting of logging
MarkEWaite cf9aa8c
Report cache dir location when found
MarkEWaite 8f6058d
Better log message when cache entry found
MarkEWaite d670743
Add call to clear repository cache
MarkEWaite 987b3c0
Clear repository size cache on test entry
MarkEWaite dbd2c7a
Merge branch 'master' into find-more-caches
MarkEWaite f74d8ed
Merge branch 'master' into find-more-caches
MarkEWaite ee2cce4
Remove System.out from test
MarkEWaite ea73f1e
Fix merge mistakes
MarkEWaite File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
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.
In which case would we have multiple caches for the same git repository?
Would it happen if two different multi branch projects work on a different version of the same git repository?
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 think that one case that might happen is two jobs that refer to a remote repository with different URLs and with different update frequencies. If one of the caches is only updated once a week and the other is updated once an hour, the "once an hour" repository may have a larger size than the "once a week" repository. This assumes the larger of the two values is the better approximation of repository size.