Thanks. 

Not sure if that will help me though as my slaves are all linux slaves. 
 Besides, I do believe disconnecting and reconnecting did install a newer 
slave.jar for me as is evident by its timestamp.

[[email protected] jenkins20]$ ls -lrt
total 181912
drwxrwxr-x. 4 support support        38 Nov 18  2016 scripts
drwxrwxr-x. 6 support support        57 Jan 30 15:16 workspace
drwxr-xr-x  8 support support      4096 Mar 15 01:35 jdk1.8.0_131
-rw-r--r--  1 support support 185540433 May  6 18:23 jdk-8u131-linux-x64.tar
.gz
-rw-rw-r--  1 support support    730299 Jul 30 15:46 slave.jar



On Monday, July 31, 2017 at 2:18:56 PM UTC-7, Mark Waite wrote:
>
> Yes, he downloaded the latest version of slave.jar from his Jenkins server.
>
> Refer to https://issues.jenkins-ci.org/browse/JENKINS-45352 for the 
> details of his investigation.
>
> Mark Waite
>
> On Mon, Jul 31, 2017 at 2:39 PM Sreeram Krishna <[email protected] 
> <javascript:>> wrote:
>
>> Thomas, did you delete the slave.jar and let Jenkins download a new one 
>> to the slave and reconnect?  I tried disconnecting and reconnecting the 
>> slave, but did not try what you did.  
>>
>> On Mon, Jul 31, 2017 at 1:33 PM, 'Thomas Gimpel' via Jenkins Users <
>> [email protected] <javascript:>> wrote:
>>
>>> I had a similar problem with our Windows nodes. One of them always threw 
>>> an exception and the other one did not complete GIT commands. In the end I 
>>> reinstalled the slave software (especially slave.jar). After that all 
>>> worked as expected.
>>>
>>>
>>> On Monday, July 31, 2017 at 8:29:24 PM UTC+2, Sam K wrote:
>>>>
>>>> Hi
>>>>
>>>>   This is at least the second time I'm facing this issue.  When i 
>>>> updated core Jenkins from 2.47 to 2.58 and now from 2.58 to 2.71.  I 
>>>> cannot 
>>>> upgrade git plugin beyond 3.3.0.  
>>>>
>>>>    BTW, what is the difference between git client plugin and git 
>>>> plugin?  Do I need both?  Is one for the traditional Jenkins jobs and the 
>>>> other for declarative pipelines or something?  
>>>>
>>>>    Our repos are hosted in bitbucket cloud.  After upgrading the git 
>>>> plugin, during a typical checkout, it hangs for a moment and continues but 
>>>> the pipeline fails because nothing got checked out.  The workspace is 
>>>> empty.  Once I downgrade the plugin back to 3.3.0, its fine.  
>>>>
>>>> The block of code checking out from git:
>>>>         
>>>> def create_env(IP_ADDRESSES){
>>>>  git url: '[email protected]:company/scripts.git', branch: 'master'
>>>>  sh (script: "./create_test_env.sh ${IP_ADDRESSES} ", returnStdout: 
>>>> false)
>>>>  }
>>>>
>>>>
>>>> Error or failed checkout behaviour.  The pipeline continues without 
>>>> complaint that checkout did not happen and fails in the very end when it 
>>>> cannot find some scripts.  
>>>>
>>>> [Pipeline] git*07-30-2017-15:05*  > git rev-parse --is-inside-work-tree # 
>>>> timeout=10*07-30-2017-15:05* Fetching changes from the remote Git 
>>>> repository*07-30-2017-15:05*  > git config remote.origin.url 
>>>> [email protected]:company/scripts.git # timeout=10*07-30-2017-15:05* 
>>>> Fetching upstream changes from 
>>>> [email protected]:company/scripts.git*07-30-2017-15:05*  > git --version 
>>>> # timeout=10*07-30-2017-15:05*  > git fetch --tags --progress 
>>>> [email protected]:company/scripts.git 
>>>> +refs/heads/*:refs/remotes/origin/**07-30-2017-15:05*  > git rev-parse 
>>>> refs/remotes/origin/master^{commit} # timeout=10*07-30-2017-15:05*  > git 
>>>> rev-parse refs/remotes/origin/origin/master^{commit} # 
>>>> timeout=10*07-30-2017-15:05* Checking out Revision 
>>>> c4ae02523570f7c1b9bbf5fe85aa864d8b299c9a 
>>>> (refs/remotes/origin/master)[Pipeline] }[Pipeline] // node[Pipeline] 
>>>> }[Pipeline] // node[Pipeline] }
>>>>
>>>>
>>>>
>>>> After downgrading plugin version
>>>>
>>>> [Pipeline] {[Pipeline] git*07-31-2017-03:00*  > git rev-parse 
>>>> --is-inside-work-tree # timeout=10*07-31-2017-03:00* Fetching changes from 
>>>> the remote Git repository*07-31-2017-03:00*  > git config 
>>>> remote.origin.url [email protected]:company/scripts.git # 
>>>> timeout=10*07-31-2017-03:00* Fetching upstream changes from 
>>>> [email protected]:company/scripts.git*07-31-2017-03:00*  > git --version 
>>>> # timeout=10*07-31-2017-03:00*  > git fetch --tags --progress 
>>>> [email protected]:company/scripts.git 
>>>> +refs/heads/*:refs/remotes/origin/**07-31-2017-03:00*  > git rev-parse 
>>>> refs/remotes/origin/master^{commit} # timeout=10*07-31-2017-03:00*  > git 
>>>> rev-parse refs/remotes/origin/origin/master^{commit} # 
>>>> timeout=10*07-31-2017-03:00* Checking out Revision 
>>>> c4ae02523570f7c1b9bbf5fe85aa864d8b299c9a 
>>>> (refs/remotes/origin/master)*07-31-2017-03:00*  > git config 
>>>> core.sparsecheckout # timeout=10*07-31-2017-03:00*  > git checkout -f 
>>>> c4ae02523570f7c1b9bbf5fe85aa864d8b299c9a*07-31-2017-03:00*  > git branch 
>>>> -a -v --no-abbrev # timeout=10*07-31-2017-03:00*  > git branch -D master # 
>>>> timeout=10*07-31-2017-03:00*  > git checkout -b master 
>>>> c4ae02523570f7c1b9bbf5fe85aa864d8b299c9a*07-31-2017-03:00*  > git rev-list 
>>>> c4ae02523570f7c1b9bbf5fe85aa864d8b299c9a # timeout=10[Pipeline] 
>>>> stash*07-31-2017-03:00* Stashed 3 file(s)[Pipeline] wrap[Pipeline] {
>>>>
>>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-users/f575KWgoODA/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected] <javascript:>.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/edfac3fb-e1cb-42d2-a694-10202623ab66%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/edfac3fb-e1cb-42d2-a694-10202623ab66%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CAKn1gMsM%2Bnw5Dbb9m%2BVgaUxRdnJod%3D0FJh5dx9%2B4F1KgFq4cjA%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKn1gMsM%2Bnw5Dbb9m%2BVgaUxRdnJod%3D0FJh5dx9%2B4F1KgFq4cjA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b46ad255-51de-4d32-aea6-9cd321b9fca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to