Silencing the list of remote branches so it doesn't spam the console log #8
Conversation
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
|
Jenkins » git-client-plugin #21 UNSTABLE |
|
make sense, but I'd prefer the reverse option, i.e. make git-client quiet by configuring extra parameters |
|
I added GitClient.quietRemoteBranches to quiet this specific print loop. I also considered "quiet" or "lessVerbose", but "quiet" usually means don't print anything, and "lessVerbose" just doesn't sound correct (and conflicts with "verbose" if both are specified"). Let me know if you had something else in mind and I can reimplement it. |
|
Jenkins » git-client-plugin #22 UNSTABLE |
|
Not sure where we left off. Do you want to merge this for me? |
ndeloof
added a commit
that referenced
this pull request
Mar 29, 2013
Silencing the list of remote branches so it doesn't spam the console log
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.
@ndeloof for review
Large git repositories with many developers can have hundreds of branches (multiple branches per developer), which makes it spammy to print them all out when fetching remote repositories. This change just prints out the total number of branches, unless the user requests verbose output.