Re: Upgraded Plugins: Jenkins fails to start

[Ullrich Hafner]

Is there a reason that you are still using the old and unmaintained JaCoCo 
plugin and not the code-coverage-api plugin? The functionality should be the 
same.

> 
> On Tuesday, June 1, 2021 at 2:30:34 AM UTC+1 raould...@gmail.com 
>  wrote:
> We stumbled on the same error after upgrading plugins on Jenkins last week.
> Search in your Jenkins plugin directory for the jar file starting with the 
> name: guice.
> The results should only list one version of the guice jar.
> 
> In our case it turned out that the Jacoco plugin came with a newer version of 
> guice than the other plugins did, That caused this problem. We downgraded the 
> Jacoco plugin and it worked again (from jacoco 3.2.0 back to 3.1.1 )
> 
> Op zondag 23 mei 2021 om 19:55:03 UTC+2 schreef sverr...@gmail.com 
> :
> I have upgraded all the plugins, then restarted Jenkins.
> It fails to start properly.
> Any idea what the problem here is about?
> 
> The website is loading, but shows the following Stacktrace
> java.lang.IllegalArgumentException: Unable to inject class 
> hudson.model.UserIdMapper   at 
> hudson.init.TaskMethodFinder.lookUp(TaskMethodFinder.java:125)
>  at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) 
>  at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) 
>  at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) 
>  at jenkins.model.Jenkins$5.runTask(Jenkins.java:1131) 
>  at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) 
>  at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
>  at 
> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
>  
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  
>  at java.lang.Thread.run(Thread.java:748) 
> Caused: org.jvnet.hudson.reactor.ReactorException 
>  at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) 
>  at jenkins.InitReactorRunner.run(InitReactorRunner.java:49) 
>  at jenkins.model.Jenkins.executeReactor(Jenkins.java:1164)
>  at jenkins.model.Jenkins.(Jenkins.java:962) 
>  at hudson.model.Hudson.(Hudson.java:85) 
>  at hudson.model.Hudson.(Hudson.java:81) 
>  at hudson.WebAppMain$3.run(WebAppMain.java:295) 
> Caused: hudson.util.HudsonFailedToLoad at 
> hudson.WebAppMain$3.run(WebAppMain.java:312)
> 
> The jenkins log output shows rthe following Exceptions:
> 2021-05-23 16:50:01.547+ [id=37]INFO
> jenkins.InitReactorRunner$1#onAttained: Listed all plugins
> 2021-05-23 16:50:09.041+ [id=36]SEVERE  
> h.ExtensionFinder$GuiceFinder#: Failed to create Guice container from 
> all the plugins
> java.lang.LinkageError: loader constraint violation: loader (instance of 
> hudson/PluginFirstClassLoader) previously initiated loading for a different 
> type with name "com/google/inject/Binder"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at 
> jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1155)
> at 
> jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1326)
> at 
> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1377)
> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342)
> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1095)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> com.google.inject.multibindings.Multibinder.newSetBinder(Multibinder.java:136)
> at 
> com.google.inject.multibindings.Multibinder.newSetBinder(Multibinder.java:99)
> at 
> hudson.plugins.depgraph_view.model.graph.DependencyGraphModule.configure(DependencyGraphModule.java:49)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at 
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at 
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:285)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at net.java.sezpoz

Allow Windows JNLP agent connected with websockets to be installed as a service

[arun B]

Hi,

I recently changed my Jenkins infra to use WebSockets instead of JNLP port 
for the agent's connection. I was able to successfully set up the agent 
from a Linux machine. whereas in windows, I'm not able to connect but 
unable to make it as a service. Any inputs will help.

[image: image (79).png]

-- 
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/17d35bfb-06f9-4b06-b964-92a3cf453b4cn%40googlegroups.com.

Health check URL

[arun B]

Hi,

I recently changed my infra from classic ELB to Application Load balancer 
for my jenkins application, where the listener got changed from TCP port to 
HTTP port.

I get 403 error with the health check path "/" . Can you please share the 
successful health check url ?

Also I tried /login?from=%2F , it worked. But not sure is it the right 
health check path .

Please advise.

Thanks
Arun

-- 
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/ddf5ab3c-2bf4-4a07-a5cc-1c20042e2a0fn%40googlegroups.com.

Improper format in build history

[arun B]

Hi All,

My build history shows like the below image. My Jenkins Version is OSS 
(latest).

Any inputs will help.
[image: Screen Shot 2021-06-07 at 9.25.27 PM.png]

Thanks
Arun

-- 
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/c4cade7f-f992-47d4-b9d6-5a2408792040n%40googlegroups.com.

Environment variable "sometimes" not expanded as "Repository URL"

[mj1414...@gmail.com]

 

Hello,

we’re running Jenkins 2.277.4 on RH7 using OpenJDK11 (and no container) + 
Git plugin 4.7.1

In “Global properties” of the Jenkins configuration, we’ve defined a shell 
variable:

GerritSlave

ssh://h...@gerrit-com:29418/repo/path

 

Later on, in the job configuration we use this in 

Source Code Management

  Git

Repository URL

   ${GerritSlave}

 

Having the job triggered by polling.

 Now we had to find, that we see jobs not starting and in “Git polling log” 
we find:



Started on Jun 8, 2021, 5:26:00 PM

Polling SCM changes on master

Using strategy: Default

[poll] Last Built Revision: Revision 
5cb005655e96b87a21df36a5c1dad1ebdb925854 
(refs/remotes/origin/branches/maintenance/PSint)

The recommended git tool is: NONE

using credential 50da578b-178c-4cba-b103-91c74f6522ed

> git rev-parse --resolve-git-dir 
/var/fpwork/WS/PHY_TX--LF--PSint--buildTrigger/PHY_TX/.git # timeout=10

Fetching changes from the remote Git repositories

> git config remote.origin.url ${GerritSlave} # timeout=10

Cleaning workspace

> git rev-parse --verify HEAD # timeout=10

Resetting working tree

> git reset --hard # timeout=10

> git clean -fdx # timeout=10

Fetching upstream changes from ${GerritSlave}

> git --version # timeout=10

> git --version # 'git version 2.30.0'

> git config --get remote.${GerritSlave}.url # timeout=10

FATAL: hudson.plugins.git.GitException: Failed to fetch from ${GerritSlave}

hudson.plugins.git.GitException: Command "git config --get 
remote.${GerritSlave}.url" returned status code 1:

stdout: 

stderr: 

  at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2661)

 ---

So it looks like the variable didn’t get expanded and then the polling 
fails.

If this happens, it seems the polling gets stuck in this situation.

 

If I now trigger the job once manually (“Build with parameters”), the GIT 
polling will work: The variable gets expanded as expected, the job gets 
triggered if needed.

But it seems eventually, it gets stuck in the same way again.

I’m not sure, but it seems the problem started with updating the Jenkins 
core (from 2.263.4 to 2.277.4) and the GIT plugin.

Any ideas how to debug – or even better solve – this problem ?

Anyone seeing similar issues, maybe since updating ?

Regards

Martin

-- 
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/f1d9c2e5-2e2d-47fe-b9c4-6ac3843eb067n%40googlegroups.com.

Re: Jenkins upgrade from 2.250 to 2.275

[jn...@cloudbees.com]

you can just switch the war.
Make sure you do not go to a lower version though.  in other words if you 
are on 2.275  you could use 2.289.1 but you use 2.292 then you will have to 
wait for the next LTS to be released above that (which will be about 3 
months time).


On Monday, May 31, 2021 at 6:34:52 PM UTC+1 s.p...@gmail.com wrote:

> Thank you Björn . I will look into this. Are there any steps I need to 
> consider before migrating from weekly versions to LTS or just download the 
> war and replace it with the current war file?  Really appreciate your help !
>
> On Monday, May 31, 2021 at 2:51:24 AM UTC-4 ice...@googlemail.com wrote:
>
>> BTW, if you don't want to do too frequent updates (upgrade each week and 
>> check for all changes each time), I would consider switching to the LTS 
>> series (2.277.1 in your case).
>> Then such changes would be easier to find in the LTS changelog. 
>>
>> Björn
>>
>> Björn Pedersen schrieb am Montag, 31. Mai 2021 um 08:47:46 UTC+2:
>>
>>> Hi,
>>>
>>> it seems you  did not upgrade all plugins as well. These effects are 
>>> caused by the tables-to-div migrations.
>>>
>>> See https://www.jenkins.io/doc/developer/views/table-to-div-migration/ 
>>> for more details...
>>>
>>> Björn
>>>
>>> s.p...@gmail.com schrieb am Montag, 31. Mai 2021 um 02:52:14 UTC+2:
>>>
 After I upgraded Jenkins from 2.250 to 2.275, I noticed that the UI for 
 the Jobs configuration looks different. The section for Source Code 
 Management/Build Triggers/Build Environment/build/Post-build actions are 
 missing at the top of the job configuration page and I see a couple of 
 Artifactory configuration sections(tabs). Also, the SSH 
 settings/configuration that we set up for each job are missing. Not sure 
 how to turn off the Artifactory configuration and restore the SSH 
 settings. 
 Please the attached screenshots. Please help. TIA
 Jenkins is running on Windows 2012R2 server.




-- 
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/ce8b7200-4a5b-46d7-909f-fd3453409edbn%40googlegroups.com.

Re: Upgraded Plugins: Jenkins fails to start

[jn...@cloudbees.com]

There is a PR to the jacoco plugin that should fix this.

https://github.com/jenkinsci/jacoco-plugin/pull/151  along with a build of 
that 
https://ci.jenkins.io/job/Plugins/job/jacoco-plugin/job/PR-151/lastStableBuild/artifact/target/jacoco.hpi
 
for people who have been hit and want a fix (or to test it) before it gets 
released.

/James

On Tuesday, June 1, 2021 at 2:30:34 AM UTC+1 raould...@gmail.com wrote:

> We stumbled on the same error after upgrading plugins on Jenkins last week.
> Search in your Jenkins plugin directory for the jar file starting with the 
> name: guice.
> The results should only list one version of the guice jar.
>
> In our case it turned out that the Jacoco plugin came with a newer version 
> of guice than the other plugins did, That caused this problem. We 
> downgraded the Jacoco plugin and it worked again (from jacoco 3.2.0 back to 
> 3.1.1 )
>
> Op zondag 23 mei 2021 om 19:55:03 UTC+2 schreef sverr...@gmail.com:
>
>> I have upgraded all the plugins, then restarted Jenkins.
>> It fails to start properly.
>> Any idea what the problem here is about?
>>
>> The website is loading, but shows the following Stacktrace
>> java.lang.IllegalArgumentException: Unable to inject class 
>> hudson.model.UserIdMapper   at 
>> hudson.init.TaskMethodFinder.lookUp(TaskMethodFinder.java:125)
>>  at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) 
>>  at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) 
>>  at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) 
>>  at jenkins.model.Jenkins$5.runTask(Jenkins.java:1131) 
>>  at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) 
>>  at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
>>  at 
>> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
>>  
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>  
>>  at java.lang.Thread.run(Thread.java:748) 
>> Caused: org.jvnet.hudson.reactor.ReactorException 
>>  at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) 
>>  at jenkins.InitReactorRunner.run(InitReactorRunner.java:49) 
>>  at jenkins.model.Jenkins.executeReactor(Jenkins.java:1164)
>>  at jenkins.model.Jenkins.(Jenkins.java:962) 
>>  at hudson.model.Hudson.(Hudson.java:85) 
>>  at hudson.model.Hudson.(Hudson.java:81) 
>>  at hudson.WebAppMain$3.run(WebAppMain.java:295) 
>> Caused: hudson.util.HudsonFailedToLoad at 
>> hudson.WebAppMain$3.run(WebAppMain.java:312)
>>
>> The jenkins log output shows rthe following Exceptions:
>> 2021-05-23 16:50:01.547+ [id=37]INFO
>> jenkins.InitReactorRunner$1#onAttained: Listed all plugins
>> 2021-05-23 16:50:09.041+ [id=36]SEVERE  
>> h.ExtensionFinder$GuiceFinder#: Failed to create Guice container from 
>> all the plugins
>> java.lang.LinkageError: loader constraint violation: loader (instance of 
>> hudson/PluginFirstClassLoader) previously initiated loading for a different 
>> type with name "com/google/inject/Binder"
>> at java.lang.ClassLoader.defineClass1(Native Method)
>> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
>> at 
>> jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1155)
>> at 
>> jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1326)
>> at 
>> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1377)
>> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342)
>> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1095)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>> at 
>> com.google.inject.multibindings.Multibinder.newSetBinder(Multibinder.java:136)
>> at 
>> com.google.inject.multibindings.Multibinder.newSetBinder(Multibinder.java:99)
>> at 
>> hudson.plugins.depgraph_view.model.graph.DependencyGraphModule.configure(DependencyGraphModule.java:49)
>> at 
>> com.google.inject.AbstractModule.configure(AbstractModule.java:62)
>> at 
>> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
>> at com.google.inject.spi.Elements.getElements(Elements.java:110)
>> at 
>> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
>> at 
>> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
>> at com.google.inject.Guice.createInjector(Guice.java:96)
>> at com.google.inject.Guice.createInjector(Guice.java:73)
>> at 
>> hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:285)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
>> Method)
>> at 
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingCon

ANN - Jenkins project infrastructure was affected by Fastly outage on Jun 08, 2021

[Oleg Nenashev]

Dear all,

As you may know, there was a major Fastly outage that led to many outages
around the web. Fastly is a worldwide Content Delivery Network (CDN)
service used by many sites and services (website ).
Fastly sponsors the Jenkins project, and we use it for many services, and
we have been a happy user of it for more than one year by now. Many Jenkins
services were affected.

Examples of affected services: Jenkins website (jenkins.io
), documentation site, plugins site (
plugins.jenkins.io/), update centers, and even the status page (
status.jenkins.io). These services are used by many Jenkins instances, and
also by many Jenkins developers, adopters and vendors. There might have
been lasting impact on user instances, including but not limited to: plugin
update failures, documentation access issues, monitoring alerts, etc.

The Jenkins infrastructure team is aware of the situation. We are working
on the resolution where possible, and we wait for the resolution of the
root cause on Fastly’s side. If you want to participate in the resolution,
join our #jenkins-infra channel on libera.chat
. We will also do a
public retrospective later, stay tuned for the follow-ups.

Thanks for your patience, and #HugOps to the Fastly team.

Best regards,

Oleg Nenashev

Jenkins Infra Team

-- 
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/CAPfivLBaDgFAnhJEWsks7Ru81vjuEUkz-U7WMxrF79iLMUZRog%40mail.gmail.com.