Thanks @mawinter69,
We followed your instruction and it resolved 50-60% issues, Now we are facing common issue for git-plugin though we have not defined in our plugin.txt, it might definitely coming from dependent plugin, error as below inside container:
2024-05-02 06:47:27.668+0000 [id=40] WARNING hudson.PluginWrapper#versionDependencyError: Suppressing dependency error in influxdb v3.6.1: Update required: Git plugin (git 4.11.2-SNAPSHOT (private-9e2f4c92-jenkins)) to be updated to 5.2.0 or higher
2024-05-02 06:47:27.634+0000 [id=33] WARNING hudson.PluginWrapper#versionDependencyError: Suppressing dependency error in git-changelog v3.38: Update required: Git plugin (git 4.11.2-SNAPSHOT (private-9e2f4c92-jenkins)) to be updated to 5.0.2 or higher
Thu, May 2 2024 12:17:27 pm 2024-05-02 06:47:27.635+0000 [id=31] WARNING hudson.PluginWrapper#versionDependencyError: Suppressing dependency error in git-parameter v0.9.19: Update required: Git plugin (git 4.11.2-SNAPSHOT (private-9e2f4c92-jenkins)) to be updated to 5.0.2 or higher
Thu, May 2 2024 12:17:27 pm 2024-05-02 06:47:27.636+0000 [id=31] WARNING hudson.PluginWrapper#versionDependencyError: Suppressing dependency error in pipeline-github-lib v42.v0739460cda_c4: Update required: Git plugin (git 4.11.2-SNAPSHOT (private-9e2f4c92-jenkins)) to be updated to 5.0.0 or higher
We have checked all plugins from plugins.txt which respect to dependencies but we donāt see this git 4.11.2-SNAOSHOT plugin in any of the plugin, so not sure from where this plugin is coming fromā¦Also we grep 4.11.2-SNAPSHOT version in /jenkins/plugins folder but we can see only git plugin directory is using this plugin
How can we check this git plugin is coming from which dependent plugin, can you please suggest on the same?
you have a custom update site anywhere? Because the official Jenkins update site is not offering SNAPSHOT versions.
So this can only happen if you either have your own update site that has this version or you deployed that version manually.
Anyway what I would do is to add the git plugin explicitly to your plugin.txt file and not rely on the dependencies here.
Yes, I deleted plugins folder before making these changes and then tried to add git plugin in plugins.txt, deploy latest changes and checked, issue still persist
This is strange.
Normally only those version can be installed that are available in the update site and a SNAPSHOT version isnāt there.
So you must have some other process that is copying plugins that runs after plugins.txt was processed but before Jenkins starts.
Hi @mawinter69
Im on jenkins 2.361.4 and my ganet node is successfully connected but if i check logs i can see below
slave setup done.
ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.lang.NoSuchFieldException: modifiers
at java.base/java.lang.Class.getDeclaredField(Class.java:2610)
at org.jenkinsci.plugins.envinject.service.EnvInjectMasterEnvVarsSetter.call(EnvInjectMasterEnvVarsSetter.java:35)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from colobp14.calypso.com/10.100.90.114:39980
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1784)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
at hudson.remoting.Channel.call(Channel.java:1000)
at hudson.FilePath.act(FilePath.java:1277)
at org.jenkinsci.plugins.envinject.EnvInjectComputerListener.onOnline(EnvInjectComputerListener.java:144)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:748)
at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:176)
at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:337)
at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:428)
at org.jenkinsci.remoting.engine.JnlpProtocol4Handler$Handler.lambda$onChannel$0(JnlpProtocol4Handler.java:334)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:30)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:70)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused: org.jenkinsci.lib.envinject.EnvInjectException
at org.jenkinsci.plugins.envinject.service.EnvInjectMasterEnvVarsSetter.call(EnvInjectMasterEnvVarsSetter.java:42)
at org.jenkinsci.plugins.envinject.service.EnvInjectMasterEnvVarsSetter.call(EnvInjectMasterEnvVarsSetter.java:16)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:376)
at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:125)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused: java.io.IOException
at org.jenkinsci.plugins.envinject.EnvInjectComputerListener.onOnline(EnvInjectComputerListener.java:146)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:748)
at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:176)
at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:337)
at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:428)
at org.jenkinsci.remoting.engine.JnlpProtocol4Handler$Handler.lambda$onChannel$0(JnlpProtocol4Handler.java:334)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:30)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:70)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Agent successfully connected and online
One more issue we are facing is, jobs are working when we start agent as root but not working with jenkins userā¦ this issue is new to us and not sure on the solution
can you please help to suggest on this?
, there was git.jpi file which had SNAPSHOT version, after removing this, that issue resolved