Re: Please delete perforce-plugin component from Jira

That should be fine, thanks! Any remaining perforce-plugin tickets should probably just be closed anyway, so moving them to p4-plugin shouldn't be a problem. Thanks again! On Tue, Dec 10, 2019 at 11:10 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > 22:02 <@jen

Re: Please delete perforce-plugin component from Jira

22:02 <@jenkins-admin> java.lang.RuntimeException: java.net.SocketTimeoutException I suspect not all the items got moved over. Forgive me if you didn't want it moved, but the bot doesn't really have an option to purely disable. On Tue, Dec 10, 2019 at 10:02 PM Gavin Mogan wrote: > Go IRC Bot,

Re: Please delete perforce-plugin component from Jira

Go IRC Bot, Apparently I can do it 2:01 <+halkeye> jenkins-admin: Delete component perforce-plugin and move its issues to p4-plugin 22:01 <@jenkins-admin> Deleting the subcomponent perforce-plugin. All issues will be moved to p4-plugin Lemme know if that works. Gavin On Tue., Dec. 10, 2019, 3:

Re: 2019 Election: voting has closed

Thank you KK, I added my feedback. On Tuesday, December 3, 2019 at 9:58:02 AM UTC-5, Kohsuke Kawaguchi wrote: > > I believe you can edit the document directly. The documen is WiP at the > moment, so feel free to add text, comment, provide edit suggestions, etc. > If you prefer, prefix the text w

Re: findsecbugs in spotbugs

Hey Jeff, I think it is ok to introduce it. Sounds like it would add value. There should be a switch to at least disable failing the build because of findsecbugs. Despite the potential problems with introducing it, I am +1 on it since it will definitely help the development of new plugins. Li

Please delete perforce-plugin component from Jira

Hey folks, As per the subject, can we please delete the perforce-plugin component from Jenkins' Jira? It's been deprecated for years now, but folks are still accidentally filing tickets against it instead of p4-plugin. If we can't delete it, can we change the default assignee to "Unassigned"?

Re: Fosdem Presence

I will be at FOSDEM! Meeting is a bit more complicated, but I will try :) If there are slots in the EU morning timezone, it will be great. I can spend a significant time at the booth (~50% of the conference?), and I could probably prepare demos and slidedecks for the booth. BR, Oleg On Tuesday,

findsecbugs in spotbugs

Jenkins developers, I've been working on introducing findsecbugs into the Jenkins developer ecosystem. findsecbugs is a plugin for spotbugs (formerly findbugs) that adds analysis for a significant collection of bug rules that could potentially impact security. More information is at https://f

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

LGTM On Tue, Dec 10, 2019 at 7:51 PM Slide wrote: > +1 looks like a great idea! > > On Tue, Dec 10, 2019 at 8:38 AM Matt Sicker wrote: > >> +1 to this idea and initial maintainers. This would go a long way >> toward unblocking changes in this area! :) >> >> On Tue, Dec 10, 2019 at 7:42 AM Marky

Q: rename a variable without breaking compatibility in the declarative pipeline

Hi there, I thought the readResolve might be the way to go but apparently I missed something and then there are no backward compatible for the when changeset

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

+1 looks like a great idea! On Tue, Dec 10, 2019 at 8:38 AM Matt Sicker wrote: > +1 to this idea and initial maintainers. This would go a long way > toward unblocking changes in this area! :) > > On Tue, Dec 10, 2019 at 7:42 AM Marky Jackson > wrote: > > > > I have not been as active as I would

Re: Offical policy for plugins stored not in organization

Wouldn't it be easier to do in update center? Since SCM block has to be up to date so mvn release actually pushes tags to your SCM, couldn't update center be updated to ignore and not list any plugins that don't have the SCM set to the jenkinsci org? On Tue., Dec. 10, 2019, 3:45 a.m. Daniel Beck,

Re: Proposal: Deprecate Jenkins.RUN_SCRIPTS, PluginManager.UPLOAD_PLUGINS, && PluginManager.CONFIGURE_UPDATECENTER permission types

I am currently working through a few remaining test failures and will take the PR out of draft status once they are fixed On Tuesday, December 10, 2019 at 6:08:24 AM UTC-5, Oleg Nenashev wrote: > > I am +1 for deprecating them. > All major plugins already hide them by default, and we have a secur

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

+1 to this idea and initial maintainers. This would go a long way toward unblocking changes in this area! :) On Tue, Dec 10, 2019 at 7:42 AM Marky Jackson wrote: > > I have not been as active as I would like but I would also like to be a > maintainer based on our previous conversation > > On Dec

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

I have not been as active as I would like but I would also like to be a maintainer based on our previous conversation > On Dec 10, 2019, at 3:34 AM, Oleg Nenashev wrote: > >  > BTW, I suggest the following list of maintainers based on the recent activity: > Mark Waite > Alex Earl > Carlos Sanc

Jenkins Parent POM 1.53 release with bulk dependency updates (not plugin-pom)

Hi all, Just a heads-up, I am planning to release a new version of Parent POM for Jenkins core and libraries. This release includes a bulk dependency update performed by dependabot, and hence there is a high risk of regressions in some components. I deployed 1.5

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

I like this idea > On Dec 10, 2019, at 2:19 AM, Oleg Nenashev wrote: > >  > Hi all, > > Right now we have a number of official packages for Docker: > https://github.com/jenkinsci/docker > https://github.com/jenkinsci/docker-slave > https://github.com/jenkinsci/docker-ssh-slave > https://

Re: Offical policy for plugins stored not in organization

On Tue, Dec 10, 2019 at 12:25 PM Oleg Nenashev wrote: > I think we should block releases from non-Jenkins organizations for newly > hosted/released plugins. > Newly hosted plugins need to be forked, else they don't get permissions (I hope -- at least that's how I did it when I reviewed new plugi

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

BTW, I suggest the following list of maintainers based on the recent activity: - Mark Waite - Alex Earl - Carlos Sanchez - Oleg Nenashev - Baptiste Mathus - Olivier Vernin Alternative is to just keep all members of https://github.com/orgs/jenkinsci/teams/docker/members though

Re: Offical policy for plugins stored not in organization

I created https://github.com/OctopusDeploy/octopus-jenkins-plugin/issues/60 to discuss this issue with maintainers On Tuesday, December 10, 2019 at 12:25:06 PM UTC+1, Oleg Nenashev wrote: > > I think we should block releases from non-Jenkins organizations for newly > hosted/released plugins. > A

Re: Offical policy for plugins stored not in organization

I think we should block releases from non-Jenkins organizations for newly hosted/released plugins. AFAICT the easiest way to do so is to add a check to Plugin POM, but we can also do some enforcement on the update site later. As Daniel said, it is likely to be a can of worms. FTR the plugin sit

Re: Adoption of JenkinsPipelineUnit library

Hi Nik, I see a response from Ozan ib the referenced issue. Also Stas is now formally a maintainer, so his approval also counts. I have granted you permissions in GitHub, welcome aboard! For the release permissions you will need to update https://github.com/jenkins-infra/repository-permissions-u

Re: Proposal: Deprecate Jenkins.RUN_SCRIPTS, PluginManager.UPLOAD_PLUGINS, && PluginManager.CONFIGURE_UPDATECENTER permission types

I am +1 for deprecating them. All major plugins already hide them by default, and we have a security advisory for it. https://jenkins.io/security/advisory/2017-04-10/#matrix-authorization-strategy-plugin-allowed-configuring-dangerous-permissions and below BR, Oleg On Monday, December 9, 2019 a

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

I would like that very much On Tue, Dec 10, 2019, 11:19 AM Oleg Nenashev wrote: > Hi all, > > Right now we have a number of official packages for Docker: > >- https://github.com/jenkinsci/docker >- https://github.com/jenkinsci/docker-slave >- https://github.com/jenkinsci/docker-ssh-s

Proposal: Official Docker Image maintenance team (Jenkins and Agents)

Hi all, Right now we have a number of official packages for Docker: - https://github.com/jenkinsci/docker - https://github.com/jenkinsci/docker-slave - https://github.com/jenkinsci/docker-ssh-slave - https://github.com/jenkinsci/docker-jnlp-slave - https://github.com/jenkinsci/jnlp

Fosdem Presence

Hi Folks, It's now this time of the year when we plan our Fosdem trip And I am glad to share that Jenkins project stand has been accepted this year More information here -> https://fosdem.org/2020/news/2019-11-19-accepted-stands/ We still have plenty of things to prepare so if you are intereste