[JIRA] (JENKINS-38515) Get the output from git client for debugging
Title: Message Title Jonathan Strickland closed an issue as Not A Defect See last comment; you have to hit an error condition to see the full logs which is thrown up in the GitException. A good path will not show the logs. Jenkins / JENKINS-38515 Get the output from git client for debugging Change By: Jonathan Strickland Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-38515) Get the output from git client for debugging
Title: Message Title Jonathan Strickland commented on JENKINS-38515 Re: Get the output from git client for debugging Mark Waite Ok so I feel like I wasted a lot of resources time on this; definitely apologize in advance. After looking at the code (https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1752) I found that its only going to give the stderr and stdout output if an actual error occurs. Thus, my testing of good path we were not seeing the full dumps. After testing with an error condition (simulate bad credentials which is really easy) we saw the complete curl dumps. In case someone else hits this issue and needs debug tracing, this is what we did: 1. Inject the following into your environment. We did it using puppet to orchestrate our environments and place a profile.d file on build servers / container images: $ more /etc/profile.d/git.sh export GIT_CURL_VERBOSE=1 export GIT_TRACE=1 umask 077 These may/may not work with 2.x git, it appears some of the trace/verbose env vars have changed. 2. You have to hit an error conditions for them to show up. https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1752 as an error (timeout, bad status code, ect..) will throw a git exception with the debug information from stderr / stdout of the git cli command. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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,
[JIRA] (JENKINS-38515) Get the output from git client for debugging
Title: Message Title Mark Waite commented on JENKINS-38515 Re: Get the output from git client for debugging If you're running command line git and running on a specific slave and cloning with ssh, you may be able to get the same result by editing your ~/.ssh/config file to place the ssh configuration debug settings there. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38515) Get the output from git client for debugging
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38515 Get the output from git client for debugging Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38515) Get the output from git client for debugging
Title: Message Title Jonathan Strickland updated an issue Jenkins / JENKINS-38515 Get the output from git client for debugging Change By: Jonathan Strickland We have been experiencing some infrastructure issues are causing some of our git commands to fail (fetch, pull, ect..) on our Jenkins infrastructure side. We wanted to turn on some deeper git trace levels to capture further information to help us debug the issues. On our jenkins slaves/master we turned on the below to enable git trace. The trace shows up when running via the command line and the env vars show up in the system configuration for each slave/master.[jenkins@15d08c2a101e ~]$ more /etc/profile.d/git.shexport GIT_CURL_VERBOSE=1export GIT_TRACE=1The issue we are having is enabling the correct global/job environment variables to show this output in the console of the jobs. We attempted to enable the verbose env var at https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/GitClient.java (see attachement) but do not get much more information. Is there an easy way to get the git command output sent to the job console . ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38515) Get the output from git client for debugging
Title: Message Title Jonathan Strickland updated an issue Jenkins / JENKINS-38515 Get the output from git client for debugging Change By: Jonathan Strickland Summary: Get the output from git client for debugging Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
