Run GitClientTest.testSparseCheckoutWithCliGitLFS when credentials available#1337
Merged
MarkEWaite merged 1 commit intojenkinsci:masterfrom Sep 8, 2025
Conversation
…ailable The test fails in nearly 100% of cases when credentials are not provided, even though the repository is a public repository. When credentials are provided, the test only fails in about 20% of the cases. The credentials I use for the test are narrowly scoped to exactly one repository and to only allow access to repository content. Since the repository content is already publicly readable, the credential does not grant any additional permissions. The ci.jenkins.io agents do not have the credential, so they will not run the test. Testing done Confirmed that test fails consistently without credentials. Confirmed that test fails in approximately 20% of cases when I use a range of agents including: * Debian 11 * Debian 12 * Debian Testing * openSUSE 15.6 * Red Hat Enterprise Linux 8 * Rocky Linux 9 * Ubuntu 22 * Ubuntu 24 * Windows
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Run GitClientTest.testSparseCheckoutWithCliGitLFS when credentials available
The test fails in nearly 100% of cases when credentials are not provided, even though the repository is a public repository. When credentials are provided, the test only fails in about 20% of the cases. The credentials I use for the test are narrowly scoped to exactly one repository and to only allow access to repository content. Since the repository content is already publicly readable, the credential does not grant any additional permissions.
The ci.jenkins.io agents do not have the credential, so they will not run the test.
Testing done
Confirmed that test fails consistently without credentials.
Confirmed that test fails in approximately 20% of cases when I use a range of agents including:
Submitter checklist