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

Kernel Panic

unread,

May 20, 2018, 3:50:56 PM5/20/18

to Jenkins Users

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: <st:include> 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

Mark Waite

unread,

May 20, 2018, 3:54:48 PM5/20/18

to jenkins...@googlegroups.com

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.

--
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.

Kernel Panic

unread,

May 20, 2018, 4:26:35 PM5/20/18

to Jenkins Users

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: <st:include> Type org.eclipse.jgit.transport.RemoteConfig not present

Thanks for your time and support

Regards

Kernel Panic

unread,

May 20, 2018, 4:30:23 PM5/20/18

to Jenkins Users

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ó:

Kernel Panic

unread,

May 20, 2018, 4:32:46 PM5/20/18

to Jenkins Users

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ó:

Kernel Panic

unread,

May 20, 2018, 4:48:08 PM5/20/18

to Jenkins Users

as I can see the versions are up to date

El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:

Screen Shot 2018-05-20 at 5.46.23 PM.png

Mark Waite

unread,

May 20, 2018, 5:43:56 PM5/20/18

to jenkins...@googlegroups.com

On Sun, May 20, 2018 at 2:30 PM Kernel Panic <netwar...@gmail.com> 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 <netwar...@gmail.com> 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: <st:include> 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-use...@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.

Mark Waite

unread,

May 20, 2018, 6:00:03 PM5/20/18

to jenkins...@googlegroups.com

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 "<plugin-name>.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 "<plugin-name>.jpi" without a matching "<plugin-name>.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 "<plugin-name>.jpi" (or "<plugin-name>.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

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com.

Kernel Panic

unread,

May 20, 2018, 6:24:27 PM5/20/18

to Jenkins Users

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.<init>(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.<init>(KlassDescriptor.java:27)

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

at org.kohsuke.stapler.MetaClass.<init>(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)

Mark Waite

unread,

May 20, 2018, 6:36:46 PM5/20/18

to jenkins...@googlegroups.com

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/dc913356-fab7-48c1-88b5-9328b5500816%40googlegroups.com.

Kernel Panic

unread,

May 20, 2018, 6:48:23 PM5/20/18

to Jenkins Users

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)