Re: Jenkins Contributor Summit @ cdCon 2022

['Alyssa Tong' via Jenkins Developers]

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. Physical space has been allocated at the cdCon venue
> for an in-person Jenkins Contributor Summit. However, organizers may wish
> to enable remote contributors to participate as well, through zoom, etc.
>
> Kind regards,
>
> *Kara de la Marck *
> *Continuous Delivery Foundation*
> kdelama...@linuxfoundation.org
> linkedin.com/in/karadelamarck/
>
>
>
> On Thu, Jan 20, 2022 at 6:42 PM Alyssa Tong  wrote:
>
>> HI Kara,
>>
>> Thank you for the invite. Are you looking for the summit to be virtual or
>> in person?
>>
>> thnx,
>> alyssa
>>
>> On Thu, Jan 20, 2022 at 2:28 AM Kara de la Marck <
>> kdelama...@linuxfoundation.org> wrote:
>>
>>> Hi all,
>>>
>>> We're looking forward to cdCon, 7-8 June
>>> , in Austin Texas!
>>>
>>> CFP is open so please submit your talks!
>>> https://events.linuxfoundation.org/cdcon/program/cfp/
>>>
>>> In addition, we'd like to invite the Jenkins Community to hold a one day
>>> Jenkins Contributor Summit as part of cdCon.
>>>
>>> Please respond with your interest, who would like to participate, and
>>> who will be leading the organization of the event.
>>>
>>> Kind regards,
>>>
>>> *Kara de la Marck *
>>> *Continuous Delivery Foundation*
>>> kdelama...@linuxfoundation.org
>>> linkedin.com/in/karadelamarck/
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Advocacy and Outreach SIG" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to
>>> jenkins-advocacy-and-outreach-sig+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CABX%2BMXb2FOSUtWMfb0PWV%3DhDStcMGXcqDFJTWMt3ZrDZv%2Bbqng%40mail.gmail.com
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMBsfbtgb%3DGZXLMVFsEXUkqgNgQS%2Bok28b4eaaDRNH1F50dNTw%40mail.gmail.com.

Re: Error publishing plugin

[Alberto Bec]

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 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. Alberto Bec,  wrote:
>
>> 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 update failed for 
>>> refs/heads/master."
>>>
>>> Do I need to do this in a branch then merge that into master? Or am I 
>>> missing a permission?
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/240d9a8a-b742-43e8-a9ac-dad03a9415fan%40googlegroups.com.

Re: Help needed with a stuck PR merge

[Konstantin Voin]

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
>
> On Thursday, January 20, 2022 at 3:56:31 PM UTC+1 Jesse Glick wrote:
>
>> On Thu, Jan 20, 2022 at 9:51 AM Konstantin Voin  wrote:
>>
>>> No luck
>>>
>>
>> https://github.com/jenkins-infra/helpdesk/issues/new/choose 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0f08e319-7abb-4c37-a81f-9438c50bf112n%40googlegroups.com.

Re: Error publishing plugin

['Gavin Mogan' via Jenkins Developers]

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. Alberto Bec,  wrote:

> 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 update failed for
>> refs/heads/master."
>>
>> Do I need to do this in a branch then merge that into master? Or am I
>> missing a permission?
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutMr4R1rthU0bXWMrjy9dmmQrrkf9AfXfP1qDKKZqS6OA%40mail.gmail.com.

Re: Error publishing plugin

[Alberto Bec]

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 update failed for 
> refs/heads/master."
>
> Do I need to do this in a branch then merge that into master? Or am I 
> missing a permission?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com.

Error publishing plugin

[Alberto Bec]

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 I 
missing a permission?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/aa11d549-ed21-4ab2-9ec6-265a8903a9f7n%40googlegroups.com.

Re: Help needed with a stuck PR merge

['Herve Le Meur' via Jenkins Developers]

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 9:51 AM Konstantin Voin  wrote:
>
>> No luck
>>
>
> https://github.com/jenkins-infra/helpdesk/issues/new/choose 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0f827b4c-188a-4e36-aff0-ed3ae96c9f8cn%40googlegroups.com.

Re: Dropping support for IE 11

['jn...@cloudbees.com' via Jenkins Developers]

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 make any backports harder to versions that still support IE 
(should they be needed for any security or regression, but that would be 
the same for any change) so I doubt it has any impact on this descision..

/James

On Monday, January 17, 2022 at 7:37:32 AM UTC timja...@gmail.com wrote:

> Fine to promote edge,
>
> I don’t think IE should stay on any level.
>
> It will get broken very quickly if we remove the compat we have added for 
> it or stop enforcing PRs be compatible with it.
>
> Realistically that’s unlikely to hit the LTS version till June so will 
> match up with EOL anyway, but I don’t think we need to keep it there till 
> then?
>
> On Sun, 16 Jan 2022 at 23:13, James Nord  wrote:
>
>> Given Edge is Chromium based would it make sense to promote that to tier 1
>> at the same time to leave a platform default browser with T1 
>> comparability / support?
>>
>> It's much less likely to be broken than Safari based on comparability 
>> charts.
>>
>> As such I would have no issue dropping IE support should edge be promoted.
>>
>> /James
>> On Sunday, 16 January 2022 at 21:47:32 UTC ullrich...@gmail.com wrote:
>>
>>> Yes, it makes sense to drop support (or use Tier 3). I’m also using JS 
>>> features that do not work in IE. 
>>>
>>>
>>> Am 16.01.2022 um 22:41 schrieb Oleg Nenashev :
>>>
>>> I would suggest explicitly moving IE 11 to "Tier 3" for now until the 
>>> official end of life, with explicit statement it is deprecated. It would 
>>> have the same effect as removing it, because Tier 3 states that there're 
>>> " No guarantees. We will accept patches, but only if they are low risk. 
>>> *This 
>>> is the default unless a browser/version is listed below*". Having 
>>> explicit support tier would be useful for those users who look into 
>>> migration.
>>>
>>> I also suggest promoting Microsoft Edge to Tier 1 in the same patch 
>>>
>>> IIUC with removal of IE 11 support we will be also able to cleanup all 
>>> CSS style default hacks, right? If so, maybe dropping IE11 right away is 
>>> justified
>>>  
>>>
>>> On Sunday, January 16, 2022 at 10:39:27 PM UTC+1 ga...@gavinmogan.com 
>>> wrote:
>>>
 Absolutely on board with this. The fact that some companies decide to 
 keep this old legacy broken browser around shouldn't hold anyone else 
 back. 

 > Bootstrap 5 doesn't support it (I assume warnings-ng is already 
 incompatible with IE 11) 

 Css not working is very different than javascript not working 

 > Drop IE support completely from the support table on 
 https://www.jenkins.io/doc/administration/requirements/web-browsers/ 

 I know I had to use my open source saucelabs account when I was 
 helping out with blueocean, its so hard to test these days. 

 Gavin 

 On Sun, Jan 16, 2022 at 12:13 PM Tim Jacomb  wrote:
  
 > 
 > Hello 
 > 
 > I think it's time that we drop support for IE 11. 
 > 
 > There's some really good background information for the why's and 
 what's in the angular RFC: 
 > https://github.com/angular/angular/issues/41840 
 > 
 > Some useful reasons why: 
 > - IE 11 was released in 2013 and has only received bug and security 
 fixes since 
 > - Office365 dropped support in August 2021 
 > - Bootstrap 5 doesn't support it (I assume warnings-ng is already 
 incompatible with IE 11) 
 > - Official end of life is June 2022 
 > - Difficulty of testing changes on it and we have no automated test 
 coverage of it 
 > 
 > This was last discussed in Nov 2019 (
 https://groups.google.com/g/jenkinsci-dev/c/TV_pLEah9B4) 
 > 
 > I propose: 
 > Drop IE support completely from the support table on 
 https://www.jenkins.io/doc/administration/requirements/web-browsers/ 
 > 
 > When: 
 > After the next LTS baseline cutoff, approx 1st February 
 > 
 > Thoughts? 
 > 
 > Thanks 
 > Tim 
 > 
 > -- 
 > You received this message because you are subscribed to the Google 
 Groups "Jenkins Developers" group. 
 > To unsubscribe from this group and stop receiving emails from it, 
 send an email to jenkinsci-de...@googlegroups.com. 
 > To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidYfEY0gTeEH7dRtZ%3DNy%3D%3DC9Tk1KgCSsuqszMi4Jonvvg%40mail.gmail.com
 . 

>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-de...@googlegroups.com.
>>>
>>> To view this