Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
On Sun, May 20, 2018 at 6:52 PM Kernel Panic 
wrote:

> Ok, I'll try to install a previous version manually , I have no option to
> Downgrade it from the UI, do you know which is the previous stable version
> to 3.9.0 ? or which one should I try with Jenkins 2.107.3 ?
>

Git plugin releases in the last 6 months: 3.9.0, 3.8.0, 3.7.0
Git client plugin releases in the last 6 months: 2.7.2, 2.7.1, 2.7.0

The message you're seeing is from the git client plugin, not the git
plugin.  Changing versions of the git plugin is unlikely to help.

All those versions are expected to work with Jenkins 2.107.3.  The plugin
pages (git  and git client
)  include the changelogs for each
of those releases.


> Is there a way to run the plugin manually like "java something" to see if
> I can see any other error? I cannot find which is the dependency error or
> how to fix it, maybe a previous version works fine.
>

Sorry, but there isn't a command line way to simulate the problem you're
seeing.  I don't understand the problem you're seeing.

My personal hunch is that you may need to remove all cases where you have
both an hpi and a jpi file for the same plugin, remove the subdirectory of
the plugins directory for those cases (for example, if you have both a
git-client.jpi and a git-client.hpi, remove one of those two files and
remove "plugins/git-client" directory).

Mark Waite


> Thanks
> Regards
>
>
> El domingo, 20 de mayo de 2018, 21:45:25 (UTC-3), Mark Waite escribió:
>
>> Yes, it means that the git client plugin did not initialize correctly.
>> The git client plugin includes JGit.  That class (and the RemoteConfig
>> class) are classes from JGit which is included in the git client plugin.
>>
>> On Sun, May 20, 2018 at 6:24 PM Kernel Panic  wrote:
>>
> Hi Mark
>>> Under Manage Old Data I found this, does it mean something to you?
>>>
>>> hudson.model.FreeStyleBuild project-name #82 NoClassDefFoundError:
>>> org/eclipse/jgit/lib/AnyObjectId
>>> El domingo, 20 de mayo de 2018, 20:36:48 (UTC-3), Mark Waite escribió:



 On Sun, May 20, 2018 at 5:32 PM Kernel Panic 
 wrote:

> Ok, I'll play a bit with it, and what do you think about this error?
> does it mean anything? what happens if I remove or clean 
> /var/cache/jenkins
> directory? I can bet this is the root of cause, but no idea how to resolve
> that
> dependency error.
>
>
> org.apache.commons.jelly.JellyTagException:
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>  Type org.eclipse.jgit.transport.RemoteConfig not present
>
>
 I think that error means that the git client plugin failed to
 initailize and all git operations after the git client plugin failure to
 initailize will be suspect.  The git client plugin initalization failure is
 likely much earlier in the log file.

 Mark Waite



> Thanks
> Regards
>
> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>
>> I don't know how the Jenkins loader decides between an hpi and a
>> jpi file.  I would assume it will choose jpi if it exists, and choose
>> hpi if the jpi does not exist.  However, that assumption could be
>> completely wrong.
>>
>> The docker image that I use contains only jpi files.  See
>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>>  for
>> the list of plugins that I use.  I had assumed (possibly incorrectly) 
>> that
>> hpi files were originally associated with the Hudson project, and jpi 
>> files
>> are associated with the Jenkins project.
>>
>> If you have both hpi and jpi files, that may be a source of confusion
>> for Jenkins.  You might try an experiment to assure that only one or the
>> other are available.
>>
>> Mark Waite
>>
>>
>>
>> On Sun, May 20, 2018 at 5:07 PM Kernel Panic 
>> wrote:
>>
> Hi Mark,
>>> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of
>>> the plugin, and  I get that error on every job I want to configure by 
>>> the
>>> way, is not related to a particular job, are all of them with the same
>>> error.
>>>
>>> Byt the way, I have both jpi and hpi files, which one should I
>>> replace with with .bak version?
>>>
>>>
>>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>>>
>>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>>>
>>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>>>
>>>
>>>
>>> Thanks you very much for your help
>>> Regards
>>>
>>>
>>> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite
>>> 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
Ok, I'll try to install a previous version manually , I have no option to 
Downgrade it from the UI, do you know which is the previous stable version 
to 3.9.0 ? or which one should I try with Jenkins 2.107.3 ?
Is there a way to run the plugin manually like "java something" to see if I 
can see any other error? I cannot find which is the dependency error or how 
to fix it, maybe a previous version works fine.

Thanks
Regards

El domingo, 20 de mayo de 2018, 21:45:25 (UTC-3), Mark Waite escribió:
>
> Yes, it means that the git client plugin did not initialize correctly.  
> The git client plugin includes JGit.  That class (and the RemoteConfig 
> class) are classes from JGit which is included in the git client plugin.
>
> On Sun, May 20, 2018 at 6:24 PM Kernel Panic  > wrote:
>
>> Hi Mark
>> Under Manage Old Data I found this, does it mean something to you?
>>
>> hudson.model.FreeStyleBuild project-name #82 NoClassDefFoundError: 
>> org/eclipse/jgit/lib/AnyObjectId
>> El domingo, 20 de mayo de 2018, 20:36:48 (UTC-3), Mark Waite escribió:
>>>
>>>
>>>
>>> On Sun, May 20, 2018 at 5:32 PM Kernel Panic  
>>> wrote:
>>>
 Ok, I'll play a bit with it, and what do you think about this error? 
 does it mean anything? what happens if I remove or clean 
 /var/cache/jenkins 
 directory? I can bet this is the root of cause, but no idea how to resolve 
 that
 dependency error.


 org.apache.commons.jelly.JellyTagException: 
 jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
  
  Type org.eclipse.jgit.transport.RemoteConfig not present


>>> I think that error means that the git client plugin failed to initailize 
>>> and all git operations after the git client plugin failure to initailize 
>>> will be suspect.  The git client plugin initalization failure is likely 
>>> much earlier in the log file.
>>>
>>> Mark Waite
>>>
>>>  
>>>
 Thanks
 Regards

 El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:

> I don't know how the Jenkins loader decides between an hpi and a 
> jpi file.  I would assume it will choose jpi if it exists, and choose 
> hpi if the jpi does not exist.  However, that assumption could be 
> completely wrong.
>
> The docker image that I use contains only jpi files.  See 
> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>  for 
> the list of plugins that I use.  I had assumed (possibly incorrectly) 
> that 
> hpi files were originally associated with the Hudson project, and jpi 
> files 
> are associated with the Jenkins project.
>
> If you have both hpi and jpi files, that may be a source of confusion 
> for Jenkins.  You might try an experiment to assure that only one or the 
> other are available.
>
> Mark Waite
>
>
>
> On Sun, May 20, 2018 at 5:07 PM Kernel Panic  
> wrote:
>
 Hi Mark, 
>> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the 
>> plugin, and  I get that error on every job I want to configure by the 
>> way, 
>> is not related to a particular job, are all of them with the same error.
>>
>> Byt the way, I have both jpi and hpi files, which one should I 
>> replace with with .bak version?
>>
>>
>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>>
>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>>
>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>>
>>
>>
>> Thanks you very much for your help
>> Regards
>>
>>
>> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>>
>>> When I say "the jenkins log", I mean the log file written by Jenkins 
>>> as it is running.  I don't mean the log from individual jobs.
>>>
>>> On my Debian machine, the Jenkins logs are written in 
>>> /var/log/jenkins/
>>>
>>> Mark Waite
>>>
>>> On Sun, May 20, 2018 at 4:51 PM Kernel Panic  
>>> wrote:
>>>
>> And this is the full log when I go to project / configure.

 org.apache.commons.jelly.JellyTagException: 
 jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
   Type org.eclipse.jgit.transport.

 RemoteConfig not present
at 
 org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
at 
 org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
at 
 org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
Yes, it means that the git client plugin did not initialize correctly.  The
git client plugin includes JGit.  That class (and the RemoteConfig class)
are classes from JGit which is included in the git client plugin.

On Sun, May 20, 2018 at 6:24 PM Kernel Panic 
wrote:

> Hi Mark
> Under Manage Old Data I found this, does it mean something to you?
>
> hudson.model.FreeStyleBuild project-name #82 NoClassDefFoundError:
> org/eclipse/jgit/lib/AnyObjectId
> El domingo, 20 de mayo de 2018, 20:36:48 (UTC-3), Mark Waite escribió:
>>
>>
>>
>> On Sun, May 20, 2018 at 5:32 PM Kernel Panic  wrote:
>>
>>> Ok, I'll play a bit with it, and what do you think about this error?
>>> does it mean anything? what happens if I remove or clean /var/cache/jenkins
>>> directory? I can bet this is the root of cause, but no idea how to resolve
>>> that
>>> dependency error.
>>>
>>>
>>> org.apache.commons.jelly.JellyTagException:
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>>
>>>
>> I think that error means that the git client plugin failed to initailize
>> and all git operations after the git client plugin failure to initailize
>> will be suspect.  The git client plugin initalization failure is likely
>> much earlier in the log file.
>>
>> Mark Waite
>>
>>
>>
>>> Thanks
>>> Regards
>>>
>>> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>>>
 I don't know how the Jenkins loader decides between an hpi and a
 jpi file.  I would assume it will choose jpi if it exists, and choose
 hpi if the jpi does not exist.  However, that assumption could be
 completely wrong.

 The docker image that I use contains only jpi files.  See
 https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
  for
 the list of plugins that I use.  I had assumed (possibly incorrectly) that
 hpi files were originally associated with the Hudson project, and jpi files
 are associated with the Jenkins project.

 If you have both hpi and jpi files, that may be a source of confusion
 for Jenkins.  You might try an experiment to assure that only one or the
 other are available.

 Mark Waite



 On Sun, May 20, 2018 at 5:07 PM Kernel Panic 
 wrote:

>>> Hi Mark,
> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the
> plugin, and  I get that error on every job I want to configure by the way,
> is not related to a particular job, are all of them with the same error.
>
> Byt the way, I have both jpi and hpi files, which one should I replace
> with with .bak version?
>
>
> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>
> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>
> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>
>
>
> Thanks you very much for your help
> Regards
>
>
> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>
>> When I say "the jenkins log", I mean the log file written by Jenkins
>> as it is running.  I don't mean the log from individual jobs.
>>
>> On my Debian machine, the Jenkins logs are written in
>> /var/log/jenkins/
>>
>> Mark Waite
>>
>> On Sun, May 20, 2018 at 4:51 PM Kernel Panic 
>> wrote:
>>
> And this is the full log when I go to project / configure.
>>>
>>> org.apache.commons.jelly.JellyTagException: 
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>   Type org.eclipse.jgit.transport.
>>>
>>> RemoteConfig not present
>>> at 
>>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>> at 
>>> org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>> at 
>>> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>> at 
>>> org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at 
>>> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>> at 
>>> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
Hi Mark
Under Manage Old Data I found this, does it mean something to you?

hudson.model.FreeStyleBuild project-name #82 NoClassDefFoundError: 
org/eclipse/jgit/lib/AnyObjectId
El domingo, 20 de mayo de 2018, 20:36:48 (UTC-3), Mark Waite escribió:
>
>
>
> On Sun, May 20, 2018 at 5:32 PM Kernel Panic  > wrote:
>
>> Ok, I'll play a bit with it, and what do you think about this error? does 
>> it mean anything? what happens if I remove or clean /var/cache/jenkins 
>> directory? I can bet this is the root of cause, but no idea how to resolve 
>> that
>> dependency error.
>>
>>
>> org.apache.commons.jelly.JellyTagException: 
>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>  
>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>
>>
> I think that error means that the git client plugin failed to initailize 
> and all git operations after the git client plugin failure to initailize 
> will be suspect.  The git client plugin initalization failure is likely 
> much earlier in the log file.
>
> Mark Waite
>
>  
>
>> Thanks
>> Regards
>>
>> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>>
>>> I don't know how the Jenkins loader decides between an hpi and a 
>>> jpi file.  I would assume it will choose jpi if it exists, and choose 
>>> hpi if the jpi does not exist.  However, that assumption could be 
>>> completely wrong.
>>>
>>> The docker image that I use contains only jpi files.  See 
>>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>>>  for 
>>> the list of plugins that I use.  I had assumed (possibly incorrectly) that 
>>> hpi files were originally associated with the Hudson project, and jpi files 
>>> are associated with the Jenkins project.
>>>
>>> If you have both hpi and jpi files, that may be a source of confusion 
>>> for Jenkins.  You might try an experiment to assure that only one or the 
>>> other are available.
>>>
>>> Mark Waite
>>>
>>>
>>>
>>> On Sun, May 20, 2018 at 5:07 PM Kernel Panic  
>>> wrote:
>>>
>> Hi Mark, 
 Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the 
 plugin, and  I get that error on every job I want to configure by the way, 
 is not related to a particular job, are all of them with the same error.

 Byt the way, I have both jpi and hpi files, which one should I replace 
 with with .bak version?


 -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak

 -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi

 -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi



 Thanks you very much for your help
 Regards


 El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:

> When I say "the jenkins log", I mean the log file written by Jenkins 
> as it is running.  I don't mean the log from individual jobs.
>
> On my Debian machine, the Jenkins logs are written in /var/log/jenkins/
>
> Mark Waite
>
> On Sun, May 20, 2018 at 4:51 PM Kernel Panic  
> wrote:
>
 And this is the full log when I go to project / configure.
>>
>> org.apache.commons.jelly.JellyTagException: 
>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>   Type org.eclipse.jgit.transport.
>>
>> RemoteConfig not present
>>  at 
>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>  at 
>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>  at 
>> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>  at 
>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
On Sun, May 20, 2018 at 5:32 PM Kernel Panic 
wrote:

> Ok, I'll play a bit with it, and what do you think about this error? does
> it mean anything? what happens if I remove or clean /var/cache/jenkins
> directory? I can bet this is the root of cause, but no idea how to resolve
> that
> dependency error.
>
>
> org.apache.commons.jelly.JellyTagException:
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>  Type org.eclipse.jgit.transport.RemoteConfig not present
>
>
I think that error means that the git client plugin failed to initailize
and all git operations after the git client plugin failure to initailize
will be suspect.  The git client plugin initalization failure is likely
much earlier in the log file.

Mark Waite



> Thanks
> Regards
>
> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>
>> I don't know how the Jenkins loader decides between an hpi and a
>> jpi file.  I would assume it will choose jpi if it exists, and choose
>> hpi if the jpi does not exist.  However, that assumption could be
>> completely wrong.
>>
>> The docker image that I use contains only jpi files.  See
>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>>  for
>> the list of plugins that I use.  I had assumed (possibly incorrectly) that
>> hpi files were originally associated with the Hudson project, and jpi files
>> are associated with the Jenkins project.
>>
>> If you have both hpi and jpi files, that may be a source of confusion for
>> Jenkins.  You might try an experiment to assure that only one or the other
>> are available.
>>
>> Mark Waite
>>
>>
>>
>> On Sun, May 20, 2018 at 5:07 PM Kernel Panic  wrote:
>>
> Hi Mark,
>>> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the
>>> plugin, and  I get that error on every job I want to configure by the way,
>>> is not related to a particular job, are all of them with the same error.
>>>
>>> Byt the way, I have both jpi and hpi files, which one should I replace
>>> with with .bak version?
>>>
>>>
>>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>>>
>>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>>>
>>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>>>
>>>
>>>
>>> Thanks you very much for your help
>>> Regards
>>>
>>>
>>> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>>>
 When I say "the jenkins log", I mean the log file written by Jenkins as
 it is running.  I don't mean the log from individual jobs.

 On my Debian machine, the Jenkins logs are written in /var/log/jenkins/

 Mark Waite

 On Sun, May 20, 2018 at 4:51 PM Kernel Panic 
 wrote:

>>> And this is the full log when I go to project / configure.
>
> org.apache.commons.jelly.JellyTagException: 
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>   Type org.eclipse.jgit.transport.
>
> RemoteConfig not present
>   at 
> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at 
> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
Ok, I'll play a bit with it, and what do you think about this error? does 
it mean anything? what happens if I remove or clean /var/cache/jenkins 
directory? I can bet this is the root of cause, but no idea how to resolve 
that
dependency error.

org.apache.commons.jelly.JellyTagException: 
jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
 
 Type org.eclipse.jgit.transport.RemoteConfig not present

Thanks
Regards

El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>
> I don't know how the Jenkins loader decides between an hpi and a 
> jpi file.  I would assume it will choose jpi if it exists, and choose 
> hpi if the jpi does not exist.  However, that assumption could be 
> completely wrong.
>
> The docker image that I use contains only jpi files.  See 
> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>  for 
> the list of plugins that I use.  I had assumed (possibly incorrectly) that 
> hpi files were originally associated with the Hudson project, and jpi files 
> are associated with the Jenkins project.
>
> If you have both hpi and jpi files, that may be a source of confusion for 
> Jenkins.  You might try an experiment to assure that only one or the other 
> are available.
>
> Mark Waite
>
>
>
> On Sun, May 20, 2018 at 5:07 PM Kernel Panic  > wrote:
>
>> Hi Mark, 
>> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the 
>> plugin, and  I get that error on every job I want to configure by the way, 
>> is not related to a particular job, are all of them with the same error.
>>
>> Byt the way, I have both jpi and hpi files, which one should I replace 
>> with with .bak version?
>>
>>
>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>>
>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>>
>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>>
>>
>>
>> Thanks you very much for your help
>> Regards
>>
>>
>> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>>
>>> When I say "the jenkins log", I mean the log file written by Jenkins as 
>>> it is running.  I don't mean the log from individual jobs.
>>>
>>> On my Debian machine, the Jenkins logs are written in /var/log/jenkins/
>>>
>>> Mark Waite
>>>
>>> On Sun, May 20, 2018 at 4:51 PM Kernel Panic  
>>> wrote:
>>>
>> And this is the full log when I go to project / configure.

 org.apache.commons.jelly.JellyTagException: 
 jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
   Type org.eclipse.jgit.transport.

 RemoteConfig not present
at 
 org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at 
 org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
I don't know how the Jenkins loader decides between an hpi and a jpi file.
I would assume it will choose jpi if it exists, and choose hpi if the
jpi does not exist.  However, that assumption could be completely wrong.

The docker image that I use contains only jpi files.  See
https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
for
the list of plugins that I use.  I had assumed (possibly incorrectly) that
hpi files were originally associated with the Hudson project, and jpi files
are associated with the Jenkins project.

If you have both hpi and jpi files, that may be a source of confusion for
Jenkins.  You might try an experiment to assure that only one or the other
are available.

Mark Waite



On Sun, May 20, 2018 at 5:07 PM Kernel Panic 
wrote:

> Hi Mark,
> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the
> plugin, and  I get that error on every job I want to configure by the way,
> is not related to a particular job, are all of them with the same error.
>
> Byt the way, I have both jpi and hpi files, which one should I replace
> with with .bak version?
>
>
> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>
> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>
> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>
>
>
> Thanks you very much for your help
> Regards
>
>
> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>
>> When I say "the jenkins log", I mean the log file written by Jenkins as
>> it is running.  I don't mean the log from individual jobs.
>>
>> On my Debian machine, the Jenkins logs are written in /var/log/jenkins/
>>
>> Mark Waite
>>
>> On Sun, May 20, 2018 at 4:51 PM Kernel Panic  wrote:
>>
> And this is the full log when I go to project / configure.
>>>
>>> org.apache.commons.jelly.JellyTagException: 
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>   Type org.eclipse.jgit.transport.
>>>
>>> RemoteConfig not present
>>> at 
>>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>> at 
>>> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>> at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>> at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
Hi Mark, 
Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the 
plugin, and  I get that error on every job I want to configure by the way, 
is not related to a particular job, are all of them with the same error.

Byt the way, I have both jpi and hpi files, which one should I replace with 
with .bak version?


-rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak

-rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi

-rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi



Thanks you very much for your help
Regards

El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>
> When I say "the jenkins log", I mean the log file written by Jenkins as it 
> is running.  I don't mean the log from individual jobs.
>
> On my Debian machine, the Jenkins logs are written in /var/log/jenkins/
>
> Mark Waite
>
> On Sun, May 20, 2018 at 4:51 PM Kernel Panic  > wrote:
>
>> And this is the full log when I go to project / configure.
>>
>> org.apache.commons.jelly.JellyTagException: 
>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>   Type org.eclipse.jgit.transport.
>>
>> RemoteConfig not present
>>  at 
>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>  at 
>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>  at 
>> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>  at 
>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>  at 
>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>  at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>  at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>  at 
>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>  at 
>> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>  at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>  at 
>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>  at 
>> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>>  at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>  at 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
When I say "the jenkins log", I mean the log file written by Jenkins as it
is running.  I don't mean the log from individual jobs.

On my Debian machine, the Jenkins logs are written in /var/log/jenkins/

Mark Waite

On Sun, May 20, 2018 at 4:51 PM Kernel Panic 
wrote:

> And this is the full log when I go to project / configure.
>
> org.apache.commons.jelly.JellyTagException: 
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>   Type org.eclipse.jgit.transport.
>
> RemoteConfig not present
>   at 
> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at 
> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>   at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>   at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
And this is the full log when I go to project / configure.

org.apache.commons.jelly.JellyTagException: 
jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
  Type org.eclipse.jgit.transport.RemoteConfig not present
at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at 
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
Hi Mark, really appreciated your help!
this is the full log

May 20, 2018 10:41:27 PM hudson.model.Run execute
INFO: project-name #319 main build action completed: FAILURE
May 20, 2018 10:41:27 PM jenkins.plugins.slack.ActiveNotifier completed
WARNING: Project project-name has no Slack configuration.
May 20, 2018 10:43:23 PM org.eclipse.jetty.server.session.Session 
beginInvalidate
INFO: Session node048asxnoizepb18kiq7qs8g5p83 already being invalidated
May 20, 2018 10:43:30 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: descriptor.helpFile in 
/job/project-name/configure. Reason: 
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at 
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at 
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at 
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at 
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at 
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
I suspect the last thing in the Jenkins log is much less helpful for
diagnosis than the early contents of the Jenkins log.  Somewhere in the
early portions of the Jenkins log I would expect to find a good hint that
something is unable to start.

On Sun, May 20, 2018 at 4:24 PM Kernel Panic 
wrote:

> Thank you very much for the explanation, I will try to restore the old
> plugin version, and by the way this is the last thing on jenkins log
>
> Caused by: java.lang.NullPointerException
>
> at
> org.jenkinsci.plugins.github.config.GitHubPluginConfig.constructDefaultUrl(GitHubPluginConfig.java:228)
>
> at
> org.jenkinsci.plugins.github.config.GitHubPluginConfig.getHookUrl(GitHubPluginConfig.java:116)
>
> ... 341 more
>
>
> May 20, 2018 9:00:55 PM hudson.ExpressionFactory2$JexlExpression evaluate
>
> WARNING: Caught exception evaluating: descriptor.helpFile in
> /job/project-name/configure. Reason:
> java.lang.reflect.InvocationTargetException
>
> java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)Caused
> by: java.lang.NoClassDefFoundError: org/eclipse/jgit/transport/RemoteConfig
>
> at java.lang.Class.getDeclaredMethods0(Native Method)
>
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>
> at java.lang.Class.getDeclaredMethods(Class.java:1975)
>
> at
> org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:149)
>
> at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:85)
>
> at
> org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:216)
>
> at
> org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:141)
>
> at org.kohsuke.stapler.lang.Klass.getFunctions(Klass.java:98)
>
> at org.kohsuke.stapler.KlassDescriptor.(KlassDescriptor.java:27)
>
> at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:105)
>
> at org.kohsuke.stapler.MetaClass.(MetaClass.java:93)
>
> at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:204)
>
> at
> org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:109)
>
> at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:257)
>
> at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:252)
>
> at hudson.model.Descriptor.getHelpFile(Descriptor.java:750)
>
> at hudson.model.Descriptor.getHelpFile(Descriptor.java:732)
>
> at hudson.model.Descriptor.getHelpFile(Descriptor.java:721)
>
> ... 160 more
>
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.jgit.transport.RemoteConfig
>
> at
> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374)
>
> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327)
>
> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> El domingo, 20 de mayo de 2018, 19:00:03 (UTC-3), Mark Waite escribió:
>
>> On Sun, May 20, 2018 at 2:32 PM Kernel Panic  wrote:
>>
>>> If there was a manual update, ( I can see some some git-client git and
>>> git hub hpi/jpi  files under plugin directory ) how can I revert it back?
>>>
>>> Thanks you very much!
>>>
>>>
>> If one or more plugins were upgraded from a prior version to the current
>> version, then there would be a ".bak" file in the /plugins/
>> subdirectory of the Jenkins home directory.  For example, I recently
>> upgraded the docker-commons plugin and there is now a "docker-commons.bak"
>> file (previous docker-commons plugin version) and a "docker-commons.jpi"
>> file (currentl version of the docker-commons plugin).
>>
>> Plugins which have not been upgraded (at least on my installation) appear
>> as ".jpi" without a matching ".bak".
>>
>> If you want to replace an existing plugin at the file system level with a
>> different version, it may be enough to stop Jenkins, perform a backup, then
>> repalce the ".jpi" (or ".hpi" if it exists
>> instead) with the replacement version.
>>
>> You might also read the Jenkins log file to see if there are hints in the
>> log file that might give an indication why the plugin is unable to start.
>>
>> Mark Waite
>>
>>
>
>>> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:

 Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
 confirm that there are no warnings about unsatisfied dependencies?

 I think that type of message might appear if a new git plugin were
 manually uploaded to a system that hadn't yet updated the git client plugin
 to the latest version.

 On Sun, May 20, 2018 at 1:50 PM Kernel Panic 
 wrote:

> Hello
> I inherited a server with git 2.107.3 installed, it seems the previous
> admin upgraded it, now when I got to project config I get this error:
>
> org.apache.commons.jelly.JellyTagException:
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>  

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
Thank you very much for the explanation, I will try to restore the old 
plugin version, and by the way this is the last thing on jenkins log

Caused by: java.lang.NullPointerException

at 
org.jenkinsci.plugins.github.config.GitHubPluginConfig.constructDefaultUrl(GitHubPluginConfig.java:228)

at 
org.jenkinsci.plugins.github.config.GitHubPluginConfig.getHookUrl(GitHubPluginConfig.java:116)

... 341 more


May 20, 2018 9:00:55 PM hudson.ExpressionFactory2$JexlExpression evaluate

WARNING: Caught exception evaluating: descriptor.helpFile in 
/job/project-name/configure. Reason: 
java.lang.reflect.InvocationTargetException

java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)Caused by: 
java.lang.NoClassDefFoundError: org/eclipse/jgit/transport/RemoteConfig

at java.lang.Class.getDeclaredMethods0(Native Method)

at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)

at java.lang.Class.getDeclaredMethods(Class.java:1975)

at org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:149)

at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:85)

at 
org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:216)

at 
org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:141)

at org.kohsuke.stapler.lang.Klass.getFunctions(Klass.java:98)

at org.kohsuke.stapler.KlassDescriptor.(KlassDescriptor.java:27)

at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:105)

at org.kohsuke.stapler.MetaClass.(MetaClass.java:93)

at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:204)

at 
org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:109)

at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:257)

at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:252)

at hudson.model.Descriptor.getHelpFile(Descriptor.java:750)

at hudson.model.Descriptor.getHelpFile(Descriptor.java:732)

at hudson.model.Descriptor.getHelpFile(Descriptor.java:721)

... 160 more

Caused by: java.lang.ClassNotFoundException: 
org.eclipse.jgit.transport.RemoteConfig

at 
jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374)

at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327)

at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)

at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
El domingo, 20 de mayo de 2018, 19:00:03 (UTC-3), Mark Waite escribió:
>
>
>
> On Sun, May 20, 2018 at 2:32 PM Kernel Panic  wrote:
>
>> If there was a manual update, ( I can see some some git-client git and 
>> git hub hpi/jpi  files under plugin directory ) how can I revert it back?
>>
>> Thanks you very much!
>>
>>
> If one or more plugins were upgraded from a prior version to the current 
> version, then there would be a ".bak" file in the /plugins/ 
> subdirectory of the Jenkins home directory.  For example, I recently 
> upgraded the docker-commons plugin and there is now a "docker-commons.bak" 
> file (previous docker-commons plugin version) and a "docker-commons.jpi" 
> file (currentl version of the docker-commons plugin).
>
> Plugins which have not been upgraded (at least on my installation) appear 
> as ".jpi" without a matching ".bak".
>
> If you want to replace an existing plugin at the file system level with a 
> different version, it may be enough to stop Jenkins, perform a backup, then 
> repalce the ".jpi" (or ".hpi" if it exists 
> instead) with the replacement version.
>
> You might also read the Jenkins log file to see if there are hints in the 
> log file that might give an indication why the plugin is unable to start.
>
> Mark Waite
>  
>
>>
>> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>>>
>>> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to 
>>> confirm that there are no warnings about unsatisfied dependencies?  
>>>
>>> I think that type of message might appear if a new git plugin were 
>>> manually uploaded to a system that hadn't yet updated the git client plugin 
>>> to the latest version.
>>>
>>> On Sun, May 20, 2018 at 1:50 PM Kernel Panic  
>>> wrote:
>>>
 Hello
 I inherited a server with git 2.107.3 installed, it seems the previous 
 admin upgraded it, now when I got to project config I get this error:

 org.apache.commons.jelly.JellyTagException: 
 jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
  
  Type org.eclipse.jgit.transport.RemoteConfig not present

 If I scroll down to Source Management I do not see the git option, only 
 None, CVS, and CVS Project set.
 If I got to Manage Jenkins / Configure System I get the same java error.

 The git plugin version is 3.9.0 and I do no see an option to downgrade, 
 so Im lost in here, any  idea how can I troubleshoot this issue?
 The servert is Debian 8.2 

 

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
On Sun, May 20, 2018 at 2:32 PM Kernel Panic  wrote:

> If there was a manual update, ( I can see some some git-client git and git
> hub hpi/jpi  files under plugin directory ) how can I revert it back?
>
> Thanks you very much!
>
>
If one or more plugins were upgraded from a prior version to the current
version, then there would be a ".bak" file in the /plugins/
subdirectory of the Jenkins home directory.  For example, I recently
upgraded the docker-commons plugin and there is now a "docker-commons.bak"
file (previous docker-commons plugin version) and a "docker-commons.jpi"
file (currentl version of the docker-commons plugin).

Plugins which have not been upgraded (at least on my installation) appear
as ".jpi" without a matching ".bak".

If you want to replace an existing plugin at the file system level with a
different version, it may be enough to stop Jenkins, perform a backup, then
repalce the ".jpi" (or ".hpi" if it exists
instead) with the replacement version.

You might also read the Jenkins log file to see if there are hints in the
log file that might give an indication why the plugin is unable to start.

Mark Waite


>
> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>>
>> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
>> confirm that there are no warnings about unsatisfied dependencies?
>>
>> I think that type of message might appear if a new git plugin were
>> manually uploaded to a system that hadn't yet updated the git client plugin
>> to the latest version.
>>
>> On Sun, May 20, 2018 at 1:50 PM Kernel Panic  wrote:
>>
>>> Hello
>>> I inherited a server with git 2.107.3 installed, it seems the previous
>>> admin upgraded it, now when I got to project config I get this error:
>>>
>>> org.apache.commons.jelly.JellyTagException:
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>>
>>> If I scroll down to Source Management I do not see the git option, only
>>> None, CVS, and CVS Project set.
>>> If I got to Manage Jenkins / Configure System I get the same java error.
>>>
>>> The git plugin version is 3.9.0 and I do no see an option to downgrade,
>>> so Im lost in here, any  idea how can I troubleshoot this issue?
>>> The servert is Debian 8.2
>>>
>>> Thanks in advance
>>> Regards
>>>
>>> --
>>> 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 jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>> 
>>> .
>>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHLxKv5xvNq2mHVvv0PPcfe4N0uZThrpACM19zAQPn7CQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
On Sun, May 20, 2018 at 2:30 PM Kernel Panic 
wrote:

> And this is the error I get when building the project
>
> Building on master in workspace /var/lib/jenkins/jobs/project-name/workspace
> [workspace] $ /bin/sh -xe /tmp/jenkins1514082732430590998.sh
>
>
That message says that you have a shell step (probably in a Freestyle job)
that is executing on the master agent in the workspace
/var/lib/jenkins/jobs/project-name/workspace*. *

+ git checkout master
> fatal: Not a git repository (or any parent up to mount point 
> /var/lib/jenkins/jobs)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
>
>
The 'sh' step is calling command line git with the command "git checkout
master".  Command line git expects to find a git repository in
/var/lib/jenkins/jobs/project-name/workspace. Command line does not see a
git repository in /var/lib/jenkins/jobs/project-name/workspace and thus
fails.

If this is a Freestyle job that was defined to use the git plugin but now
the git plugin is no longer able to be loaded, then that is probably an
expected failure. You'll likely need to fix whatever is preventing the git
plugin from being loaded.

Mark Waite

> Build step 'Execute shell' marked build as failure
> Skipped archiving because build is not successful
> Finished: FAILURE
>
>
>



>
> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>>
>> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
>> confirm that there are no warnings about unsatisfied dependencies?
>>
>> I think that type of message might appear if a new git plugin were
>> manually uploaded to a system that hadn't yet updated the git client plugin
>> to the latest version.
>>
>> On Sun, May 20, 2018 at 1:50 PM Kernel Panic  wrote:
>>
>>> Hello
>>> I inherited a server with git 2.107.3 installed, it seems the previous
>>> admin upgraded it, now when I got to project config I get this error:
>>>
>>> org.apache.commons.jelly.JellyTagException:
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>>
>>> If I scroll down to Source Management I do not see the git option, only
>>> None, CVS, and CVS Project set.
>>> If I got to Manage Jenkins / Configure System I get the same java error.
>>>
>>> The git plugin version is 3.9.0 and I do no see an option to downgrade,
>>> so Im lost in here, any  idea how can I troubleshoot this issue?
>>> The servert is Debian 8.2
>>>
>>> Thanks in advance
>>> Regards
>>>
>>> --
>>> 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 jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>> 
>>> .
>>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/f3a61d48-a4ce-4547-89d3-eb8cb321b05d%40googlegroups.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG_CPHYFmCWCLVd2efALF7jQB3j89mtamM46NJHGydgtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
If there was a manual update, ( I can see some some git-client git and git 
hub hpi/jpi  files under plugin directory ) how can I revert it back?

Thanks you very much!

El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>
> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to 
> confirm that there are no warnings about unsatisfied dependencies?  
>
> I think that type of message might appear if a new git plugin were 
> manually uploaded to a system that hadn't yet updated the git client plugin 
> to the latest version.
>
> On Sun, May 20, 2018 at 1:50 PM Kernel Panic  > wrote:
>
>> Hello
>> I inherited a server with git 2.107.3 installed, it seems the previous 
>> admin upgraded it, now when I got to project config I get this error:
>>
>> org.apache.commons.jelly.JellyTagException: 
>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>  
>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>
>> If I scroll down to Source Management I do not see the git option, only 
>> None, CVS, and CVS Project set.
>> If I got to Manage Jenkins / Configure System I get the same java error.
>>
>> The git plugin version is 3.9.0 and I do no see an option to downgrade, 
>> so Im lost in here, any  idea how can I troubleshoot this issue?
>> The servert is Debian 8.2 
>>
>> Thanks in advance
>> Regards
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>  
>> 
>> .
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
And this is the error I get when building the project

Building on master in workspace /var/lib/jenkins/jobs/project-name/workspace
[workspace] $ /bin/sh -xe /tmp/jenkins1514082732430590998.sh
+ git checkout master
fatal: Not a git repository (or any parent up to mount point 
/var/lib/jenkins/jobs)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Build step 'Execute shell' marked build as failure
Skipped archiving because build is not successful
Finished: FAILURE




El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>
> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to 
> confirm that there are no warnings about unsatisfied dependencies?  
>
> I think that type of message might appear if a new git plugin were 
> manually uploaded to a system that hadn't yet updated the git client plugin 
> to the latest version.
>
> On Sun, May 20, 2018 at 1:50 PM Kernel Panic  > wrote:
>
>> Hello
>> I inherited a server with git 2.107.3 installed, it seems the previous 
>> admin upgraded it, now when I got to project config I get this error:
>>
>> org.apache.commons.jelly.JellyTagException: 
>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>  
>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>
>> If I scroll down to Source Management I do not see the git option, only 
>> None, CVS, and CVS Project set.
>> If I got to Manage Jenkins / Configure System I get the same java error.
>>
>> The git plugin version is 3.9.0 and I do no see an option to downgrade, 
>> so Im lost in here, any  idea how can I troubleshoot this issue?
>> The servert is Debian 8.2 
>>
>> Thanks in advance
>> Regards
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>  
>> 
>> .
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f3a61d48-a4ce-4547-89d3-eb8cb321b05d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Kernel Panic
Hi, this what I get when I go to Manage Jenkins

Warnings have been published for the following currently installed 
components.GitHub Pull Request Builder 1.40.0 
GitHub
 
access tokens stored in in build.xml 
Environment 
Injector Plugin 2.1.5 
Exposure of 
sensitive build variables stored by EnvInject 1.90 and earlier 




And when I got to configure system

A problem occurred while processing the request. Please check our bug 
tracker  to see if a similar 
problem has already been reported. If it is already reported, please vote 
and put a comment on it to let us gauge the impact of the problem. If you 
think this is a new issue, please file a new issue. When you file an issue, 
make sure to add the entire stack trace, along with the version of Jenkins 
and relevant plugins. The users list 
 might be also useful in 
understanding what has happened.
Stack trace

org.apache.commons.jelly.JellyTagException: 
jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84:
  Type org.eclipse.jgit.transport.RemoteConfig not present



Thanks for your time and support

Regards


El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>
> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to 
> confirm that there are no warnings about unsatisfied dependencies?  
>
> I think that type of message might appear if a new git plugin were 
> manually uploaded to a system that hadn't yet updated the git client plugin 
> to the latest version.
>
> On Sun, May 20, 2018 at 1:50 PM Kernel Panic  > wrote:
>
>> Hello
>> I inherited a server with git 2.107.3 installed, it seems the previous 
>> admin upgraded it, now when I got to project config I get this error:
>>
>> org.apache.commons.jelly.JellyTagException: 
>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>  
>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>
>> If I scroll down to Source Management I do not see the git option, only 
>> None, CVS, and CVS Project set.
>> If I got to Manage Jenkins / Configure System I get the same java error.
>>
>> The git plugin version is 3.9.0 and I do no see an option to downgrade, 
>> so Im lost in here, any  idea how can I troubleshoot this issue?
>> The servert is Debian 8.2 
>>
>> Thanks in advance
>> Regards
>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>  
>> 
>> .
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/022d0dc1-d6a2-4cb3-a2e5-e2fe6bfad468%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

2018-05-20 Thread Mark Waite
Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
confirm that there are no warnings about unsatisfied dependencies?

I think that type of message might appear if a new git plugin were manually
uploaded to a system that hadn't yet updated the git client plugin to the
latest version.

On Sun, May 20, 2018 at 1:50 PM Kernel Panic 
wrote:

> Hello
> I inherited a server with git 2.107.3 installed, it seems the previous
> admin upgraded it, now when I got to project config I get this error:
>
> org.apache.commons.jelly.JellyTagException:
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>  Type org.eclipse.jgit.transport.RemoteConfig not present
>
> If I scroll down to Source Management I do not see the git option, only
> None, CVS, and CVS Project set.
> If I got to Manage Jenkins / Configure System I get the same java error.
>
> The git plugin version is 3.9.0 and I do no see an option to downgrade, so
> Im lost in here, any  idea how can I troubleshoot this issue?
> The servert is Debian 8.2
>
> Thanks in advance
> Regards
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFwQmouQpBmBXxfQuyw%3DZkgzkNRuD2WR7SQfTmJME80RA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.