Re: Upgraded Plugins: Jenkins fails to start

2021-05-31 Thread Raoul de Haard
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.IndexItem.instance(IndexItem.java:181)
> at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:703)
> at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:689)
> at 
> 

Re: [IMPORTANT] plugins deprecation for Digester removal

2021-05-31 Thread Baptiste Mathus
Which "code coverage" plugin are you referring to, to be sure?
Emma & cloverphp?



Le dim. 30 mai 2021 à 20:42, Oleg Nenashev  a
écrit :

> Thanks to Baptiste for bringing it up explicitly! Many plugins from the
> list can be fixed, and there are already pull requests created by Adrien
> Lecharpentier and Carroll Chiou. It would be great to help them landed,
> but many plugins are effectively abandoned. I highly recommend that the
> pull request authors ping maintainers about putting the plugin for adoption.
>
> From the list, I am particularly concerned about Code Coverage plugins
> which seemed to be actively used. If we could get their releases out, it
> would be awesome
>
>
>
>
>
>
> On Saturday, May 29, 2021 at 12:18:37 AM UTC+2 Baptiste Mathus wrote:
>
>> Hi all,
>>
>> We are about to remove a very old version of a library provided by
>> Jenkins Core: commons-digester:2.1.
>>
>> In practice, when we do this, *this will make the following plugins
>> unusable starting with the weekly and future LTS.*
>>
>> The plugins are :
>>
>>- emma ,
>>- cloverphp ,
>>- vs-code-metrics
>>,
>>- BlameSubversion
>>,
>>- javatest-report
>>,
>>- vss ,
>>- genexus ,
>>- synergy ,
>>- config-rotator 
>>,
>>- harvest ,
>>- cmvc 
>>
>> What can you do if you use one of the plugins above?
>>
>>- Say so in this thread.
>>- Preferably be ready to step up as maintainer. These plugins are
>>de-facto long abandoned, some for 5+ years, and hence anyway they're
>>already runtime risks in your instances.
>>
>>
>> Thank you!
>>
>> -- Baptiste
>>
> --
> 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/4ca24760-4664-464f-ab76-f79ed0820fc0n%40googlegroups.com
> 
> .
>

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


Re: Jenkins upgrade from 2.250 to 2.275

2021-05-31 Thread s.p...@gmail.com
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/3ce232d1-70a7-4b6b-9acf-039611542eacn%40googlegroups.com.


post to jobs that do not exists

2021-05-31 Thread Morten Bjoernsvik
Hi
jenkins v2.295

Is it possible to configure the jenkins rest-api to return a json instead 
of a html-dump on errors?

Below is a 500 posting to a job that do not exists. After creating the job 
is was all fine.

20210531103301.714|ERROR|./gitlab2jenkins/jenkins.py:152|error posting to 
jenkins on url:
https:///job/SSID/job/wips-integrationtests-test12//build 
-> 500, data:[['file0', <_io.BufferedReader name='report.zip'>], ['json', 
'{"parameter": [{"name": "gitlab/report.zip", "file": "file0"}, {"name": 
"TESTENV", "value": "test1"}, {"name": "STATUS", "value": "NA"}]}']], resp:

Jenkins [Jenkins]var 
Q=jQuery.noConflict()https://cdn.jsdelivr.net/gh/jenkinsci/dark-theme@0.0.12/src/main/resources/io/jenkins/plugins/darktheme/theme.css"/>Skip to contentJenkinshttps://jenkins.io/redirect/search-box; 
class="main-search__icon-trailing">createSearchBox("/search/");log
 
inDashboard Oops!A problem occurred while processing the 
request.Logging 
ID=72a7ea16-654c-4ac3-bf72-97e2b0f1c471REST 
APIhttps://jenkins.io/; 
target="_blank">Jenkins 2.295 

-- 
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/15abcd97-8a77-40d3-89c5-fb8b73a1d972n%40googlegroups.com.


Re: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

2021-05-31 Thread Richard Bywater
Which version of Openshift are you using? AFAIK Openshift 4 doesn't support
use of the Docker socket anymore (or at least not by default)

Richard.

On Sat, 29 May 2021 at 05:36, anilkumar panditi 
wrote:

> Hi,
> sorry for asking repeated question,
> Earlier i had worked on a Jenkins instance which is a docker docker
> container which uses the docker inside container like below.
> -v /var/run/docker.sock:/var/run/docker.sock --privileged="true"
> --user="root"
>
> But , my Jenkins instance is running on Openshift as pod ,now and i wanted
> to reuse the same Jenkinsfile which has docker commands , and failing with
> *Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is
> the docker daemon running?*
>
> Please help.
>
> --
> 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/afc6f6ad-63f1-40a0-86d3-24486b0b321dn%40googlegroups.com
> 
> .
>

-- 
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/CAAy0hwd_sdse7rjPJYhk0Gq7EajDCzGRu1JWk4%3DHocSLf%2BwpcA%40mail.gmail.com.


Re: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

2021-05-31 Thread amila...@gmail.com
Hi,

check first if openshift jenkins pod using its container engine  asweather 
docker or containerd or something else in your Openshift server.  
This error indicates docker daemon not running or cannot connect to docker 
daemon.   







not much idea about openshift docker for me.

AMila
Devops Eng



On Monday, May 31, 2021 at 1:24:46 PM UTC+5:30 anilkuma...@gmail.com wrote:

> Hi Could you please help.
>
> On Fri, May 28, 2021 at 11:06 PM anilkumar panditi  
> wrote:
>
>> Hi,
>> sorry for asking repeated question,
>> Earlier i had worked on a Jenkins instance which is a docker docker 
>> container which uses the docker inside container like below.
>> -v /var/run/docker.sock:/var/run/docker.sock --privileged="true" 
>> --user="root"
>>
>> But , my Jenkins instance is running on Openshift as pod ,now and i 
>> wanted to reuse the same Jenkinsfile which has docker commands , and 
>> failing with 
>> *Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is 
>> the docker daemon running?*
>>
>> Please help.
>>
>> -- 
>> 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/afc6f6ad-63f1-40a0-86d3-24486b0b321dn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/28fb2de5-b8b5-4e60-825e-b83f18da9a79n%40googlegroups.com.


Re: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

2021-05-31 Thread anilkumar panditi
Hi Could you please help.

On Fri, May 28, 2021 at 11:06 PM anilkumar panditi <
anilkumar.pand...@gmail.com> wrote:

> Hi,
> sorry for asking repeated question,
> Earlier i had worked on a Jenkins instance which is a docker docker
> container which uses the docker inside container like below.
> -v /var/run/docker.sock:/var/run/docker.sock --privileged="true"
> --user="root"
>
> But , my Jenkins instance is running on Openshift as pod ,now and i wanted
> to reuse the same Jenkinsfile which has docker commands , and failing with
> *Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is
> the docker daemon running?*
>
> Please help.
>
> --
> 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/afc6f6ad-63f1-40a0-86d3-24486b0b321dn%40googlegroups.com
> 
> .
>

-- 
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/CABT%2Byc7QLy0M7mRxNQcrpb5YEFKxzKTccybtpyvzcAw9iPsvvg%40mail.gmail.com.


Re: Jenkins upgrade from 2.250 to 2.275

2021-05-31 Thread 'Björn Pedersen' via Jenkins Users
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/34578c37-a274-42cd-83ab-8dcc2d023939n%40googlegroups.com.


Re: Out-of-date version(YUI)

2021-05-31 Thread Daniel Beck



> On 30. May 2021, at 03:05, s.p...@gmail.com  wrote:
> 
> Affected versions of the package are vulnerable to Cross-site Scripting(XSS) 
> via .swf files, allowing arbitary code injection into hosting server 
> CVE-2012-5881 CVE-2012-5883
> 

While we include YUI, we do not include the vulnerable file.

Your scanner is trash.

-- 
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/352C70D7-C6E1-4509-A543-ED44803A15D6%40beckweb.net.


Re: Out-of-date version(YUI)

2021-05-31 Thread Wadeck Follonier
Hello there,

Nothing to care about at the moment for YUI as all the known 
vulnerabilities are related to the presence of the Flash files ("via .swf 
files"), they were removed from the library before it was included in 
Jenkins.
But the out-of-date status is still valid unfortunately.

Best regards,

Wadeck
On Monday, May 31, 2021 at 2:33:00 AM UTC+2 s.p...@gmail.com wrote:

> Thank you, Oleg. Thank you for sharing the link to report the 
> vulnerabilities. Appreciate your help!
>
> On Sunday, May 30, 2021 at 2:46:39 PM UTC-4 o.v.ne...@gmail.com wrote:
>
>> Hello,
>>
>> Thanks for your report. I will let the Jenkins security team members to 
>> comment on that. Just for your information, we have an official process for 
>> reporting security vulnerabilities. I highly recommend following this 
>> process. Please see 
>> https://www.jenkins.io/security/#reporting-vulnerabilities
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
>>
>> On Sunday, May 30, 2021 at 3:05:00 AM UTC+2 s.p...@gmail.com wrote:
>>
>>> Our web scans shows out-of-date version(YUI) vulnerability. I'm not able 
>>> to find anything on how to remediate this finding. Any help is appreciated. 
>>> TIA
>>> Example :  /static/01babc68/scripts/yui/yahoo/yahoo-min.js 
>>> Affected versions of the package are vulnerable to Cross-site 
>>> Scripting(XSS) via .swf files, allowing arbitary code injection into 
>>> hosting server CVE-2012-5881 CVE-2012-5883
>>>
>>> *Jenkins version - 2.250 , windows 2012 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/7ce8af98-d252-4c46-bf84-5b82294db5aen%40googlegroups.com.


Re: Jenkins upgrade from 2.250 to 2.275

2021-05-31 Thread 'Björn Pedersen' via Jenkins Users
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/e82b848a-f9a0-4756-8424-e0205d881037n%40googlegroups.com.