[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Title: Message Title Jeremy Rampon commented on JENKINS-24304 Re: Enable/Disable verbose Git command logging in Jenkins build log I noticed this only happens when using the Git Additional Behavior "Checkout to specific local branch" in the job. If I remove this option, then all the prints go away. But this is not a suitable workaround for me, as my build scripts depend on the current branch being built (devp vs. prod). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Title: Message Title Mark Waite commented on JENKINS-24304 Re: Enable/Disable verbose Git command logging in Jenkins build log The output happens whenever the plugin needs to convert a name to a SHA1. That happens in several areas (like Prune stake remote tracking branches) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Title: Message Title Mark Waite edited a comment on JENKINS-24304 Re: Enable/Disable verbose Git command logging in Jenkins build log The output happens whenever the plugin needs to convert a name to a SHA1. That happens in several areas (like Prune stake stale remote tracking branches) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Title: Message Title Bruno Oliveira commented on JENKINS-24304 Re: Enable/Disable verbose Git command logging in Jenkins build log I second that request. Here is a sample of what we see in our CI. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Diogo Campos commented on JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log I don't even have the "Seen branch" line in my output, but I do have hundreds of rev-parse calls. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Mark Waite assigned JENKINS-24304 to Unassigned Enable/Disable verbose Git command logging in Jenkins build log Change By: Mark Waite (26/Dec/14 5:14 AM) Assignee: NicolasDeLoof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Mark Waite commented on JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log You might check if defining the property org.jenkinsci.plugins.gitclient.GitClient.quietRemoteBranches=true on the java command line which starts the Jenkins server. If the line you're trying to avoid is "Seen branch xyzzy", then the conditional in the code seems to only display that if quietRemoteBranches is the default value of false. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Jeremy Rampon commented on JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log In my case, it does a git rev-parse on every single public branches, which prints 100's of lines. I'm not sure why the Git plugin is doing this. In the Git config for this job, a specific tag is specified, so that's all it should need. I'm fine with defaulting to outputting the git command, but these rev-parse commands are really polluting the logs in my case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Kanstantsin Shautsou commented on JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log Could you provide log where this git output such terrible that you want disable it? Having full log during build process is a good practice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
