Re: Adopt oic-auth-plugin

Hi Michael, Would mind me to be another maintainer? Best, On Tue, Aug 27, 2019 at 7:57 AM Rick wrote: > Hi Michael, > > It's totally reasonable. I'm the maintainer of serval plugins. Sometimes, > I just don't have enough time out maintain them like you. > > Best, > > On Mon, Aug 26, 2019 at

Re: Unable to configure Fork Change Request Trait using Job DSL

Thanks for creating a patch for this 殺 /Joseph On Monday, August 19, 2019 at 9:17:45 PM UTC+2, Daniel Spilker wrote: > > Hi Parichay, > > I meant changing the constructor to > > public ForkMergeRequestDiscoveryTrait(int strategyId, SCMHeadAuthority > trust) { > > until Structs plugin supports

Re: Preparing your modules/library/plugin to be consumed by dependabot

Hi Gavin, we actually made that change in JCasC to prepare for https://github.com/jenkins-infra/plugin-site-api/pull/54 Good that dependabot is something you can depend on  Original PR https://github.com/jenkinsci/configuration-as-code-plugin/pull/1004 On Tuesday, August 27, 2019 at 6:50:38

Re: Hosting process

> Which would be a downside I think. Oh I thought that was the intention Yea for sure a downside On Wed, Aug 28, 2019 at 11:56 AM Jesse Glick wrote: > On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers > wrote: > > That would break the fork linkage > > Which would be a

Re: Request for admin permissions to ec2-plugin repo

This is my bad, they did that and I told them to do this > On Aug 28, 2019, at 11:56 AM, Jesse Glick wrote: > > On Wed, Aug 28, 2019 at 1:47 PM Raihaan Shouhell > wrote: >> Could I be granted the appropriate permissions? > > You can skip posting to the dev list for this sort of thing, and

Re: Request for admin permissions to ec2-plugin repo

On Wed, Aug 28, 2019 at 1:47 PM Raihaan Shouhell wrote: > Could I be granted the appropriate permissions? You can skip posting to the dev list for this sort of thing, and just open a ticket in the `INFRA` project / `github` component. -- You received this message because you are subscribed to

Re: Hosting process

On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers wrote: > That would break the fork linkage Which would be a downside I think. Also the current method forces you to remember to delete your own account’s clone so the @jenkinsci one does not appear as a fork of it. Also you

Re: Replace authorize-project-plugin

Hi everybody, Since Jenkins LTS 2.176.1 (https://jenkins.io/doc/upgrade-guide/2.176/) which includes https://issues.jenkins-ci.org/browse/JENKINS-24513 there is an administrative monitor in place. It recommends to install the authorize-project plugin. Having a look at the usage chart at

Re: Request for admin permissions to ec2-plugin repo

To add to this, Raihaan is already the maintainer of this plugin and has rights to the repo but also needs to be added to the admin group for this repository so release-drafter and dependabot can be added. > On Aug 28, 2019, at 8:36 AM, Raihaan Shouhell > wrote: > > Hi all, > > I'd like to

Request for admin permissions to ec2-plugin repo

Hi all, I'd like to enable release-drafter and dependabot for ec2-plugin's repository but do not have enough permissions on it. Could I be granted the appropriate permissions? My github id is res0nance Cheers, Raihaan -- You received this message because you are subscribed to the Google

Re: Hosting process

On Wed, Aug 28, 2019 at 9:31 AM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Why transfer it at all? Why not clone, create the new repo, then push. > > That would break the fork linkage, and be less complicated. > > Probably a little slower but doesn't need to

Re: Hosting process

Why transfer it at all? Why not clone, create the new repo, then push. That would break the fork linkage, and be less complicated. Probably a little slower but doesn't need to be realtime speeds On Wed., Aug. 28, 2019, 9:03 a.m. Slide, wrote: > > On Wed, Aug 28, 2019 at 8:59 AM Oleg Nenashev

Re: Impact of BOM on plugin versions

Ok, thanks for the clarification. And I assumed it based on all the Maven knowledge you have. ;) On Wed, Aug 28, 2019 at 10:43 AM Jesse Glick wrote: > > On Wed, Aug 28, 2019 at 11:15 AM Matt Sicker wrote: > > I thought you were already on the Maven PMC. > > Perhaps you were thinking of Stephen.

Re: Hosting process

On Wed, Aug 28, 2019 at 8:59 AM Oleg Nenashev wrote: > the requester would initiate a repository transfer request on Github >> > > Note that it used to require some additional automation logic, because a > contributor cannot just move a project to jenkinsci. > It has to happen through an

Re: Hosting process

> > the requester would initiate a repository transfer request on Github > Note that it used to require some additional automation logic, because a contributor cannot just move a project to jenkinsci. It has to happen through an intermediate organization like

Re: Impact of BOM on plugin versions

On Wed, Aug 28, 2019 at 11:15 AM Matt Sicker wrote: > I thought you were already on the Maven PMC. Perhaps you were thinking of Stephen. > are you suggesting that I shouldn't use the bom in credentials? No, I was just linking to an IT demonstrating that—so far as I can tell—it is safe to

Re: Hosting process

Sounds like a good idea. On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers wrote: > > +1 > I like the idea of not having to contact support to break the link > > > On Tue, Aug 27, 2019 at 10:01 AM Slide wrote: >> >> Based on some feedback from various people during plugin

Re: Impact of BOM on plugin versions

And here I thought you were already on the Maven PMC. Perhaps you could try reminding them on the dev lists? Also, are you suggesting that I shouldn't use the bom in credentials? Or is that issue resolved? On Tue, Aug 27, 2019 at 11:07 AM Jesse Glick wrote: > > On Tue, Aug 27, 2019 at 11:09 AM

Re: SwaggerHub for Jenkins

Just to bump this thread, I would say that it would be great to have REST API specs hosted in a centralized ways, similar to plugin Javadocs . Looks like SwaggerHub offers a pretty good user experience, so why not? Some notes: - We could also make

Re: Next LTS line selection open. Due 2019-08-27

+1 from me to choose 2.190 as the baseline. On Wednesday, August 28, 2019 at 7:39:31 AM UTC-4, Oleg Nenashev wrote: > > Great to see the fix! https://github.com/jenkinsci/jenkins/pull/4176 can > be trivially backported, so I think we can go ahead with 2.190 as a > baseline. > > BR, Oleg > > >

Re: Next LTS line selection open. Due 2019-08-27

Great to see the fix! https://github.com/jenkinsci/jenkins/pull/4176 can be trivially backported, so I think we can go ahead with 2.190 as a baseline. BR, Oleg On Wed, Aug 28, 2019 at 12:54 PM Mark Waite wrote: > > > On Tuesday, August 27, 2019 at 6:00:13 AM UTC-4, Oleg Nenashev wrote: >> >>

Re: Next LTS line selection open. Due 2019-08-27

On Tuesday, August 27, 2019 at 6:00:13 AM UTC-4, Oleg Nenashev wrote: > > For me 2.187 is a default pick. If somebody investigates JENKINS-58912 > > /