[Jenkins Docker] Preinstalling plugins not working

2019-12-23 Thread domi
Hi, I just tried to update our Jenkins Docker Image with the latest version (Jenkins 2.204.1). To preinstall plugins, we use the provided 'install-plugins.sh’ script. But it does not work as before anymore… Many plugins fail to be downloaded e.g. the script tries to get the 'git-client-plugin’

Re: [Jenkins Docker] Preinstalling plugins not working

2019-12-23 Thread 'Gavin Mogan' via Jenkins Developers
I think there are issues with the infra right now, but with th holidays happening there's not a lot of eyes on it. I would recommend retrying for now. Gavin On Mon., Dec. 23, 2019, 1:50 a.m. domi, wrote: > Hi, > > I just tried to update our Jenkins Docker Image with the latest version >

Re: retrospecitvly publishing the jenkins bom

2019-12-23 Thread Oleg Nenashev
Fine with me. Probably we should think about renaming components to "core-bom" and "plugin-bom" to stop creating confusion On Monday, December 23, 2019 at 1:50:19 PM UTC+1, James Nord wrote: > > Created > https://github.com/jenkins-infra/repository-permissions-updater/pull/1377 >

Re: Blacklist/delete perl plugin?

2019-12-23 Thread Oleg Nenashev
I would prefer to just finalize JEP-7 and purge all the related Ruby-based plugins. It is not sustainable going forward, we know that there are JEP-200 issues (which we had to workaround) and Java 11-related things inside. Regarding the Perl Plugin, I will add the maintainer to Cc. On Sunday,

Re: [Jenkins Docker] Preinstalling plugins not working

2019-12-23 Thread Oleg Nenashev
Yes, there are infra instabilities reported in different channels. I am looking into it, but I do not have a lot of time/permissions. See #jenkins-infra for details On Monday, December 23, 2019 at 11:14:48 AM UTC+1, Gavin Mogan wrote: > > I think there are issues with the infra right now, but

Re: retrospecitvly publishing the jenkins bom

2019-12-23 Thread James Nord
Created https://github.com/jenkins-infra/repository-permissions-updater/pull/1377 On Wednesday, October 30, 2019 at 11:54:55 PM UTC, Mark Waite wrote: > > I definitely like the idea of retroactively available

Jenkins Plugin Error

2019-12-23 Thread wla
Hello, if i follow this tut : https://jenkins.io/doc/developer/tutorial/extend/ i get the following error Stapler processed this HTTP request as follows, but couldn't find the resource to consume the request -> evaluate( :hudson.model.Hudson,"/job/testProject/4/greeting") ->

Re: Blacklist/delete perl plugin?

2019-12-23 Thread Oleg Nenashev
+ Alexey Melezhik On Mon, Dec 23, 2019 at 1:18 PM Oleg Nenashev wrote: > I would prefer to just finalize JEP-7 and purge all the related Ruby-based > plugins. It is not sustainable going forward, we know that there are > JEP-200 issues (which we had to workaround) and Java 11-related things >

Re: Fosdem Presence

2019-12-23 Thread Oleg Nenashev
Hi all, Updates from the Advocacy SIG meeting on Thursday: - 30 Jan: We will have the following: (1) full day JX training delivered by Viktor F. (2) half day (8-noon) Jenkins training delivered by Mark Waite. Links to be posted soon. There is a small fee to compensate catering -

Re: Jenkins Plugin Error

2019-12-23 Thread 'Gavin Mogan' via Jenkins Developers
You havn't really given us very much to work with. At least seeing the code we could make a shot at this. Did you confirm your run has the action (look at the xml file) What url did you try to hit? Looks like /job/testProject/4/greeting but want to confirm Did you define getUrlName() to