Re: Jenkins Contributor Summit @ cdCon 2022

Thank you. I'll add this to the next Jenkins Adv & Outreach Sig meeting for discussion. On Thu, Jan 20, 2022 at 11:00 AM Kara de la Marck < kdelama...@linuxfoundation.org> wrote: > Hi Alyssa, > > To a large degree, this can be decided by the organizers of the Jenkins > Contributor Summit.

Re: Error publishing plugin

Thanks, the "Include administrators" option was set on the rule. Didn't know that was a thing On Friday, January 21, 2022 at 12:54:56 PM UTC-5 ga...@gavinmogan.com wrote: > So that's usually branch protection settings in GitHub. I've personally > never found a way to support mvn release and

Re: Help needed with a stuck PR merge

Thank you! On Friday, January 21, 2022 at 5:31:31 AM UTC-5 hle...@cloudbees.com wrote: > FTR, > https://github.com/jenkins-infra/helpdesk/issues/2756#issuecomment-1018253290 > > > That status has not been used for quite awhile it’s now ‘Jenkins’ > > I’ve updated the branch protection for you >

Re: Error publishing plugin

So that's usually branch protection settings in GitHub. I've personally never found a way to support mvn release and have branch protection enabled. You could disable the no pushes while you do the release. I bet there's also a way to tell mvn to use a branch On Fri., Jan. 21, 2022, 7:45 a.m.

Re: Error publishing plugin

Forgot to include screenshot On Friday, January 21, 2022 at 10:43:59 AM UTC-5 Alberto Bec wrote: > I'm trying to publish our plugin using the manual method > but > getting the error "remote: error: GH006: Protected branch

Error publishing plugin

I'm trying to publish our plugin using the manual method but getting the error "remote: error: GH006: Protected branch update failed for refs/heads/master." Do I need to do this in a branch then merge that into master? Or am

Re: Help needed with a stuck PR merge

FTR, https://github.com/jenkins-infra/helpdesk/issues/2756#issuecomment-1018253290 > That status has not been used for quite awhile it’s now ‘Jenkins’ > I’ve updated the branch protection for you On Thursday, January 20, 2022 at 3:56:31 PM UTC+1 Jesse Glick wrote: > On Thu, Jan 20, 2022 at

Re: Dropping support for IE 11

The only issue I would have in early removal is if a plugin dropped compatability whilst it was still supported for a supported LTS version, that said we have no stake in what a plugin does or does not do. So I guess I have no issue with dropping IE today and promoting Edge to T1. it could