Also, adding to the thread
>>If you create a job that runs on the slave which only performs a "git
clone https://localgitserveir/git/AXP.git";, does it fail with the same
message?
It fails with the cannot read the username message . Device not configured
Is there any way to fix this issue
On
hi Mark
>From the log it only shows that the last command that was executed by the
git plugin is
git --version
it did not do git checkout -f origin/master or origin/main
And if I do the commands lik git --version, it works fine. I have the git
version 1.9.3 on my mac box
Now, for sub modules
That's all the logging there is from the git plugin. The console log is
usually sufficiently verbose to provide everything I need for problem
diagnosis.
If you execute those commands from a job on the slave, do you see the same
results?
If you create a job that runs on the slave which only perfo
After some wondering with the System Log in the Manage Jenkins ->Sytem Log,
I was able to add a logger for hudson.plugins.git but it has very minimal
output. It only posts, the the followig
Jan 19, 2015 1:47:05 PM FINE hudson.Proc
Running: git rev-parse --is-inside-work-tree
Jan 19, 2015 1:47
I would like to extend the past reply. Srry for pressing hit too soon.
What is the right way to find the exact operations that the git plugin
does. In the cases , where the slave and the master is in the same box, I
see that it mentioned
"Using .gitcredentials"
I dont see it in the slave machin
Is there a place where I can find , the exact commands that the git plugin
uses ?
On Monday, January 19, 2015 at 1:13:26 PM UTC-8, Mark Waite wrote:
>
> You might try debugging by creating build steps which perform the
> operations you need, rather than using the git plugin to perform those
> o
You might try debugging by creating build steps which perform the
operations you need, rather than using the git plugin to perform those
operations. Then you can enable the debugging options or levels which best
suit your needs.
On Mon, Jan 19, 2015 at 1:34 PM, Parag Paul wrote:
> The console o
The console output is not enough. For me, only for one of the GIT
respositories, a fetch from the repo keeps failing. This is a local git
server that we have setup on a OSX box
We keep getting this error on the slave
Error fetching remote repo 'origin'
We are running jenkins master on another