Re: Request for access to YouTube account

['Olblak' via Jenkins Developers]

Hi,
I just added Bruno to the list of people with manager access to the Youtub 
channel.

On Thursday, 27 October 2022 at 09:34:03 UTC+2 sme...@cloudbees.com wrote:

> +1
>
> On Wed, Oct 26, 2022 at 7:13 PM 'Alyssa Tong' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> +1 from me as well 
>>
>> On Wed, Oct 26, 2022 at 8:18 AM Adrien Lecharpentier <
>> adrien.lec...@gmail.com> wrote:
>>
>>> +1
>>>
>>> Le mer. 26 oct. 2022 à 15:16, Alexander Brandes  a 
>>> écrit :
>>>
 +1

 On Wednesday, 26 October 2022 at 15:09:53 UTC+2 damien@gmail.com 
 wrote:

> +1 for me!
>
> Bruno's work on the SIG is clearly an indicator of the trust we can 
> put.
> I'm also convinced that he'll have plenty of idea to 
> documente/describe/improve the SIG publication process
>
> Le mercredi 26 octobre 2022 à 15:07:33 UTC+2, ullrich...@gmail.com a 
> écrit :
>
>> +1
>>
>> Am 26.10.2022 um 14:42 schrieb timja...@gmail.com > >:
>>
>> +1
>>
>> On Wednesday, 26 October 2022 at 13:18:13 UTC+1 goun...@gmail.com 
>> wrote:
>>
>>> Hi group,
>>>
>>> I sometimes run the Platform SIG meeting (like 
>>> https://www.youtube.com/watch?v=R2322YxIciQ) and would like to be 
>>> able to post the resulting video to YouTube when Mark is on PTO for 
>>> example.
>>> Therefore I'm asking the authorization to be granted access to the 
>>> Youtube account/channel (to upload the recording to the channel).
>>>
>>> Best wishes,
>>>
>>> Bruno Verachten
>>>
>>
>> -- 
>> 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/77f08589-693b-46cd-96e4-cb665587b9a9n%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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/7b20bf94-250e-4815-a481-dcfbc27e4ed8n%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-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvxTx3sL6pCuJybnx6vhsX%2BsruVRmeTQj10S9csMBP7j%2Bg%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 discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMBsfbvT6qZQ0jhWPKdho3UNYXLRKEmVVVK6_aenbdCE9xKV3g%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/86525b52-b388-46f7-a9d0-554ed9567582n%40googlegroups.com.

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

['Olblak' via Jenkins Developers]

+1  :) 

On Thu, Oct 13, 2022, at 11:39 AM, 'Stephane Merle' via Jenkins Developers 
wrote:
> +1 for me too
> good luck Alexander
> 
> On Thu, Oct 13, 2022 at 9:44 AM 'Daniel Beck' via Jenkins Developers 
>  wrote:
>> 
>> 
>> On Thu, Oct 13, 2022 at 9:11 AM Tim Jacomb  wrote:
>>> I would like to propose Alexander Brandes (@NotMyFault 
>>> ) to join the Jenkins Core team.
>> 
>> +1 
>> 
>> 
>> -- 
>> 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/CAMo7PtJFQvvfqtNixCGOk34quz7Fm_bu0as_QNOVxX%2BXY5jvwA%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/CAO%2B-N1qxoBRFwKk4%3DJdVY%2B_gns%2BCaMd8J_DC9xuWnRqzEfYDZA%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/b67d978b-bc39-4cb4-a2a3-3ad69cdf621c%40app.fastmail.com.

Re: Request for access to Zoom +YT account

['Olblak' via Jenkins Developers]

Hi Damien,
I sent you an invite.
At the moment, they are 4 owners, KK, Tyler, Oleg, and me

And 10 "managers", so it's probably a good time to review those permission


On Sun, May 22, 2022, at 1:08 PM, Damien Duportal wrote:
> Hi @Olivier @Oleg @Kohsuke (at least?),
> 
> It appears that Mark lacks the permissions to add me to the YouTube account 
> (so I might post Infra meeting recordings).
> 
> Could you add me as member of the "Jenkins" account so I’m autonomous to do 
> so? (my gmail id is damien.duportal  gmail.com).
> 
> Many thanks!
> 
> Damien
> 
>> Le 9 juin 2021 à 18:45, Damien Duportal  a écrit :
>> 
>> Thanks, credentials for Zoom received, and working as expected.
>> 
>> I now need help from someone with access to the YT channel to help me to 
>> upload the recording (I've NEVER uploaded a video on YT of my life so 
>> help/guidelines are more than welcome)
>> 
>> Damien
>> 
>> Le mercredi 9 juin 2021 à 11:42:01 UTC+2, timja...@gmail.com a écrit :
>>> I've sent Damien the zoom account details
>>> 
>>> Someone else will need to set him up on YouTube I think? (not sure if I 
>>> have access)
>>> 
>>> 
>>> On Tue, 8 Jun 2021 at 15:14, Mark Waite  wrote:
 +1 from me
 
 On Tue, Jun 8, 2021 at 7:59 AM Tim Jacomb  wrote:
> +1 from me
> 
> On Tue, 8 Jun 2021 at 14:53, Oleg Nenashev  wrote:
>> +1 from me
>> 
>> On Tuesday, June 8, 2021 at 3:41:39 PM UTC+2 damien@gmail.com wrote:
>>> 
>>> As per https://groups.google.com/g/jenkinsci-dev/c/K0wqZpL5a88 , Mark 
>>> is having limited bandwidth and I've volunteered to drive the next UX 
>>> SIG meeting until everything goes back to normal.
>>> 
>>> Therefore I'm asking the authorization to be granted access to the Zoom 
>>> account (to allow me to start the meeting and record it), and to the 
>>> Youtube account/channel (to upload the recording in the channel)?
>>> 
>>> Cheers,
>>> 
>>> Damien DUPORTAL
>>> damien@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 discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/078ff174-45e2-4980-aabd-6635784b52a2n%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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidL0khnq3NeMnwcwbe6kz2cGFqOaR5heMXOqv7_X%2BjTyQ%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 discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtELR0fdpA3NdSwey%3DU3-%2BMvCm8oCJmVLSWpzr8WYKfGzg%40mail.gmail.com
  
 .
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/NxbSC6uL0x0/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/3df8ce86-1d45-4b0a-ab1b-6a730c5faf8dn%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/DE069EC5-C5CB-42A4-8450-C0678A35BCEB%40gmail.com
>  
> .

-- 
You 

Re: Sunsetting mirror.jenkins.io in favor of get.jenkins.io

['Olblak' via Jenkins Developers]

Hey,

> One of the first steps is to change the code on the Jenkins project that uses 
> the old "mirror.jenkins.io" and change it to https://get.jenkins.io.

Is there any motivation to not just redirect traffic from mirror.jenkins.io to 
get.jenkins.io
that would only be one CNAME change.

And if you want to take extra care, we could just announce on the blogpost that 
HTTP support will be remove in one month.
Anyway the updatecenter only use HTTPS if I recall correctly.

On Thu, May 5, 2022, at 12:01 PM, Damien Duportal wrote:
> Hello dear contributors!
> 
> The infrastructure team is going, in the upcoming weeks, to sunset the 
> service "mirror.jenkins.io" in favor of get.jenkins.io.
> 
> More details can be found in this issue: 
> https://github.com/jenkins-infra/helpdesk/issues/2888.
> 
> One of the first steps is to change the code on the Jenkins project that uses 
> the old "mirror.jenkins.io" and change it to https://get.jenkins.io.
> 
> However this might have some impact and the infra team need help to review, 
> challenge and approve this change.
> 
> A first step is on the shared pipeline library: 
> https://github.com/jenkins-infra/pipeline-library/pull/374 .
> This change request might have an impact on the Jenkins Core build and the 
> test harnesses so better notifying contributors.
> 
> ETA of this 1st change is 9th of May unless there is strong reason to not to.
> 
> Many thanks in advance!
> 
> For the infra team, Damien DUPORTAL
> 
> 
> -- 
> 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/4de12a3f-160d-4b17-baeb-358e718fe884n%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/5ccc0b9d-ea9b-46c1-a3f2-cf188a532ab6%40www.fastmail.com.

Re: [ci.jenkins.io] Replace Blue Ocean in default display URL

['Olblak' via Jenkins Developers]

Hey,

I think it makes sense to default to classic Jenkins.
It could also be interesting to monitor for the coming month how many people 
still use blueocean by looking at the url  ci.jenkins.io/blue/*

On Tue, May 3, 2022, at 2:03 PM, Alexander Brandes wrote:
> +1 for changing the default URL.
> 
> If I'm navigating through the checks' integration on GitHub, I almost always 
> copy the URL to remove the "/display/redirect" part to not end up on the blue 
> ocean view. 
> 
> ~ Alex
> On Tuesday, 3 May 2022 at 11:50:31 UTC+2 damien@gmail.com wrote:
>> Hello dear contributors!
>> 
>> The Jenkins infra team recently received a request 
>> (https://github.com/jenkins-infra/helpdesk/issues/2833) to change the 
>> default display URL for ci.jenkins.io.
>> 
>> The goal of the request is to ensure that when you click on a GitHub check 
>> link related to ci.jenkins.io, then you are redirect to the classic Jenkins 
>> UI (instead of Blue Ocean).
>> 
>> Blue Ocean is still kept in ci.jenkins.io as it is still used by many (and 
>> provides features that does not exist on the classic UI as for today).
>> 
>> But since Blue Ocean is not really well maintained, chanigng the default 
>> display link would centralize the actual contribution UI effort on the 
>> classic UI by... using it !
>> 
>> Are there any voices (and if yes: why?) against this change for 
>> ci.jenkins.io?
>> 
>> For the infra-team,
>> 
>> Damien DUPORTAL
> 
> 
> -- 
> 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/9fe869d3-054c-4ede-850e-36387d433417n%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/d3e814a4-1165-4df2-89c3-5167841b79d5%40www.fastmail.com.

Re: [jenkins-infra] Re: 1Password tram for Jenkins passwords?

['Olblak' via Jenkins Developers]

+1, 
A while ago, I considered using Keepassx with shared storage but 1Password 
could be an easier approach.

On Wed, Nov 3, 2021, at 9:45 PM, 'Gavin Mogan' via Jenkins Developers wrote:
> They also have an open source program - 
> https://github.com/1Password/1password-teams-open-source
> 
> Being open source, i've heard really amazing things about bitwarden, but I 
> don't know if their pricing would support jenkins. And I get the impression 
> we wouldn't want to host it on our infra.
> 
> So +1 for 1password for me (I personally use lastpass, and bet they would 
> also be happy to sponsor).
> 
> Gavin
> 
> On Tue, Nov 2, 2021 at 12:29 PM Matt Sicker  wrote:
>> Definitely a good idea. Credentials sharing should always use a
>> dedicated password management or vault style service. 1password is
>> fairly easy to use, too.
>> 
>> On Tue, Nov 2, 2021 at 4:42 AM Oleg Nenashev  wrote:
>> >
>> > Hi all,
>> >
>> > 1Password launched a free offering open source teams: 
>> > https://github.com/1Password/1password-teams-open-source. From what I see 
>> > we are compliant with sponsorship conditions.
>> >
>> > We have quite a lot of passwords we use, especially in Advocacy & Outreach 
>> > (Zoom, Twitter accounts, etc.). It would be generally useful if we could 
>> > transfer these passwords to a shared storage so that we could share them 
>> > with people, track access and credential leaks.
>> >
>> > The same might be useful for infrastructure accounts if it don't have SSO, 
>> > and for various test accounts we have.
>> >
>> > WDYT? I thin
>> >
>> > Best regards,
>> > Oleg
>> >
>> > --
>> > 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/CAPfivLCk0iSK2yHE6GujCj361Cexwo3QhXcO6y7f6o2Okp08ww%40mail.gmail.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Infrastructure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins-infra+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web, visit 
>> https://groups.google.com/d/msgid/jenkins-infra/CACmp6koTJrcz633KvgBMVFZPLDWjrxxzfTQv3Or4QbrVFhg_pw%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/CAG%3D_Duty-jbW3CaBT9TrR4vFSjcAf-RL4BWr4sFL8-OTUk08jg%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/21640ebd-42ea-4087-8372-9b968bdf9fd8%40www.fastmail.com.

Re: Company plugins in Jenkins org

['Olblak' via Jenkins Developers]

While I don't know yet how it would work with our existing tooling, I am in 
favor of that approach and that would also be useful for other companies as 
well

On Thursday, 21 October 2021 at 13:47:24 UTC+2 jn...@cloudbees.com wrote:

> Hi all,
>
> CloudBees has a number of plugins in jenkins-ci organisation that we are 
> maintainers of.
>
> Currently when our internal teams change we need to modify multiple GitHub 
> repo settings and associated permissions RPU.  This is cumbersome (and 
> error prone) for us, and for the reviewers of the RPU PRs.
>
> I would like to propose (and ask for) a "CloudBees plugin developers" 
> group in the jenkinsci or that we can add CloudBees developers to and then 
> grant permissions to on the plugins that we maintain.  This will allow us 
> to just modify a single GitHub group and have the permissions updated in 
> all our plugins.
>
> Additionally to make RPU easier, we are planning to add support for groups 
> of users so that we would just need to modify a single "group definition 
> file" to update permissions in artifactory.
>
> This approach would then also be available to other companies with 
> multiple plugins in the Future.
>
> WDYT?
>
> /James
>

-- 
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/2b63810e-2f5b-4a39-aea8-872419a6857en%40googlegroups.com.

Re: Emeritus concept for Jenkins developers (was: Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team)

['Olblak' via Jenkins Developers]

> (though there's a couple surprising names on that list)
People on that list didn't complain when I introduce that special *team* :p 

That being said, reviewing permissions on a regular basis is important and 
having an "alumni" or an "emeritus" team is one of the best way to keep 
maintainers in the organization without taking the risk of having then with 
unneeded access.
And of course, we can easily grant more permission if needed.

So +1 for the idea 

On Tue, Sep 28, 2021, at 3:23 AM, 'Gavin Mogan' via Jenkins Developers wrote:
> Infra has an Alumni team  (though there's a couple surprising names on that 
> list) which is essentially the same thing. 
> https://github.com/orgs/jenkins-infra/teams/alumni
> Thanks for all your done, but as a non active contributor its risky to give 
> you write access to things.
> 
> Gavin
> 
> On Mon, Sep 27, 2021 at 3:03 AM Baptiste Mathus  wrote:
>> I'm not that much concerned that we wouldn't do exactly what Apache does 
>> TBH. More of an inspiration.
>> 
>> IOW, we could just create a special team with no permission of "emeritus" 
>> members. People in jenkins/core that we know have not been active since 1+ 
>> year anywhere. 
>> And when in doubt, we'd double check with these persons, and if they don't 
>> answer we'd move them to this emeritus list.
>> 
>> 
>> Baptiste
>> 
>> 
>> Le jeu. 23 sept. 2021 à 20:30, Matt Sicker  a écrit :
>>> At Apache, emeritus status is typically requested by the individual.
>>> That might be hard to emulate here if some otherwise emeritus members
>>> of Jenkins aren't here to request emeritus. Some forms of active
>>> versus inactive members could be useful, though, for code review
>>> purposes and other bookkeeping.
>>> 
>>> On Thu, Sep 23, 2021 at 5:08 AM Tim Jacomb  wrote:
>>> >
>>> > +1 we have this in jenkins-infra
>>> >
>>> > On Thu, 23 Sep 2021 at 10:28, Baptiste Mathus  wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> Following up on Jesse's comment, and as I was reflecting on this a few 
>>> >> days ago: I think we should introduce an Emeritus concept/status for 
>>> >> Jenkins core team's inactive members.
>>> >>
>>> >> That would allow "cleaning up" the list for various reasons, while still 
>>> >> recognizing the contributions of such individuals.
>>> >>
>>> >> I think, akin to Apache does in many projects, we should also have a 
>>> >> straightforward way for such members to be reinstated inthe core list 
>>> >> when they would request it.
>>> >>
>>> >> WDYT?
>>> >>
>>> >> Once we agree on this principle, we will also need to dicuss the 
>>> >> "inactive member" definition, but that's a secondary concern for now IMO.
>>> >>
>>> >> Baptiste
>>> >>
>>> >> Le mer. 22 sept. 2021 à 14:10, wfoll...@cloudbees.com 
>>> >>  a écrit :
>>> >>>
>>> >>> +1 as well, really involved in the community so it's just natural :-)
>>> >>>
>>> >>> On Wednesday, September 22, 2021 at 2:05:32 PM UTC+2 Jesse Glick wrote:
>>> 
>>>  If he is interested, absolutely +1!
>>> 
>>>  By the way there are a number of people in 
>>>  https://github.com/orgs/jenkinsci/teams/core/members who are no longer 
>>>  active in the Jenkins community and who should likely be removed.
>>> >>>
>>> >>> --
>>> >>> 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/2735a776-6bdf-485c-bdb0-96d45175ab67n%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/CANWgJS5RcWPCSPghkpyBL3TH8iwv96ogjSbunVBbAdQ0rsTh6A%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/CAH-3Bie4XJNJ_WNDmH%3DJsuid4g5w9X%3D%2B8%3DTn3odWs0gZoZLHhQ%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 
>>> 

Re: Release team members

['Olblak' via Jenkins Developers]

Hi Tim,

Thanks for driving this, I think that would be useful for me to be in the 
release team on the jenkins-ci organization

On Thu, Sep 23, 2021, at 9:48 AM, Tim Jacomb wrote:
> Hello
> 
> Continuing from 
> https://groups.google.com/g/jenkinsci-dev/c/YhXRKybGgMg/m/IRjH_VykCwAJ 
> 
> I would like to invite the previous release leads to join the release team 
> officially in jenkinsci/jenkins-infra GitHub organisations:
> 
> a release then consider stepping up for a release lead role for an LTS 
> release or joining the #jenkins-release room on Libera IRC
> 
>  * Beatriz Muñoz (@bmunozm)
> 
>  * Ildefonso Montero (@imonteroperez)
> 
>  * Mark Waite (@MarkEWaite)
> 
>  * Raihaan Shouhell (@res0nance)
> 
>  * Basil Crow (@basil)
> 
> 
> Daniel, Olivier (olblak), Wadeck, Oleg you are all in the team in 
> jenkins-infra, would you like to join the team in jenkinsci as well?
> 
> If you would like to join then please reply to this email.
> For others if you would like to get involved in a release then consider 
> stepping up for a release lead role for an LTS release or joining the 
> #jenkins-release room on Libera IRC
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieVaZAEP3wJBVzpKe1g5YvjEBcRag49vSJ-Fy8Q2%3DDQCw%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/d63ba734-1a99-45c0-bc26-4fb34b5724ca%40www.fastmail.com.

Jenkins Elections 2021

['Olblak' via Jenkins Developers]

Hi Everybody, 

The Jenkins project will elect two board members and five officers during 
upcoming elections.

If you've contributed to Jenkins prior to September 1, 2021, you're 
eligible to vote. All contributions count for eligibility! If you've helped 
others with Jenkins, tested Jenkins, documented Jenkins, reviewed the 
changes of others, or made changes yourself, you're eligible to vote.

Register to vote in the election by joining the Jenkins election voter 
group at https://community.jenkins.io/g/election-voter

Nominations are open for Jenkins board members and for Jenkins officers. 
Submit nominations by sending a message to the Jenkins elections committee 
through https://community.jenkins.io/g/election-committee

https://www.jenkins.io/blog/2021/09/20/election-period-opened/

Cheers,

-- 
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/e6ed1a10-daed-4382-8118-cb9c82b9c61cn%40googlegroups.com.

Re: Postponing 2.303.2 by two weeks

['Olblak' via Jenkins Developers]

+1

On Monday, 6 September 2021 at 14:16:46 UTC+2 Mark Waite wrote:

> +1 from me.
>
> On Mon, Sep 6, 2021 at 5:48 AM Tim Jacomb  wrote:
>
>> Sounds fine to me.
>> If no negative feedback by end of tomorrow let’s adjust the dates
>>
>> On Mon, 6 Sep 2021 at 11:26, Raul Arabaolaza  
>> wrote:
>>
>>> +1
>>>
>>> On Monday, September 6, 2021 at 12:24:24 PM UTC+2 Daniel Beck wrote:
>>>
 Hi everyone, 

 I'd like to postpone 2.303.2 by two weeks. RC would be scheduled for 
 September 22, the final release on October 6. All future scheduled dates 
 would be postponed accordingly. 

 We've done this occasionally in the past when there are scheduling or 
 availability issues, typically around Christmas, and sometimes during 
 summer or JW/DW travels. 

 In this case, I'd like to include security fixes in the release, and 
 I'm not confident we'll be done on time with their preparation. The wiki 
 infra issue[1] isn't helping either. 

 Thoughts? 

 Daniel 

 1: https://www.jenkins.io/blog/2021/09/04/wiki-attacked/ 

 -- 
>>> 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/9747100e-ae34-46f7-a9ea-9b8a6dbe4060n%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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicNn2nY%3Dhc%3D8%3DPw_9VEX1KE1hVPsjyVLj9%2Bd0O047_QWA%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/5845bf2e-25ad-4ad0-9375-b06f558bc441n%40googlegroups.com.

Jenkins Election 2021 Proposal

['Olblak' via Jenkins Developers]

Hi Everybody,

As you may guess with the title, I am looking for feedback regarding the 
upcoming election.
I would like to validate this process by next week's Governance meeting

Feel free to add your suggestion or feedback on community.jenkins.io 


Cheers

-- 
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/1bd57fb3-b4a4-4804-8e47-c16564e764den%40googlegroups.com.

Re: Sign-up for 'beta projects' in GitHub issues

['Olblak' via Jenkins Developers]

I added jenkins-infra to the waiting list 

On Wed, Jun 23, 2021, at 10:03 PM, Tim Jacomb wrote:
> Mark mentioned on Twitter he’s like to try it on Jenkins.io too 
> https://twitter.com/markewaite/status/1407780053769850882?s=21
> 
> On Wed, 23 Jun 2021 at 20:04, Tim Jacomb  wrote:
>> Hello,
>> 
>> Should we sign-up for the new beta projects in jenkinsci?
>> 
>> https://github.com/features/issues
>> 
>> Would be useful to be able to set-up more featureful boards across plugins, 
>> probably other use-cases too.
>> 
>> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bid10mD4XwChU-Yf-iL%3DMsTVkCCY_cYMga4-yi2szCykuQ%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/7fb8aa14-9b28-4b49-97a5-0fdb71a4c573%40www.fastmail.com.

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Due to personal reasons, I won't be available for the contributor summit.


On Sat, Jun 19, 2021, at 10:39 AM, Oleg Nenashev wrote:
> Hi all,
> 
> I have created the #jenkins-contributor-summit channel in the Continuous 
> Delivery Foundation Slack workspace. Anyone is welcome to join and 
> participate in the organization, planning, and async conversation. How to 
> join the CDF Slack 
> <https://github.com/jenkins-infra/jenkins.io/blob/4ae597e83870f4e86475ecd702f0895acb5c5cdf/chat/#continuous-delivery-foundation>.
>  I have also restructured the agenda in the coordination doc 
> <https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit#heading=h.j46ljtvh5tfx>
>  based on the discussion we had last week. Landing page update: 
> https://github.com/jenkins-infra/jenkins.io/pull/4429
> 
> *On my availability*: Sadly, I cannot commit on my availability during, 
> before or after the summit. The Jenkins governance board and officers are 
> informed about the situation. Personal emergency. I will do my best to help 
> where I can and to prepare the State of the Union session. Will try to 
> deliver on other action items like end user panel. Olivier Vernin will be 
> taking over the overall summit coordination, together with other org team 
> members. Thanks a lot to Olivier! As always, everyone is invited to 
> participate and contribute! How to help? 
> <https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit#heading=h.4hqgkvihqtvc>
> 
> *On Kubernetes operator.* Based on the separate conversation with Bartek, I 
> have added the breakout session of the operator. We also expect a short 
> 5-10min update during the State of The Union in the beginning of the summit.
> 
> Best regards,
> Oleg
> 
> On Thursday, June 17, 2021 at 1:39:08 PM UTC+2 Olblak wrote:
>> __
>> Hi Bartłomiej,
>> 
>> That would be really great. 
>> Vibhav is interested to present initiatives from the Coud Native SIG, maybe 
>> you could sync with him for that part
>> The sig update is around 10min max and then we have more time in a later 
>> session to go deeper on the jenkins kubernetes operator.
>> 
>> I am adding your name on the schedule for the longer session, do you already 
>> have an idea of how long you need?
>> Would 30 min work for you? 
>> 
>> 
>> 
>> On Thu, Jun 17, 2021, at 9:50 AM, 'Bartłomiej Antoniak' via Jenkins 
>> Developers wrote:
>>> Hi all,
>>> 
>>> I'm happy to take over Jenkins Kubernetes Operator part. The initial idea 
>>> was to present high-level update and further plans during opening session. 
>>> Then reserve a breakout session for the deep dive to particular topics and 
>>> longer discussion if needed.
>>> 
>>> Regards,
>>> Bartek
>>> 
>>> śr., 16 cze 2021 o 13:28 'Olblak' via Jenkins Developers 
>>>  napisał(a):
>>>> __
>>>> Same here, it makes the schedule easier from EU :p 
>>>> 
>>>> Because of the PDT timezone, I was thinking of the following topic order
>>>> 
>>>> 1. Project update 
>>>> 2. Contributor track, as this part heavily require participation from 
>>>> attendees
>>>> 3. SIG  update
>>>> followed by all presentations such as unconference,etc.
>>>> 
>>>> If we are on EDT, then it would make sense to swap Contributor track and 
>>>> SIG update so 
>>>> 1. Project Update
>>>> 2. SIG Update <- Seems more logical in terms of timeline
>>>> 3. Contributor Track <- This would be easier for folks from US West coast 
>>>> to participate
>>>>  to the contributor track. 
>>>> 
>>>> I am curious what people from APAC would prefer?
>>>> 
>>>> Again based on all the discussion I am having, I am still trying to  draft 
>>>> schedule here 
>>>> <https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Wed, Jun 16, 2021, at 12:34 PM, Tim Jacomb wrote:
>>>>> If its east coast 9am I can help more / attend some sessions :)
>>>>> 
>>>>> On Wed, 16 Jun 2021 at 11:02, Oleg Nenashev  wrote:
>>>>>> I think we can schedule it as we wish, we just need to announce it 
>>>>>> timely. East Coast 9am is my strong preference
>>>>>> 
>>>>>> On Wed, Jun 16, 2021, 11:53 'Olblak' via Jenkins Developers 
>>>&g

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Hi Bartłomiej,

That would be really great. 
Vibhav is interested to present initiatives from the Coud Native SIG, maybe you 
could sync with him for that part
The sig update is around 10min max and then we have more time in a later 
session to go deeper on the jenkins kubernetes operator.

I am adding your name on the schedule for the longer session, do you already 
have an idea of how long you need?
Would 30 min work for you? 



On Thu, Jun 17, 2021, at 9:50 AM, 'Bartłomiej Antoniak' via Jenkins Developers 
wrote:
> Hi all,
> 
> I'm happy to take over Jenkins Kubernetes Operator part. The initial idea was 
> to present high-level update and further plans during opening session. 
> Then reserve a breakout session for the deep dive to particular topics and 
> longer discussion if needed.
> 
> Regards,
> Bartek
> 
> śr., 16 cze 2021 o 13:28 'Olblak' via Jenkins Developers 
>  napisał(a):
>> __
>> Same here, it makes the schedule easier from EU :p 
>> 
>> Because of the PDT timezone, I was thinking of the following topic order
>> 
>> 1. Project update 
>> 2. Contributor track, as this part heavily require participation from 
>> attendees
>> 3. SIG  update
>> followed by all presentations such as unconference,etc.
>> 
>> If we are on EDT, then it would make sense to swap Contributor track and SIG 
>> update so 
>> 1. Project Update
>> 2. SIG Update <- Seems more logical in terms of timeline
>> 3. Contributor Track <- This would be easier for folks from US West coast to 
>> participate
>>  to the contributor track. 
>> 
>> I am curious what people from APAC would prefer?
>> 
>> Again based on all the discussion I am having, I am still trying to  draft 
>> schedule here 
>> <https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0>
>> 
>> 
>> 
>> 
>> On Wed, Jun 16, 2021, at 12:34 PM, Tim Jacomb wrote:
>>> If its east coast 9am I can help more / attend some sessions :)
>>> 
>>> On Wed, 16 Jun 2021 at 11:02, Oleg Nenashev  wrote:
>>>> I think we can schedule it as we wish, we just need to announce it timely. 
>>>> East Coast 9am is my strong preference
>>>> 
>>>> On Wed, Jun 16, 2021, 11:53 'Olblak' via Jenkins Developers 
>>>>  wrote:
>>>>> __
>>>>> Hi Everybody,
>>>>> 
>>>>> I think I am wrong since the beginning while working on the contributor 
>>>>> summit agenda. :(
>>>>> Is the contributor summit supposed to start at 9AM PDT or 9AM EDT? 
>>>>> This is "slightly" different for session that would benefit from folks 
>>>>> from EU and US west coast
>>>>>  
>>>>> 
>>>>> On Fri, Jun 11, 2021, at 9:46 PM, Baptiste Mathus wrote:
>>>>>> I'm sorry to be so late on this... I am going to write here for 
>>>>>> visibility, and I'll also add or see to add it correctly the sheet 
>>>>>> initiated by Oleg.
>>>>>> 
>>>>>> 1. I would like to help facilitate a conversation on Guava upgrade in 
>>>>>> Jenkins Core.
>>>>>> As you know, this work is already somehow started. I'd like us to take 
>>>>>> the summit opportunity to decide on next steps, approaches.
>>>>>> Our team at CloudBees is committed to help on this subject.
>>>>>> 
>>>>>> 2. Plugin EOL policy // plugin maintenance status
>>>>>> I think these two subjects would serve us as a community to keep moving 
>>>>>> Jenkins forward.
>>>>>> For the commons-digester:2.1 recent removal for instance, I think we 
>>>>>> spent a subtantial amount of effort on plugins nobody should use anymore 
>>>>>> since a long time.
>>>>>> If we had had such a policy, we could have saved a lot of energy 
>>>>>> together.
>>>>>> 
>>>>>> 3. Company/team ownership for plugins
>>>>>> As an ex-HOSTING team member and a contributor since a few years, I 
>>>>>> think we need to have a clearer stance for companies to implement a 
>>>>>> Jenkins plugin for their software.
>>>>>> It happens regularly than a company, not intimate with the Jenkins 
>>>>>> Project's governance, will request commit access to a plugin they think 
>>>>>> they own somehow. (e.g. HOSTING-901, HOSTING-346, HOSTING-288, 
>>>>>>

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Same here, it makes the schedule easier from EU :p 

Because of the PDT timezone, I was thinking of the following topic order

1. Project update 
2. Contributor track, as this part heavily require participation from attendees
3. SIG  update
followed by all presentations such as unconference,etc.

If we are on EDT, then it would make sense to swap Contributor track and SIG 
update so 
1. Project Update
2. SIG Update <- Seems more logical in terms of timeline
3. Contributor Track <- This would be easier for folks from US West coast to 
participate 
 to the contributor track. 

I am curious what people from APAC would prefer?

Again based on all the discussion I am having, I am still trying to  draft 
schedule here 
<https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0>




On Wed, Jun 16, 2021, at 12:34 PM, Tim Jacomb wrote:
> If its east coast 9am I can help more / attend some sessions :)
> 
> On Wed, 16 Jun 2021 at 11:02, Oleg Nenashev  wrote:
>> I think we can schedule it as we wish, we just need to announce it timely. 
>> East Coast 9am is my strong preference
>> 
>> On Wed, Jun 16, 2021, 11:53 'Olblak' via Jenkins Developers 
>>  wrote:
>>> __
>>> Hi Everybody,
>>> 
>>> I think I am wrong since the beginning while working on the contributor 
>>> summit agenda. :(
>>> Is the contributor summit supposed to start at 9AM PDT or 9AM EDT? 
>>> This is "slightly" different for session that would benefit from folks from 
>>> EU and US west coast
>>>  
>>> 
>>> On Fri, Jun 11, 2021, at 9:46 PM, Baptiste Mathus wrote:
>>>> I'm sorry to be so late on this... I am going to write here for 
>>>> visibility, and I'll also add or see to add it correctly the sheet 
>>>> initiated by Oleg.
>>>> 
>>>> 1. I would like to help facilitate a conversation on Guava upgrade in 
>>>> Jenkins Core.
>>>> As you know, this work is already somehow started. I'd like us to take the 
>>>> summit opportunity to decide on next steps, approaches.
>>>> Our team at CloudBees is committed to help on this subject.
>>>> 
>>>> 2. Plugin EOL policy // plugin maintenance status
>>>> I think these two subjects would serve us as a community to keep moving 
>>>> Jenkins forward.
>>>> For the commons-digester:2.1 recent removal for instance, I think we spent 
>>>> a subtantial amount of effort on plugins nobody should use anymore since a 
>>>> long time.
>>>> If we had had such a policy, we could have saved a lot of energy together.
>>>> 
>>>> 3. Company/team ownership for plugins
>>>> As an ex-HOSTING team member and a contributor since a few years, I think 
>>>> we need to have a clearer stance for companies to implement a Jenkins 
>>>> plugin for their software.
>>>> It happens regularly than a company, not intimate with the Jenkins 
>>>> Project's governance, will request commit access to a plugin they think 
>>>> they own somehow. (e.g. HOSTING-901, HOSTING-346, HOSTING-288, 
>>>> HOSTING-134, and we could go on)
>>>> Only then they discover that from the Jenkins Project's standpoint, they 
>>>> do not *exist*. An ex-employee that may have even left a given company 
>>>> could disagree to let commit rights go and they would be entitled to this 
>>>> (fortunately didn't happen yet, to my knowledge).
>>>> 
>>>> The other case I've got in mind is the "team" concept. That's the one I'm 
>>>> most interested in personally. For example, when people move between teams 
>>>> in our company etc., we usually need to update many files in RPU and 
>>>> request commit access in various repositories.
>>>> If we could have an official concept for teams within the Jenkins Project, 
>>>> I think we could set up special GH teams (for example one for ours at 
>>>> CloudBees) + create possibly such a concept for it inside RPU to define 
>>>> this only once.
>>>> I think this is already doable (we already have the core team within GH 
>>>> e.g.), and we could request an ad-hoc implementation and move on. But I 
>>>> think there's merit in defining something generalized for the Jenkins 
>>>> Project's governance.
>>>> 
>>>> Thanks for reading :). I definitely didn't plan to send such a long email.
>>>> 
>>>> Have a great weeked everyone.   
>>>> 
>>>> Le jeu. 10 juin 2021

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Hi Everybody,

I think I am wrong since the beginning while working on the contributor summit 
agenda. :(
Is the contributor summit supposed to start at 9AM PDT or 9AM EDT? 
This is "slightly" different for session that would benefit from folks from EU 
and US west coast
 

On Fri, Jun 11, 2021, at 9:46 PM, Baptiste Mathus wrote:
> I'm sorry to be so late on this... I am going to write here for visibility, 
> and I'll also add or see to add it correctly the sheet initiated by Oleg.
> 
> 1. I would like to help facilitate a conversation on Guava upgrade in Jenkins 
> Core.
> As you know, this work is already somehow started. I'd like us to take the 
> summit opportunity to decide on next steps, approaches.
> Our team at CloudBees is committed to help on this subject.
> 
> 2. Plugin EOL policy // plugin maintenance status
> I think these two subjects would serve us as a community to keep moving 
> Jenkins forward.
> For the commons-digester:2.1 recent removal for instance, I think we spent a 
> subtantial amount of effort on plugins nobody should use anymore since a long 
> time.
> If we had had such a policy, we could have saved a lot of energy together.
> 
> 3. Company/team ownership for plugins
> As an ex-HOSTING team member and a contributor since a few years, I think we 
> need to have a clearer stance for companies to implement a Jenkins plugin for 
> their software.
> It happens regularly than a company, not intimate with the Jenkins Project's 
> governance, will request commit access to a plugin they think they own 
> somehow. (e.g. HOSTING-901, HOSTING-346, HOSTING-288, HOSTING-134, and we 
> could go on)
> Only then they discover that from the Jenkins Project's standpoint, they do 
> not *exist*. An ex-employee that may have even left a given company could 
> disagree to let commit rights go and they would be entitled to this 
> (fortunately didn't happen yet, to my knowledge).
> 
> The other case I've got in mind is the "team" concept. That's the one I'm 
> most interested in personally. For example, when people move between teams in 
> our company etc., we usually need to update many files in RPU and request 
> commit access in various repositories.
> If we could have an official concept for teams within the Jenkins Project, I 
> think we could set up special GH teams (for example one for ours at 
> CloudBees) + create possibly such a concept for it inside RPU to define this 
> only once.
> I think this is already doable (we already have the core team within GH 
> e.g.), and we could request an ad-hoc implementation and move on. But I think 
> there's merit in defining something generalized for the Jenkins Project's 
> governance.
> 
> Thanks for reading :). I definitely didn't plan to send such a long email.
> 
> Have a great weeked everyone.   
> 
> Le jeu. 10 juin 2021 à 14:27, Kara de la Marck  a 
> écrit :
>> Thanks for your suggestion, Oleg!
>> 
>> It's likely better for us to keep all the updates together for the 
>> Contributors Summit, that way they will be easier to consume for all 
>> interested parties.
>> 
>> Would it be possible for a contributor who can't make it on the 25th to 
>> record an update on behalf of a SIG or track?  And that this pre-recorded 
>> update would be shown during the allocated time on the 25th?
>>  
>> 
>> On Thu, Jun 10, 2021 at 2:03 AM Oleg Nenashev  wrote:
>>> Hi Kara,
>>> 
>>> Thanks for the feedback and for helping with the Cloud Native SIG! I 
>>> understand the timezones are imperfect. Apart from moving a meeting to an 
>>> earlier slot, we have an option to do the Cloud Native SIG meeting on 
>>> Saturday, Jun 26.
>>> 
>>> I can host meetings if they are after 4AM UTC. Maybe Rick or Himandri would 
>>> be also available.
>>> 
>>> BR, Oleg
>>> 
>>> 
>>> On Wed, Jun 9, 2021, 21:50 Kara de la Marck  
>>> wrote:
>>>> Hi all,
>>>> 
>>>> Thank you for organizing the Contributor Summit and its schedule, Oleg and 
>>>> Olivier. 
>>>> 
>>>> I'm very happy to lead on the Cloud Native track to ensure that we have a 
>>>> speaker to summarize recent highlights in the Cloud Native SIG; ideally, 
>>>> this would be an active community member.  
>>>> 
>>>> Please note that the time as currently scheduled will be too late for our 
>>>> Cloud Native SIG participants and contributors in India (and APAC 
>>>> generally). 
>>>> 
>>>> 
>>>> 
>>>> On Wed, Jun 9, 2021 at 11:48 AM 'Olblak' via Jenkins Devel

Re: Using JDK 11 instead of JDK 8 in default docker images

['Olblak' via Jenkins Developers]

What the current state here?
Looks like the docker image still use java 8 by default but the helm chart 
switched to java 11

Should we talk about switching to java11 by default during the contributor 
summit?

On Monday, 10 May 2021 at 15:47:41 UTC+2 timja...@gmail.com wrote:

> What metric would people consider? 
>
> 0? Few new issues? From personal experience on Java 11 I have never hit 
> the above issues (apart from illegal reflective access log messages) 
>
> Query I used to look:
>
> https://issues.jenkins.io/browse/JENKINS-64831?filter=22940=labels%20in%20(java11-compatibility)%20and%20resolution%20is%20EMPTY
>
> On Mon, 10 May 2021 at 13:31, Jesse Glick  wrote:
>
>> On Sun, May 9, 2021 at 4:10 AM Tim Jacomb  wrote:
>>
>>> encourage existing users to migrate
>>>
>>
>> Feels a bit premature when the list of `java11-compatibility` issues 
>> still includes bugs in core and widely used plugins.
>>
>> (The only ones I have personal experience with are JENKINS-61212 
>> , which should only 
>> affect users terminating TLS in Jenkins, rather than a reverse 
>> proxy/ingress which I suppose is more customary; and JENKINS-57139 
>>  which affects the GUI 
>> agent installers that would be lightly deprecated in JEP-230 but for now 
>> remain in core.)
>>
>> -- 
>>
> 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/CANfRfr0w-YsTD3odTAJouMGG2QZLRpq85Q6ynp8pzFEk0vJgzg%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/b61e8db2-0c93-4e7f-9147-6ce662c1acfcn%40googlegroups.com.

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Thanks, Oleg for driving this. 

Yesterday, Mark suggested to me to move the contributor track as early as 
possible to have as many people from AMER and EMEA in an interactive session.
This an idea that I like very much and I would like to discuss it tomorrow. 
So we would have "project update", "contributor track", "SIG update", "CDF 
project collaboration" as I am suggesting in the google sheet.



On Wed, Jun 9, 2021, at 6:45 AM, Oleg Nenashev wrote:
> Thanks to Olivier for the contributions and willing to help! Based on the 
> feedback in the voting poll, I created a meeting on Thursday, 1PM UTC. At 
> this meeting we will agree on the agenda and split the 
> organization/moderation tasks. Everyone is welcome to participate, and I will 
> also try to record this meeting.
> 
> Links:
> 
> * [Calendar 
> Link](https://calendar.google.com/event?action=TEMPLATE=NzJqczZjZjY1ZDBrYnU1dTk3amowdjEycHMgNHNzMTJmMG1xcjN0YnAxdDJmZTM2OXNsZjRAZw=4ss12f0mqr3tbp1t2fe369slf4%40group.calendar.google.com)
> * Zoom: 
> [https://zoom.us/j/92075127451](https://www.google.com/url?q=https://zoom.us/j/92075127451=D=calendar=2=AOvVaw0vmVjHpVhjIfQltFhxiNL8)
> * [Coordination 
> doc](https://www.google.com/url?q=https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit?usp%3Dsharing=D=calendar=2=AOvVaw1CixKPCaFPv2WOYUWlY14h)
> * [Contributor Summit 
> Schedule](https://www.google.com/url?q=https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit?usp%3Dsharing=D=calendar=2=AOvVaw2OIj6N3yj8cCjKP5YpNUSC)
> * [Event landing 
> page](https://www.google.com/url?q=https://www.jenkins.io/events/contributor-summit/=D=calendar=2=AOvVaw3INLbGY58ZLcGoCUXTX7iy)
> 
> On Mon, Jun 7, 2021 at 10:48 AM 'Olblak' via Jenkins Developers 
>  wrote:
>> __
>> Hi Everybody, 
>> 
>> I started a draft for the Contributor summit schedule.
>> https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0
>> 
>> Feel free to comment if
>> - A specific session should or should not be present.
>> - A timeslot allocated to a specific session is too long or too short
>> - You know a good person of contact for each session
>> - Anything that you may think of :)
>> 
>> 
>> 
>> On Mon, Jun 7, 2021, at 9:06 AM, 'Olblak' via Jenkins Developers wrote:
>>>> Lemme work on that. I could create a GitHub repo with issues for picking 
>>>> up.
>>>> It can be a quite good way for onboarding of new event contributors. What 
>>>> do you think?
>>> 
>>> I wouldn't bother with that.
>>> CDcon is in three weeks so we have two weeks to prepare for the contributor 
>>> summit.
>>> Let stick to the google document and maybe create a google sheet to work on 
>>> the schedule.
>>> 
>>> I think at this stage the best way to help is to either propose topics that 
>>> should be covered and identify the correct person to lead those topics. 
>>> I would be interested to know from RedHat and VirtusLab their vision on the 
>>> Jenkins operator.
>>> I would be interested to know how to prepare next Jenkins (online) meetup. 
>>> What people learned about running online event, etc...
>>> I would be interested to have a session on "howto" contribute to Jenkins, 
>>> targeting new contributors and that would also be a good opportunity to 
>>> have interactive session.  
>>> 
>>>> I started a Doodle for the first coordination call, please vote for the 
>>>> slots here: 
>>>> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
>>> Thank you for the poll, you were faster than me :D 
>>> 
>>> 
>>>> Yes, we need to build the schedule and to confirm the timeslots. Will 
>>>> start a Google Sheet or a Google Calendar for it.
>>> Let me handle that, and I'll put a link to the google document
>>> 
>>> 
>>> On Sun, Jun 6, 2021, at 6:49 PM, Oleg Nenashev wrote:
>>>> Hi all, thanks for the interest and feedback! Any contributions will be 
>>>> appreciated. I started a Doodle for the first coordination call, please 
>>>> vote for the slots here: 
>>>> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
>>>> 
>>>> Answers below:
>>>> 
>>>> > I would like to help as, how do I can get started?
>>>> > I could help with some stuff before, during, and after the event, simply 
>>>> > let me know what to do.
>>>> 
>>>> Lemme wo

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Hi Everybody, 

I started a draft for the Contributor summit schedule.
https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0

Feel free to comment if
- A specific session should or should not be present.
- A timeslot allocated to a specific session is too long or too short
- You know a good person of contact for each session
- Anything that you may think of :)



On Mon, Jun 7, 2021, at 9:06 AM, 'Olblak' via Jenkins Developers wrote:
>> Lemme work on that. I could create a GitHub repo with issues for picking up.
>> It can be a quite good way for onboarding of new event contributors. What do 
>> you think?
> 
> I wouldn't bother with that.
> CDcon is in three weeks so we have two weeks to prepare for the contributor 
> summit.
> Let stick to the google document and maybe create a google sheet to work on 
> the schedule.
> 
> I think at this stage the best way to help is to either propose topics that 
> should be covered and identify the correct person to lead those topics. 
> I would be interested to know from RedHat and VirtusLab their vision on the 
> Jenkins operator.
> I would be interested to know how to prepare next Jenkins (online) meetup. 
> What people learned about running online event, etc...
> I would be interested to have a session on "howto" contribute to Jenkins, 
> targeting new contributors and that would also be a good opportunity to have 
> interactive session.  
> 
>> I started a Doodle for the first coordination call, please vote for the 
>> slots here: 
>> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
> Thank you for the poll, you were faster than me :D 
> 
> 
>> Yes, we need to build the schedule and to confirm the timeslots. Will start 
>> a Google Sheet or a Google Calendar for it.
> Let me handle that, and I'll put a link to the google document
> 
> 
> On Sun, Jun 6, 2021, at 6:49 PM, Oleg Nenashev wrote:
>> Hi all, thanks for the interest and feedback! Any contributions will be 
>> appreciated. I started a Doodle for the first coordination call, please vote 
>> for the slots here: 
>> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
>> 
>> Answers below:
>> 
>> > I would like to help as, how do I can get started?
>> > I could help with some stuff before, during, and after the event, simply 
>> > let me know what to do.
>> 
>> Lemme work on that. I could create a GitHub repo with issues for picking up.
>> It can be a quite good way for onboarding of new event contributors. What do 
>> you think?
>> 
>> > My understanding is, we need validation from the different speakers (once 
>> > we agree on the agenda). Is this right?
>> 
>> Yes, we need to build the schedule and to confirm the timeslots. Will start 
>> a Google Sheet or a Google Calendar for it.
>> 
>> > If I understand correctly the big picture of the day would be something 
>> > like...
>> 
>> Yes. More fine grain plan is in the Google Doc
>> 
>> > Regarding event capacity,  inside the document, It's mentioned that we 
>> > expect 300participants. ...  I guess the closest we'll be to the event and 
>> > bigger that number will be and I worry to use Zoom for that.
>> 
>> 300 is the maximum expectation based on what we can host in Zoom. Actually 
>> the current limit is 500 for Zoom Webinar if we ditch the interactive part 
>> in the opening. We can also broadcast to YouTube if needed.
>> 
>>  > Do we already have a better estimation of how many people registered for 
>> the contributor summit?
>> 
>> According to the CDF, currently we have about 700 registrations. Do not hold 
>> your breadth, the show up rate is likely to be low (4th day of cdCon and the 
>> specific agenda).
>> 
>> 
>> 
>> 
>> On Sunday, June 6, 2021 at 12:49:03 PM UTC+2 kuisat...@gmail.com wrote:
>>> Hi,
>>> 
>>> I could help with some stuff before, during, and after the event, simply 
>>> let me know what to do.
>>> 
>>> Thanks
>>> El viernes, 4 de junio de 2021 a las 23:22:43 UTC+2, Oleg Nenashev escribió:
>>>> Dear all,
>>>> 
>>>> As you know, we will be organizing the Jenkins contributor summit on June 
>>>> 25th (landing page <https://www.jenkins.io/events/contributor-summit/>). I 
>>>> would like to make it a quite big contributor event where we agree on some 
>>>> key Jenkins topics, e.g. security or API/plugin deprecation/EoL policy. 
>>>> There is also interest in contributing onboa

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

> Lemme work on that. I could create a GitHub repo with issues for picking up.
> It can be a quite good way for onboarding of new event contributors. What do 
> you think?

I wouldn't bother with that.
CDcon is in three weeks so we have two weeks to prepare for the contributor 
summit.
Let stick to the google document and maybe create a google sheet to work on the 
schedule.

I think at this stage the best way to help is to either propose topics that 
should be covered and identify the correct person to lead those topics. 
I would be interested to know from RedHat and VirtusLab their vision on the 
Jenkins operator.
I would be interested to know how to prepare next Jenkins (online) meetup. What 
people learned about running online event, etc...
I would be interested to have a session on "howto" contribute to Jenkins, 
targeting new contributors and that would also be a good opportunity to have 
interactive session.  

> I started a Doodle for the first coordination call, please vote for the slots 
> here: https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
Thank you for the poll, you were faster than me :D 


> Yes, we need to build the schedule and to confirm the timeslots. Will start a 
> Google Sheet or a Google Calendar for it.
Let me handle that, and I'll put a link to the google document


On Sun, Jun 6, 2021, at 6:49 PM, Oleg Nenashev wrote:
> Hi all, thanks for the interest and feedback! Any contributions will be 
> appreciated. I started a Doodle for the first coordination call, please vote 
> for the slots here: 
> https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll_medium=link
> 
> Answers below:
> 
> > I would like to help as, how do I can get started?
> > I could help with some stuff before, during, and after the event, simply 
> > let me know what to do.
> 
> Lemme work on that. I could create a GitHub repo with issues for picking up.
> It can be a quite good way for onboarding of new event contributors. What do 
> you think?
> 
> > My understanding is, we need validation from the different speakers (once 
> > we agree on the agenda). Is this right?
> 
> Yes, we need to build the schedule and to confirm the timeslots. Will start a 
> Google Sheet or a Google Calendar for it.
> 
> > If I understand correctly the big picture of the day would be something 
> > like...
> 
> Yes. More fine grain plan is in the Google Doc
> 
> > Regarding event capacity,  inside the document, It's mentioned that we 
> > expect 300participants. ...  I guess the closest we'll be to the event and 
> > bigger that number will be and I worry to use Zoom for that.
> 
> 300 is the maximum expectation based on what we can host in Zoom. Actually 
> the current limit is 500 for Zoom Webinar if we ditch the interactive part in 
> the opening. We can also broadcast to YouTube if needed.
> 
>  > Do we already have a better estimation of how many people registered for 
> the contributor summit?
> 
> According to the CDF, currently we have about 700 registrations. Do not hold 
> your breadth, the show up rate is likely to be low (4th day of cdCon and the 
> specific agenda).
> 
> 
> 
> 
> On Sunday, June 6, 2021 at 12:49:03 PM UTC+2 kuisat...@gmail.com wrote:
>> Hi,
>> 
>> I could help with some stuff before, during, and after the event, simply let 
>> me know what to do.
>> 
>> Thanks
>> El viernes, 4 de junio de 2021 a las 23:22:43 UTC+2, Oleg Nenashev escribió:
>>> Dear all,
>>> 
>>> As you know, we will be organizing the Jenkins contributor summit on June 
>>> 25th (landing page ). I 
>>> would like to make it a quite big contributor event where we agree on some 
>>> key Jenkins topics, e.g. security or API/plugin deprecation/EoL policy. 
>>> There is also interest in contributing onboarding events and to have joint 
>>> sessions focused on interoperability and on end user experiences.Full 
>>> coordination document 
>>> .
>>> 
>>> The event is in 3 weeks. The preparation was delayed by some professional 
>>> and personal events, and also the increased GSoC workload. There are a few 
>>> contributors who planned to dedicate time to help with hosting the event, 
>>> but unfortunately they will not be able to dedicate enough time. If we want 
>>> to organize a decent event, more organizers are needed! Beow you can find 
>>> several activities where help is needed, 
>>> 
>>> Before the summit:
>>>  * Finalizing the agenda
>>>  * Coordinating the schedule with presenters
>>>  * Finalizing the end users presentation agenda
>>>  * Getting the event promoted in the community channels
>>>  * Working with@Alyssa Tong and the CDF to deliver swag to key summit 
>>> contributors
>>>  * Facilitating conversations
>>>  * Coordinating hosting of the newcomer track. IIUC Mark will be no longer 
>>> able to drive that as we discussed with him initially
>>> During the event:

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

['Olblak' via Jenkins Developers]

Hi Oleg, 

Thanks for starting this discussion, as a first step, I would like to help with 
finalizing the agenda.
My understanding is, we need validation from the different speakers (once we 
agree on the agenda).
Is this right? 

If I understand correctly the big picture of the day would be something like.

Project Update from
 1. Board member and officer
 2. Sub-project or SIG
 3. Round Table on specific initiatives that we want to see coming. For 
instance, in your documentation you highlighted things such as Java 17, 
Jenkins, maybe other people have topic suggestions as well. 

Regarding event capacity,  inside the document, It's mentioned that we expect 
300participants.
Do we already have a better estimation of how many people registered for the 
contributor summit? 
I guess the closest we'll be to the event and bigger that number will be and I 
worry to use Zoom for that.

During the event, I'll be available to help moderate talks.

Cheers


On Fri, Jun 4, 2021, at 11:22 PM, Oleg Nenashev wrote:
> Dear all,
> 
> As you know, we will be organizing the Jenkins contributor summit on June 
> 25th (landing page ). I 
> would like to make it a quite big contributor event where we agree on some 
> key Jenkins topics, e.g. security or API/plugin deprecation/EoL policy. There 
> is also interest in contributing onboarding events and to have joint sessions 
> focused on interoperability and on end user experiences.Full coordination 
> document 
> .
> 
> The event is in 3 weeks. The preparation was delayed by some professional and 
> personal events, and also the increased GSoC workload. There are a few 
> contributors who planned to dedicate time to help with hosting the event, but 
> unfortunately they will not be able to dedicate enough time. If we want to 
> organize a decent event, more organizers are needed! Beow you can find 
> several activities where help is needed, 
> 
> Before the summit:
>  * Finalizing the agenda
>  * Coordinating the schedule with presenters
>  * Finalizing the end users presentation agenda
>  * Getting the event promoted in the community channels
>  * Working with@Alyssa Tong and the CDF to deliver swag to key summit 
> contributors
>  * Facilitating conversations
>  * Coordinating hosting of the newcomer track. IIUC Mark will be no longer 
> able to drive that as we discussed with him initially
> During the event:
>  * Hosting / Moderating the event
>  * Moderating the breakout rooms
>  * Speaking about projects, SIGs and their statuses
> After the event:
>  * Processing and publishing recordings
>  * Writing a summary blogpost
>  * Swag logistics
>  * Capturing follow-ups on the Jenkins roadmap, creating follow-up tasks
> Please respond to this thread if you would be willing to dedicate some time 
> and to contribute to the event.Please feel free to comment and suggest 
> changes in the.coordination document 
> .
> 
> Thanks for your time,
> Oleg Nenashev
> Acting Jenkins Events Officer
> 
> 

> -- 
> 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/CAPfivLCdZ51%3Dztvq%3DqOrB9KL8dAZSo3QQE_%2BvqEEoBVRZwomuQ%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/b3d60935-5b40-4632-9e7a-7eee48b1d76c%40www.fastmail.com.

Re: Discourse as the default communication channel?

['Olblak' via Jenkins Developers]

After additional testing, I decided to allow user registration, on 
community.jenkins.io.
I needed it to test the Github integration.
We can still revert that decision if needed



On Fri, May 28, 2021, at 1:57 PM, 'Olblak' via Jenkins Developers wrote:
> Hi Oleg, 
> 
> Could you elaborate 
> > experiment with language community channels
> 
> > experiment user outreach tools
> Do you have something in mind? 
> 
> On Fri, May 28, 2021, at 1:00 PM, Oleg Nenashev wrote:
>> I would be interested to particupate as the Events officer. I would like to 
>> experiment with language community channels and user outreach tools.
>> 
>> Thanks to everyone for driving this!
>> 
>> 
>> On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers 
>>  wrote:
>>> __
>>> I would like to highlight the discussion about the different possible 
>>> authentication with an option to vote
>>> -> https://community.jenkins.io/t/authentication-method-used/36
>>> 
>>> I understand not everybody at this point will be able to vote directly from 
>>> Discourse so feel free to either request access to be part of the 
>>> evaluation process or just provide feedback here.
>>> 
>>> At this stage, Bruce, Gavin, Tim and I have admin access and can send 
>>> invites.
>>> Once further in the process, we'll reevaluate admin access.
>>> 
>>> Cheers
>>> 
>>> 
>>> On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote:
>>>> I'd like to be part of the test.
>>>> 
>>>> On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers 
>>>>  wrote:
>>>>> The tech it uses can give you pretty live updates, but its designed as a 
>>>>> forum.
>>>>> 
>>>>> I've sent you a DM on IRC with an invite link for now.
>>>>> 
>>>>> 
>>>>> 
>>>>> On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
>>>>>> I would like access please. Just a question, as I am very unfamiliar 
>>>>>> with Discourse. Is it a real time communication medium, a la IRC, or 
>>>>>> something more akin to a forum? 
>>>>>> 
>>>>>> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers 
>>>>>>  wrote:
>>>>>>> For whoever is interested to participate to the Discourse project, 
>>>>>>> we started discussing over there as a way to test it and get more 
>>>>>>> familiar with the tool.
>>>>>>> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>>>>>>> 
>>>>>>> Feel free to request an access as I didn't have the time yet to really 
>>>>>>> investigate the consequences of the different authentication methods.
>>>>>>> 
>>>>>>> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
>>>>>>> > Hi Bruce, 
>>>>>>> > 
>>>>>>> > Thank you for stepping up, you already provided a lot of information 
>>>>>>> > here.
>>>>>>> > And let's not assume we all know everything about discourse as we 
>>>>>>> > definitely don't.
>>>>>>> > As you are interested to help with this project, I'll send you an 
>>>>>>> > invite to "community.jenkins.io".
>>>>>>> > 
>>>>>>> > As long as we don't have an agreement on the authentication 
>>>>>>> > mechanism, 
>>>>>>> > I'll work on invite-only.
>>>>>>> > 
>>>>>>> > Regarding identifying what we expected from Discourse, Bruce made a 
>>>>>>> > good statement that discourse is what we want it to be, so here what 
>>>>>>> > I 
>>>>>>> > would like it to solve.
>>>>>>> > I would like to easily identify and participate in discussion about 
>>>>>>> > topics that interested me across different sub-project. So as an 
>>>>>>> > initial step, Oleg suggestion seems right to me.
>>>>>>> >  
>>>>>>> > On my side, I'll investigate the different authentication options. 
>>>>>>> > Today during the infrastructure Oleg made a good remark,  we would 
>>>>>>> > like 
>&g

Re: Discourse as the default communication channel?

['Olblak' via Jenkins Developers]

Hi Oleg, 

Could you elaborate 
> experiment with language community channels

> experiment user outreach tools
Do you have something in mind? 

On Fri, May 28, 2021, at 1:00 PM, Oleg Nenashev wrote:
> I would be interested to particupate as the Events officer. I would like to 
> experiment with language community channels and user outreach tools.
> 
> Thanks to everyone for driving this!
> 
> 
> On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers 
>  wrote:
>> __
>> I would like to highlight the discussion about the different possible 
>> authentication with an option to vote
>> -> https://community.jenkins.io/t/authentication-method-used/36
>> 
>> I understand not everybody at this point will be able to vote directly from 
>> Discourse so feel free to either request access to be part of the evaluation 
>> process or just provide feedback here.
>> 
>> At this stage, Bruce, Gavin, Tim and I have admin access and can send 
>> invites.
>> Once further in the process, we'll reevaluate admin access.
>> 
>> Cheers
>> 
>> 
>> On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote:
>>> I'd like to be part of the test.
>>> 
>>> On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers 
>>>  wrote:
>>>> The tech it uses can give you pretty live updates, but its designed as a 
>>>> forum.
>>>> 
>>>> I've sent you a DM on IRC with an invite link for now.
>>>> 
>>>> 
>>>> 
>>>> On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
>>>>> I would like access please. Just a question, as I am very unfamiliar with 
>>>>> Discourse. Is it a real time communication medium, a la IRC, or something 
>>>>> more akin to a forum? 
>>>>> 
>>>>> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers 
>>>>>  wrote:
>>>>>> For whoever is interested to participate to the Discourse project, 
>>>>>> we started discussing over there as a way to test it and get more 
>>>>>> familiar with the tool.
>>>>>> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>>>>>> 
>>>>>> Feel free to request an access as I didn't have the time yet to really 
>>>>>> investigate the consequences of the different authentication methods.
>>>>>> 
>>>>>> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
>>>>>> > Hi Bruce, 
>>>>>> > 
>>>>>> > Thank you for stepping up, you already provided a lot of information 
>>>>>> > here.
>>>>>> > And let's not assume we all know everything about discourse as we 
>>>>>> > definitely don't.
>>>>>> > As you are interested to help with this project, I'll send you an 
>>>>>> > invite to "community.jenkins.io".
>>>>>> > 
>>>>>> > As long as we don't have an agreement on the authentication mechanism, 
>>>>>> > I'll work on invite-only.
>>>>>> > 
>>>>>> > Regarding identifying what we expected from Discourse, Bruce made a 
>>>>>> > good statement that discourse is what we want it to be, so here what I 
>>>>>> > would like it to solve.
>>>>>> > I would like to easily identify and participate in discussion about 
>>>>>> > topics that interested me across different sub-project. So as an 
>>>>>> > initial step, Oleg suggestion seems right to me.
>>>>>> >  
>>>>>> > On my side, I'll investigate the different authentication options. 
>>>>>> > Today during the infrastructure Oleg made a good remark,  we would 
>>>>>> > like 
>>>>>> > to ideally move away from maintaining our Ldap service and we would 
>>>>>> > like to offer more alternatives than just using a Github account so 
>>>>>> > maybe using Linux foundation accounts would be better.
>>>>>> > 
>>>>>> > 
>>>>>> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
>>>>>> > > Ha, so I was. Oops!
>>>>>> > > 
>>>>>> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
>>>>>> > >  wrote:
>>>>>> &

Re: Discourse as the default communication channel?

['Olblak' via Jenkins Developers]

For whoever is interested to participate to the Discourse project, 
we started discussing over there as a way to test it and get more familiar with 
the tool.
-> https://community.jenkins.io/t/discussion-about-categories/27/12

Feel free to request an access as I didn't have the time yet to really 
investigate the consequences of the different authentication methods.

On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
> Hi Bruce, 
> 
> Thank you for stepping up, you already provided a lot of information 
> here.
> And let's not assume we all know everything about discourse as we 
> definitely don't.
> As you are interested to help with this project, I'll send you an 
> invite to "community.jenkins.io".
> 
> As long as we don't have an agreement on the authentication mechanism, 
> I'll work on invite-only.
> 
> Regarding identifying what we expected from Discourse, Bruce made a 
> good statement that discourse is what we want it to be, so here what I 
> would like it to solve.
> I would like to easily identify and participate in discussion about 
> topics that interested me across different sub-project. So as an 
> initial step, Oleg suggestion seems right to me.
>  
> On my side, I'll investigate the different authentication options. 
> Today during the infrastructure Oleg made a good remark,  we would like 
> to ideally move away from maintaining our Ldap service and we would 
> like to offer more alternatives than just using a Github account so 
> maybe using Linux foundation accounts would be better.
> 
> 
> On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
> > Ha, so I was. Oops!
> > 
> > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
> >  wrote:
> > >
> > > Matt. It's often a confusion point. Discourse is more like a form/mailing 
> > > list type thing. Discord is realtime communication. Sounds like your 
> > > describing discord.
> > >
> > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker,  wrote:
> > >>
> > >> I’ve never used Discourse outside of video games, but it seems easier to 
> > >> set up public communities on than Slack or other things we’ve tried here 
> > >> so far. While in theory I’d prefer something open like Matrix, I do 
> > >> agree that we should try to minimize the number of services to maintain 
> > >> ourselves.
> > >>
> > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev  
> > >> wrote:
> > >>>
> > >>> Hi all,
> > >>>
> > >>> Thanks to Olivier for starting this discussion and for confirming 
> > >>> sponsorship for Discourse. This is definitely something we could use to 
> > >>> address the current sprawl of Jenkins communication channels. Many 
> > >>> channels like User Mailing list, some SIG mailing lists and many Gitter 
> > >>> channels could be replaced by discourse. So I am +1 for starting 
> > >>> evaluation.
> > >>>
> > >>>
> > >>> > 2) Configure the right level of Categories, as a first iteration I 
> > >>> > would like to focus on Jenkins users but we could extend it to 
> > >>> > Jenkins contributors as well.
> > >>>
> > >>> As Bruce said above, setting up a proper structure and moderation 
> > >>> process is essential to the success of Discourse. Before we make it 
> > >>> official, we should try it out and see how to better structure the 
> > >>> communication channels. IMHO any interested contributor with Discourse 
> > >>> expertise is welcome to participate in this effort. And thanks for 
> > >>> stepping up Bruce!
> > >>>
> > >>> My notes:
> > >>>
> > >>> I would recommend creating categories for SIGs, sub-projects and 
> > >>> outreach programs right away.
> > >>> It would be great to create generic categories like "Jenkins Pipeline" 
> > >>> or "Jenkins on Kubernetes". Plugins structure should be secondary there
> > >>> Some plugins and components may need sub-categories. Likely these would 
> > >>> be tool integration plugins (e.g. "Git plugins")
> > >>> TBD: Creating a Governance category? It is feasible, but I am not sure 
> > >>> how dit aligns with the current open governance approach through this 
> > >>> mailing list and meetings
> > >>>
> > >>> I am happy to be a guinea pig for s

Re: Migrate chat channels from freenode to libera.chat

['Olblak' via Jenkins Developers]

Hi Tim,

Thanks for bootstrapping this, I definitely support moving from Freenode to 
Libera.chat.
I have a limited bandwidth capacity at the moment but I'll try to help as soon 
as I can.
I think it's better to first move away from Freenode and then start a 
discussion about the default communication channel we want to use.



On Wed, May 26, 2021, at 12:56 PM, Tim Jacomb wrote:
> Hi all,
> 
> I would like to propose moving the following channels that currently live on 
> freenode to libera.chat:
>  * #jenkins
>  * #jenkins-hosting
>  * #jenkins-infra
>  * #jenkins-release
> There's been some very user / FOSS hostile behaviour from the owner of 
> freenode, latest example can be seen in 
> https://news.ycombinator.com/item?id=27286628.
> 
> Implementation is:
>  * Update jenkins.io
>  * Let people currently in the channel know
>  * Update ircbot to connect to new server and create new credentials
> There's been other conversations about moving the community to places like 
> discourse and replacing the ircbot with Jira webhooks, but I don't believe 
> that this is the right thread for those.
> 
> ircbot does more than just hosting, it manages github permissions and Jira 
> components as well.
> Any changes to ircbot require or Jira webhook integration requires interested 
> contributors to build solutions.
> 
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidgAHKm6t8iwB91cQ%3DO89XXEbo%2B6SX33AR_ZofsE-Pq%3DQ%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/b82ed260-c747-4f57-945a-d94e8f960faf%40www.fastmail.com.

Discourse as the default communication channel?

['Olblak' via Jenkins Developers]

Hi Everybody,

I am really glad to share that "Civilized Discourse Construction Kit, Inc", the 
company behind Discourse
offered to sponsor the Jenkins project with the business "tier"
-> https://www.discourse.org/pricing

This is a very nice opportunity to "organize" discussions happening across the 
community. 
Different people have different expectations so feel free to raise your voice 
and share your ideas.

What we want to achieve is better communication with the Jenkins community, at 
the moment a lot of valuable information is lost in the various mailing list, 
Gitter, IRC, etc.
By using Discourse it would allow to centralize questions in one place and 
regroup them by categories 

At this stage, we are still in exploratory mode, so if you have any experience 
with the tool or just want to help 
feel free to reach out so I can send you an invite. 
The discourse will be one of the topics for today's infrastructure meeting.

The service is available on "https://community.jenkins.io;.

The next steps are:

1) Delegating authentication to a third service, Github, keycloak, LDAP, etc...

My preferred approach would be to rely on Github SSO to authenticate with the 
tool. But we could still use our Jenkins account.  Opinions are more than 
welcome.

2) Configure the right level of Categories, as a first iteration I would like 
to focus on Jenkins users but we could extend it to Jenkins contributors as 
well.

3) Identify a group of people interested to lead this initiative.

Cheers

-- 
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/9f738ce5-44d8-48bc-ad97-574168cf0a2e%40www.fastmail.com.

Re: GSoC 2021 - Please welcome Jenkins students!

['Olblak' via Jenkins Developers]

Hi Everybody 


On Tue, May 18, 2021, at 1:27 AM, Matt Sicker wrote:
> Welcome, everyone!
> 
> On Mon, May 17, 2021 at 18:06 Oleg Nenashev  wrote:
>> Dear all,
>> 
>> The GSoC 2021 projects have been announced by Google today. The Continuous 
>> Delivery Foundation will have 6 projects this year, and five of them will be 
>> focused on Jenkins. You can find all HI the projects here 
>> .
>>  Please welcome the GSoC 2021 students!
>>  * Shruti Chaturvedi, "CloudEvents Plugin for Jenkins: Consume and Emit 
>> CloudEvents". Mentors: Vibhav Bobade, Jeff Pearce, Mauricio Salatino
>>  * Harshit Chopra, "Git credentials binding for sh, bat, and powershell", 
>> Mentors:  Mark Waite, Justin Harringa, Rishabh Budhouliya
>>  * Akihrio Kiuchi, "Jenkins Remoting Monitoring", Mentors: Oleg Nenashev, 
>> Sumit Sarin, Darshan Kansagara
>>  * Pulkit Sharma, "Security Validator for Jenkins Kubernetes Operator", 
>> Mentors: Bartek Antoniak, Sylwia Brant, Jakub Al-Khalili
>>  * Aditya Srivastava, "Semantic Versioning Plugin for Jenkins", Mentors: 
>> Gareth Evans, Kristin Whetstone, Olivier Vernin, Allan Burdajewicz
>>  * (+) In addition to 5 Jenkins projects, Daniel Ko will be working on 
>> try.spinnaker.io, Mentors: Dan Johnston, Fernando Freire, Cameron 
>> Motevasselani
>> During the next 3 weeks the GSoC teams will work on the community bonding, 
>> including but not limited to: getting introduced to each other and the key 
>> stakeholders, setting up the communication channels, forming the project 
>> plan, and doing knowledge transfers. We invite all community members to 
>> reach out to the project teams if you are interested in a project and want 
>> to contribute there and/or to be informed about the progress. Any assistance 
>> to the students will be always appreciated.
>> 
>> All the listed projects have high value to the Jenkins community, 
>> particularly for public cloud deployments and for the ongoing Jenkins 
>> software delivery pipelines rework. We are looking forward to working with 
>> the students and mentors this summer, welcome everyone!
>> 
>> Best regards,
>> Oleg Nenashev
>> CDF GSoC Org Team
>> 
>> P.S: See the GSoC sub-project mailing list to know more about the GSoC 
>> projects announcement: 
>> https://groups.google.com/g/jenkinsci-gsoc-all-public/c/EkwY7o2Jgzo . We 
>> will also have the regular office hours on Wednesday, 2PM UTC. See 
>> https://www.jenkins.io/events for the links
>> 
>> 
>> 

>> -- 
>> 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/CAPfivLALWHkiauVmRqUL2zqTLz4ufqo2%2BUm%2B6WPwA4rnFBj8Fw%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/CACmp6kqtsOAortf%3Dqfdo70rbNVqLFYWBgciPLuK__%3DtvsVcsDw%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/7404c258-6b10-46f3-aa70-26b87952c566%40www.fastmail.com.

Re: [jenkins-infra] Should we bring back wiki.jenkins.io?

['Olblak' via Jenkins Developers]

> I am -1 for recovering Wiki as it was. -0 if we are talking about creating a 
> new Wiki from scratch on Atlassian Cloud, just for Jenkins GitHub 
> organization members. No Jenkins LDAP would be needed there if we chose such 
> a way.

-1 for Atlassian Cloud. To me, it's still not an option unless we ask 
contributors to create an Atlassian account.
https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/

> I think that Google Docs are quite fine, and I am definitely responsible for 
> dozens of Google Docs we have in the community.

To me, they are throw away documentation. Ideally, I would like to easily find 
old information especially when we organize events like Fosdem or to review 
past contributor summit notes.



On Thu, May 6, 2021, at 4:45 PM, Oleg Nenashev wrote:
> I am -1 for recovering Wiki as it was. -0 if we are talking about creating a 
> new Wiki from scratch on Atlassian Cloud, just for Jenkins GitHub 
> organization members. No Jenkins LDAP would be needed there if we chose such 
> a way. 
> 
> IMHO Wiki can be largely replaced by Documentation-as-Code in repositories, 
> hackmd, and, if needed, on GitHub Wiki pages.SIGs could move the moist of the 
> contents there. Same for the Governance meeting, we could move to HackMd 
> easily. Advanced forums like Discourse could also help to store particular 
> pieces of content one would put on Wiki
> 
> I think that Google Docs are quite fine, and I am definitely responsible for 
> dozens of Google Docs we have in the community. Indeed it is nearly 
> impossible to find something due to many different accounts being used. Maybe 
> having a sponsored GSuite account or Switching to OwnCloud could be an option 
> if we want to centralize the location of the documents.
> 
> 
> 
> 
> 
> On Thu, May 6, 2021 at 3:57 PM Tim Jacomb  wrote:
>> Please no, wiki's suck for quality documentation.
>> 
>> Anyone can put whatever rubbish they want there.
>> 
>> On Thu, 6 May 2021 at 14:41, 'Olblak' via Jenkins Infrastructure 
>>  wrote:
>>> __
>>> Hi Everybody, 
>>> 
>>> During the last Infrastructure meeting 
>>> ,
>>>  Daniel Beck came with an interesting question.
>>> 
>>> Considering the proliferation of Google documents and other random tools to 
>>> take notes,
>>> shouldn't we consider bringing back Confluence?
>>> 
>>> While I am not convinced that a wiki is THE solution, I definitely share 
>>> his frustration.
>>> I feel we did a major step backward in terms of knowledge management across 
>>> the Jenkins project.
>>>  
>>> Nowadays, the default behavior is to create a Google document to take notes 
>>> during meetings or event organizations.
>>> This approach is very easy for synchronous collaboration but it also has 
>>> bad side effects. It's difficult to find old documents unless you 
>>> bookmarked them. And, documents lifecycle are affected by the "new" google 
>>> storage policy or corporate google accounts.
>>> 
>>> Historically, we used the wiki to take notes and write documentation. 
>>> https://wiki.jenkins.io/display/JENKINS
>>> That central place was really convenient to share and find information 
>>> across community initiatives.
>>> 
>>> That being said, I didn't forget the reasons to move away from Confluence, 
>>> and here are some of them:
>>> 
>>> 1. Spammers, because of the nature of the Jenkins project we tend to 
>>> attract a lot of spammers. Then *someone* has to do some clean-up.
>>> 2. Maintaining confluence is a major distraction that nobody wants to do. 
>>> 3. Confluence in the current state is very slow mainly due to point 2 and 
>>> due to unfinished infrastructure work.
>>> 
>>> The two last elements could be solved by asking the Linux Foundation to 
>>> maintain Confluence. The same way they do for Jira 
>>> 
>>> Also, it's worth keeping in mind that Atlassian is deprecating their 
>>> on-prem solution in 2024.
>>> 
>>> Several weeks ago, I started an experiment on the infrastructure project to 
>>> use hackmd.io to allow synchronous collaboration on meeting notes.
>>> During a meeting or a maintenance window, everybody can participate then at 
>>> the end of the meeting someone pushes the notes to a git repository like 
>>> https://github.com/jenkins-infra/documentation/#documentation
>>> To me it combines two approaches, it's as easy as a Google document to 
>>> collect notes and then we can easily store them on a git repository 
>>> directly in Markdown.
>>> Unfortunately, I am not convinced by the asynchronous collaboration 
>>> workflow.
>>> 
>>> There is a demo here - https://youtu.be/1s2Y3aPXTOI?t=126 (Sorry for the 
>>> poor video)
>>> 
>>> As I said it's an experiment, the purpose is to simplify synchronous 
>>> collaboration and then persist the content on a git repository that can 
>>> easily be browsed.
>>> 
>>> I would 

Should we bring back wiki.jenkins.io?

['Olblak' via Jenkins Developers]

Hi Everybody, 

During the last Infrastructure meeting 
,
 Daniel Beck came with an interesting question.

Considering the proliferation of Google documents and other random tools to 
take notes,
shouldn't we consider bringing back Confluence?

While I am not convinced that a wiki is THE solution, I definitely share his 
frustration.
I feel we did a major step backward in terms of knowledge management across the 
Jenkins project.
 
Nowadays, the default behavior is to create a Google document to take notes 
during meetings or event organizations.
This approach is very easy for synchronous collaboration but it also has bad 
side effects. It's difficult to find old documents unless you bookmarked them. 
And, documents lifecycle are affected by the "new" google storage policy or 
corporate google accounts.

Historically, we used the wiki to take notes and write documentation. 
https://wiki.jenkins.io/display/JENKINS
That central place was really convenient to share and find information across 
community initiatives.

That being said, I didn't forget the reasons to move away from Confluence, and 
here are some of them:

1. Spammers, because of the nature of the Jenkins project we tend to attract a 
lot of spammers. Then *someone* has to do some clean-up.
2. Maintaining confluence is a major distraction that nobody wants to do. 
3. Confluence in the current state is very slow mainly due to point 2 and due 
to unfinished infrastructure work.

The two last elements could be solved by asking the Linux Foundation to 
maintain Confluence. The same way they do for Jira 
Also, it's worth keeping in mind that Atlassian is deprecating their on-prem 
solution in 2024.

Several weeks ago, I started an experiment on the infrastructure project to use 
hackmd.io to allow synchronous collaboration on meeting notes.
During a meeting or a maintenance window, everybody can participate then at the 
end of the meeting someone pushes the notes to a git repository like 
https://github.com/jenkins-infra/documentation/#documentation
To me it combines two approaches, it's as easy as a Google document to collect 
notes and then we can easily store them on a git repository directly in 
Markdown.
Unfortunately, I am not convinced by the asynchronous collaboration workflow.

There is a demo here - https://youtu.be/1s2Y3aPXTOI?t=126 (Sorry for the poor 
video)

As I said it's an experiment, the purpose is to simplify synchronous 
collaboration and then persist the content on a git repository that can easily 
be browsed.

I would be curious to know your feeling about all of this and if you have other 
suggestions.

Cheers

-- 
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/7fc740e9-3cfd-4daf-bb0d-44b7a8564930%40www.fastmail.com.

Re: Jenkins SDLC Security: LFX Security/Snyk adoption status updates

['Olblak' via Jenkins Developers]

Hi Oleg,

Thanks for driving this.
Once we are allowed to have a second Github Organization, I would be very 
interested to experiment with it for the jenkins-infra organization. 

On Monday, 3 May 2021 at 22:24:44 UTC+2 Oleg Nenashev wrote:

> Thanks for the interest Daniel!
>
> >> Would you like to participate as a contributor?
> > What does this entail?
>
> That's a good question, to be seen. As a part of the pilot project we will 
> need:
>
>- Try out LFX Security 2.0 and configure it for some of our projects
>- Explore options for filtering out false positives, find a solution 
>for the Jenkins project taking its scale and needs
>- Try out other features like license analysis
>- Document the implementation for other maintainers
>- Keep evaluation notes and share feedback with Snyk/LFX Security. If 
>we experience blockers, multiple iterations might be required
>
> Note from the discussion: It is unlikely that we will be able to use the 
> standard Snyk's GitHub integration via GitHub App. We will likely need to 
> integrate scanning submissions into our Jenkins pipelines (there is a Snyk 
> plugin FTR) or to use GitHub actions. Reason - GitHub Integration cannot 
> handle custom Bills of Materials which will be supported by the LFX 
> Security 2.0 API (actually, by the Snyk backend).
>
> > Re licenses -- Is this something we're actively looking at as well, or 
> rather secondary. FWIW I can think of these use cases: That it's actually 
> open source; that it's compatible (no MIT plugin bundling GPL dependencies 
> or similar weirdness); that it's all OSI approved per governance document. 
> Anything else?
>
> Yes, looks good to me. I would rather prefer to avoid some licenses where 
> compatibility is disputed, e.g. traditional AGPL concerns.
>
>
> On Monday, May 3, 2021 at 9:35:17 PM UTC+2 Daniel Beck wrote:
>
>> Thanks again for driving this, Oleg! 
>>
>>
>> > On 3. May 2021, at 19:14, Oleg Nenashev  wrote: 
>> > 
>> > The proposal is to start the pilot from a small list of the 
>> repositories controlled by the pilot project participants: Jenkins core, 
>> its libraries, and some plugins from maintainers who are interested to 
>> participate in the pilot project. 
>> > 
>> > Call for feedback: 
>> > • Would you approve doing an official pilot project together with Snyk 
>> and LFX Security? 
>>
>> Yes, definitely. 
>>
>> > • Would you like to participate as a contributor? 
>>
>> What does this entail? 
>>
>> > • Would you like your plugin to participate in the pilot project? 
>>
>> Yes (although my plugins tend not to have interesting dependencies so 
>> it's probably not that interesting). 
>>
>>
>> Re private PRs and security process (minute 25-28 in the transcripts, 
>> again around 0:51) -- I don't really see a need to handle dependency 
>> updates in private in most cases, as all information that is based on is 
>> usually public anyway (CVEs in dependencies as well as dependency 
>> declarations). Additionally, vulnerabilities in plugins don't necessarily 
>> mean we're vulnerable (or that the metadata is correct to begin with), and 
>> how to exploit it isn't often obvious either. So I don't feel strongly 
>> about keeping such content private. What we prepare in jenkinsci-cert in 
>> private is almost exclusively fixes for exploitable vulnerabilities 
>> originating in Jenkins code. 
>>
>> Re CVE ignore list and such -- would like to see a plan (perhaps with the 
>> custom graph API that pre-filters plugin dependencies) how to deal with 
>> transitive plugin dependencies: Plugin X depends on plugin Y which bundles 
>> library Z. The maintainer of X doesn't really care about Z being outdated. 
>> (The same applies to "core Y" -- no need for a tool to tell plugin 
>> maintainers about core dependencies being outdated.) While we could dump 
>> all Jenkins CVEs into a giant ignore list, that wouldn't take care of this 
>> problem. 
>>
>> Re licenses -- Is this something we're actively looking at as well, or 
>> rather secondary. FWIW I can think of these use cases: That it's actually 
>> open source; that it's compatible (no MIT plugin bundling GPL dependencies 
>> or similar weirdness); that it's all OSI approved per governance document. 
>> Anything else? 
>>
>>

-- 
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/496a4b3a-0489-4783-b06b-1f27fd369bcan%40googlegroups.com.

Re: war file not available on get.jenkins.io

['Olblak' via Jenkins Developers]

Just for the context, we need to fix INFRA-2961 
<https://issues.jenkins.io/browse/INFRA-2961>   before adding 
archives.jenkins-ci.org to the pool of mirrors on get.jenkins.io


On Mon, May 3, 2021, at 8:42 AM, 'Olblak' via Jenkins Developers wrote:
> Hi, 
> 
> We have a mirror containing a copy of every artifacts created.
> It's https://archives.jenkins-ci.org and your file is available on 
> https://archives.jenkins-ci.org/war-stable/2.164.2/
> 
> We recently had to remove archives.jenkins.io from the get.jenkins.io 
> configuration as we have some work needed to be put it back.
> 
> Cheers
> 
> On Mon, May 3, 2021, at 7:31 AM, Oleg Nenashev wrote:
>> Hello,
>> 
>> Maybe there was a deployment issue, we were in progress of migrating to 
>> another release infrastructure at that point.
>> You can always download all plugin and WAR releases from the Jenkins 
>> Artifactory repo: 
>> https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/main/jenkins-war/2.164.2
>> 
>> Whatever happened with 2.164.2 on get.jenkins.io, I doubt it makes sense to 
>> restore it now. It is not even the latest LTS in the baseline
>> 
>> Best regards,
>> Oleg
>> 
>> On Monday, May 3, 2021 at 6:53:15 AM UTC+2 chetan@gmail.com wrote:
>>> Dear team,
>>> I am looking for a very specific version of jenkins - v2.164.2
>>> The website https://get.jenkins.io/war-stable/ does not have the artifact. 
>>> 
>>> It tells: *_The requested URL /pub/jenkins/war-stable/2.164.2/jenkins.war 
>>> was not found on this server._*
>>> *__*
>>> Can you please help me in getting the war file? I kind of need it urgently 
>>> :( 
>>> 
>>> Thanks in advance.
>>> 
>> 

>> -- 
>> 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/1af02a74-83d5-422d-a7d5-8e551a729954n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/1af02a74-83d5-422d-a7d5-8e551a729954n%40googlegroups.com?utm_medium=email_source=footer>.
> 
> 

> -- 
> 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/a18a3a31-dc5c-4747-9f90-3a517016cd3d%40www.fastmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/a18a3a31-dc5c-4747-9f90-3a517016cd3d%40www.fastmail.com?utm_medium=email_source=footer>.

-- 
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/938ed4d3-43c8-4375-b3f2-391b47c16827%40www.fastmail.com.

Re: war file not available on get.jenkins.io

['Olblak' via Jenkins Developers]

Hi, 

We have a mirror containing a copy of every artifacts created.
It's https://archives.jenkins-ci.org and your file is available on 
https://archives.jenkins-ci.org/war-stable/2.164.2/

We recently had to remove archives.jenkins.io from the get.jenkins.io 
configuration as we have some work needed to be put it back.

Cheers

On Mon, May 3, 2021, at 7:31 AM, Oleg Nenashev wrote:
> Hello,
> 
> Maybe there was a deployment issue, we were in progress of migrating to 
> another release infrastructure at that point.
> You can always download all plugin and WAR releases from the Jenkins 
> Artifactory repo: 
> https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/main/jenkins-war/2.164.2
> 
> Whatever happened with 2.164.2 on get.jenkins.io, I doubt it makes sense to 
> restore it now. It is not even the latest LTS in the baseline
> 
> Best regards,
> Oleg
> 
> On Monday, May 3, 2021 at 6:53:15 AM UTC+2 chetan@gmail.com wrote:
>> Dear team,
>> I am looking for a very specific version of jenkins - v2.164.2
>> The website https://get.jenkins.io/war-stable/ does not have the artifact. 
>> 
>> It tells: *_The requested URL /pub/jenkins/war-stable/2.164.2/jenkins.war 
>> was not found on this server._*
>> *__*
>> Can you please help me in getting the war file? I kind of need it urgently 
>> :( 
>> 
>> Thanks in advance.
>> 
> 

> -- 
> 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/1af02a74-83d5-422d-a7d5-8e551a729954n%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/a18a3a31-dc5c-4747-9f90-3a517016cd3d%40www.fastmail.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

['Olblak' via Jenkins Developers]

Hi,

I am definitely in favor of switching to jdk11 by default, it's really time to 
move forward. We have been using it on the Jenkins infrastructure project for 
almost a year now without major issues but we also had to fine-tune the java 
configuration for java 11.

That remains a major change with potential breaking changes, so I would 
announce it enough in advance so people can already switch to jdk11, and keep 
the java8 for several stable releases with a deprecation warning.



On Wed, Apr 28, 2021, at 6:20 PM, Tim Jacomb wrote:
> Defaults and (people not seeing a need to change)
> 
> Shipping an ‘admin monitor’ encouraging people to update would probably make 
> a difference 
> 
> On Wed, 28 Apr 2021 at 17:18, Tim Jacomb  wrote:
>> It’s just down to defaults I think.
>> 
>> We’ve seen the numbers rise as we changed the website and helm chart to use 
>> Java 11 by default
>> 
>> On Wed, 28 Apr 2021 at 17:08, Daniel Beck  wrote:
>>> 
>>> 
>>> On Wed, Apr 28, 2021 at 1:42 AM Oleg Nenashev  
>>> wrote:
 I am in favor of making JDK11 the default in all our distributions, 
 including controller and agent Docker images.
 At the same time I am afraid that removal of Java 1.8 support is 
 premature. The vast majority of Jenkins users still uses this version, and 
 the migration to Java 11 won't be seamless in al l cases. For example, 
 Maven Plugin will effectively switch project builds to Java 11 once the 
 agent images are updated. It will cause unexpected issues in user builds 
 here and there. Nothing should be critical, but we should not force users 
 to migrate immediately.
 
 IMHO there should be a grace period between Java 8 support deprecation and 
 the actual removal. Maybe 6 months or so.
>>> 
>>> Agree; I'd even be more conservative than just six months. We can and 
>>> should update the default Docker images to run on JDK 11. But we shouldn't 
>>> ignore that just ~0.3% of instances use Java 11, let's do something about 
>>> that first. I wouldn't be surprised that there are still some problems to 
>>> work out but we just have no users yet who would be affected.
>>> 
>>> 

>>> -- 
>>> 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/CAMo7PtLW05CwT6JyDHHpq52V%2BZwcRy3hQxPW7O9U-D%3DR1adL7Q%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/CAH-3BicOSJ%2B%3DMhXxO2HRz4QL7O8tm5P56MJhJPsU13z3tTe0og%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/9e55183f-9d5f-4d46-8a0c-0fddf21ebfc0%40www.fastmail.com.

[INFRA-2944] 2021-04-14 | AKS upgrade tomorrow

['Olblak' via Jenkins Developers]

Hi Everybody,

Tomorrow, we'll do an AKS cluster upgrade from 1.17 to 1.18.

The procedure upgrades one machine at a time so most services should remain up 
and running.
The services "release.ci", "infra.ci" and the ldap service will be restarted in 
the process as the containers get rescheduled to other nodes.

We didn't identify major risk for this upgrade

We are continuously improving the process so, feel free to provides feedbacks 
on the notes  and we will 
incorporate them in the next upgrades.

Cheers

-- 
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/832a10fa-6827-4b2a-9fa2-70618cb43d43%40www.fastmail.com.

2021-04-07 - Feedback - Jenkins Release issues

['Olblak' via Jenkins Developers]

Hi Everybody,

Quick feedback on the recent security release.

While we successfully managed to publish everything in time, I must admit that 
it was more painful than I expected.

So what happened?

Yesterday, as part of the release procedure we trigger the maven release job 
but we quickly got hit by timeout errors between the Jenkins agent and the 
controller. As we faced the same issue on infra.ci last week, we had an idea on 
how to mitigate that issue and  with the help of Gareth and Damien we quickly 
apply the same mitigation that we applied to infra.ci which was switching from 
using a Jenkins tunnel  to a WebSocket connection as defined in this PR 
 so we could finish 
the first release part


Today we met again with Daniel Beck to finalize the release, so we build and 
publish packages but this time we got hit by two additional issues.
First, we had WebSockets connection timeout error that we solved by increasing 
that value from 30sec to 60sec as defined in this PR 


The second issue that hit us was that we couldn't upload windows artifacts from 
the Jenkins agent to pkg.jenkins.io using the ssh-agent. The problem seems to 
be related to the latest ssh-agent plugin version which deleted non-exec based 
agent factories according to the changelog 
 :p.

Thanks to Gareth recent work on building a custom Jenkins image with our 
plugins   as I could quickly pin down the previous version in this PR 
 

So we first focus on publishing packages for non-Windows distributions, then I 
published the windows ones.

In this process, I also identified additional issues.
1) Our monitoring didn't detect that the latest Jenkins version wasn't 
available from get,jenkins.io, which seems to be regression.
2) I had to manually trigger mirrrobits mirror scan to enable them, I don't 
know yet why it didn't automatically scan mirrors.

So what's next? 
Next week we'll update the AKS cluster used by the release environment hoping 
that it will solve all the network issues we currently have.
Regarding the ssh-agent issue with the windows containers, I am looking for 
someone with better windows skills than mine :) to spare me some debugging 
time. 


Cheers,

Olivier

-- 
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/1782f6e3-09bf-4dce-85fc-c15cd7372de0%40www.fastmail.com.

Re: Plugin Hosting Requests

['Olblak' via Jenkins Developers]

Hi,

Thank you Alex for your email, I am really glad when we have the time to 
correctly prepare that kind of transition.
I mean It's totally normal that contribution time evolves.  :) 
This sounds like the perfect time for someone to step up, and I would be very 
happy to help with that transition.


On Fri, Apr 2, 2021, at 4:33 PM, Oleg Nenashev wrote:
> Thanks a lot for all your contributions Alex!
> 
> Last year we have started the Hosting Team 
>  in Jenkins, but unfortunately 
> it did not fly. At least we have several contributors with permissions and 
> up-to-date guidelines for the hosting process. There was also a significant 
> improvement in the hosting process automation, thanks to Alex and Tim.
> 
> I used to maintain the hosting process several years ago, and I will be able 
> to help with processing hosting requests. My time is also limited, and it 
> would be great to have more contributors involved. I will be happy to provide 
> mentorship to those who are interested.
> 
> Best regards,
> Oleg Nenashev
> 
> 
> 
> On Friday, April 2, 2021 at 3:55:05 PM UTC+2 adityasriva...@gmail.com wrote:
>> 
>> On Fri, Apr 2, 2021 at 4:58 PM Mark Waite  wrote:
>>> That's great Aditya.  We're glad to have additional help.  I'm not the 
>>> hosting expert, but wanted to thank you for joining the infrastructure 
>>> meeting last week.  We look forward to involving in the Jenkins project in 
>>> more ways.  Thanks again!
>> 
>> Hello Mark, 
>> The pleasure was all mine. I was truly amazed by looking at the numbers of 
>> daily downloads and TBs level data that moves around. Also had a chat later 
>> with Gareth about the same on an ad-hoc call. Learning a lot :)
>> 
>> Thanks and regards,
>> Aditya Srivastava
>> 
>>  
>>> 
>>> On Friday, April 2, 2021 at 5:18:02 AM UTC-6 adityasriva...@gmail.com wrote:
 
 Hey Alex,
 I am a newbie here, so I am not sure if I am eligible, but I sure am 
 interested in helping out. 
 I'd love to learn more about the screening part and I've done code reviews 
 before for my _small_ open-source org, so I guess that experience would 
 come in handy. 
 I am excited to learn more about this and get involved. 
 
 Thanks and Regards,
 Aditya Srivastava
 
 
 
 On Fri, Apr 2, 2021 at 10:22 AM 'Gavin Mogan' via Jenkins Developers 
  wrote:
> I'm not sure its a good idea for me to take on more tasks, but I can help 
> out more if needed. That being said, the dev list is full of people 
> contributing, it might be worth asking on the users mailing list to see 
> if there's anyone new interested in helping out, at least the first round 
> of screening new hosting requests.
> 
> On Thu, Apr 1, 2021 at 8:06 PM Slide  wrote:
>> Hi Everyone,
>> 
>> As I brought up last year, I am having less time to work on Jenkins 
>> because of work responsibilities. It's time for me to reduce my time on 
>> Jenkins again sadly. I have been handling many of the plugin hosting 
>> requests that come in, running the checker and doing code reviews on the 
>> plugins prior to them being accepted into the jenkinsci org on GitHub. I 
>> will no longer have time to do that in the near future and would like to 
>> help migrate that work to someone else who is interested in helping out 
>> the project. Is anyone interested in learning about this and becoming 
>> involved?
>> 
>> Regards,
>> 
>> Alex
>> 
>> 
>> 
>> -- 
>> Website: http://earl-of-code.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 discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfAFnGYSLe3gUC-qGzPYwEHBfKYTRnd%3DUUYH%2BtpGF8pMQ%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 discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuueuU1%3DUM4wTiEnQFWf2C9BuTRsipGT67qhP%3DyocSe_Cw%40mail.gmail.com
>  
> .
>>> 

>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Developers" group.
>>> To unsubscribe 

Re: [Github] jenkins-infra alumni team

['Olblak' via Jenkins Developers]

Hi Everybody, 
I made few changes to the Jenkins-infra GitHub organization.

**jenkins-infra/alumni**
I created the alumni team here 
<https://github.com/orgs/jenkins-infra/teams/alumni/members>, feel free to 
reach out if I put the wrong person there and I'll revert it or if I am missing 
someone.

**Repository permission**
Several teams had "admin" permission and I switched that to "maintain"

I started reviewing team repository permission and while I made few changes, I 
still have pending work but feel free to suggest teams that should or should 
not have a specific repository access

Cheers


On Mon, Mar 29, 2021, at 3:12 PM, 'Olblak' via Jenkins Developers wrote:
> Thanks everybody for your feedback, I'll create that team and start moving 
> people there
> 
> On Mon, Mar 29, 2021, at 2:15 PM, Oleg Nenashev wrote:
>> I went ahead and created a team in the jenkinsci org 
>> https://github.com/orgs/jenkinsci/teams/alumni 
>> I will move some of the known inactive contributors there.
>> On Sunday, March 28, 2021 at 3:13:43 PM UTC+2 siiy...@gmail.com wrote:
>>> +1 from me
>>> 
>>> 
>>> On Fri, Mar 26, 2021 at 9:11 AM Rick  wrote:
>>>> 
>>>> +1 from me
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 03/26/2021 00:16，Mark Waite wrote：
>>>>> +1 from me.
>>>>> 
>>>>> On Thursday, March 25, 2021 at 3:55:16 AM UTC-6 Olblak wrote:
>>>>>> __
>>>>>> Hi Everybody,
>>>>>> 
>>>>>> I am currently collecting feedback about the best way to manage user 
>>>>>> access to the Jenkins-infra GitHub organization and more specifically 
>>>>>> for people who don't contribute anymore (whatever the reason).
>>>>>> 
>>>>>> I recently review user permissions on the Github Jenkins infrastructure 
>>>>>> organization and we have 53 people with different kinds of permission. A 
>>>>>> lot of them stepped back or just don't actively contribute anymore.
>>>>>> This brings unneeded risk to the Github organization as they have change 
>>>>>> permissions even though a lot of them don't need those permissions 
>>>>>> anymore. Differently said, It doesn't make sense to take the risk that a 
>>>>>> compromised account introduces changes in our git repositories if that 
>>>>>> account doesn't need privileged access anymore.
>>>>>> 
>>>>>> So I am proposing to create a new "team" named alumni which would have 
>>>>>> read-only permissions on every public repository.
>>>>>> This would bring the following benefits
>>>>>> 
>>>>>>  1. We would still be able to assign individual alumni group member PR 
>>>>>> or Issues as knowledge experts.
>>>>>>  2. Alumni team members will have the "jenkins-infra" badge on their 
>>>>>> GitHub user profile as a way to highlight their past contribution.
>>>>>>  3. If for some reason a malicious user get access to one of the alumni 
>>>>>> account, that attacker won't be able to merge PR which reduces the risk 
>>>>>> on the GitHub organization.
>>>>>>  4. Of course, once a contributor get more active, we can still remove 
>>>>>> him from alumni group and grant him more permission
>>>>>> Any thoughts? 
>>>>>> Without any feedback, I'll wait one week, starting from this email, 
>>>>>> before implementing my plan.
>>>>>> 
>>>>>> Cheers,
>>>>>> 
>>>>>> Olivier
>>>>>> 
>>>>>> --
>>>>>>   Olblak
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 

>>>>> -- 
>>>>> 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/7719a88f-ee56-465a-a44e-67867c473cb2n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/7719a88f-ee56-465a-a44e-67867c473cb2n%40googlegroups.com?utm_medium=email

Re: [Github] jenkins-infra alumni team

['Olblak' via Jenkins Developers]

Thanks everybody for your feedback, I'll create that team and start moving 
people there

On Mon, Mar 29, 2021, at 2:15 PM, Oleg Nenashev wrote:
> I went ahead and created a team in the jenkinsci org 
> https://github.com/orgs/jenkinsci/teams/alumni 
> I will move some of the known inactive contributors there.
> On Sunday, March 28, 2021 at 3:13:43 PM UTC+2 siiy...@gmail.com wrote:
>> +1 from me
>> 
>> 
>> On Fri, Mar 26, 2021 at 9:11 AM Rick  wrote:
>>> 
>>> +1 from me
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 03/26/2021 00:16，Mark Waite wrote：
 +1 from me.
 
 On Thursday, March 25, 2021 at 3:55:16 AM UTC-6 Olblak wrote:
> __
> Hi Everybody,
> 
> I am currently collecting feedback about the best way to manage user 
> access to the Jenkins-infra GitHub organization and more specifically for 
> people who don't contribute anymore (whatever the reason).
> 
> I recently review user permissions on the Github Jenkins infrastructure 
> organization and we have 53 people with different kinds of permission. A 
> lot of them stepped back or just don't actively contribute anymore.
> This brings unneeded risk to the Github organization as they have change 
> permissions even though a lot of them don't need those permissions 
> anymore. Differently said, It doesn't make sense to take the risk that a 
> compromised account introduces changes in our git repositories if that 
> account doesn't need privileged access anymore.
> 
> So I am proposing to create a new "team" named alumni which would have 
> read-only permissions on every public repository.
> This would bring the following benefits
> 
>  1. We would still be able to assign individual alumni group member PR or 
> Issues as knowledge experts.
>  2. Alumni team members will have the "jenkins-infra" badge on their 
> GitHub user profile as a way to highlight their past contribution.
>  3. If for some reason a malicious user get access to one of the alumni 
> account, that attacker won't be able to merge PR which reduces the risk 
> on the GitHub organization.
>  4. Of course, once a contributor get more active, we can still remove 
> him from alumni group and grant him more permission
> Any thoughts? 
> Without any feedback, I'll wait one week, starting from this email, 
> before implementing my plan.
> 
> Cheers,
> 
> Olivier
> 
> --
>   Olblak
> 
> 
> 
 

 -- 
 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/7719a88f-ee56-465a-a44e-67867c473cb2n%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-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/7faf2c04.2688.1786c140815.Coremail.zxjlwt%40126.com
>>>  
>>> .
>> 
>> 
>> -- 
>> Shi Yanjun(yJunS)
>> Blog:https://github.com/yJunS
> 

> -- 
> 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/50aa7676-2e97-48a4-9f6c-cbb968e077d6n%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/a7fa95f1-217e-464c-bd27-c4e93860f428%40www.fastmail.com.

Re: Proposal: newsletter mailing list for contributor announcements

['Olblak' via Jenkins Developers]

Hi Everybody, 

I am definitely in favor of a new low traffic channel to distribute major 
news, I share Richard's opinion, I also find it difficult to keep up in the 
dev mailing list.
Personally, I would suggest using something more generic like 
"jenkins-announcement" and maybe using tags in the subject but we should 
keep it read-only and very low traffic

While I am not a big fan of the Google group, it remains the easiest 
solution :/.
I wouldn't be in favor of using the Sendgrid mailing list, mainly for 
access management. 

On Monday, 22 March 2021 at 10:33:47 UTC+1 Oleg Nenashev wrote:

> > I know it's stretching the scope of what you are talking about, but it 
> would be also good to have some kind of "Action Required" type comms 
> outside of the Dev mailing list for important changes that plugin 
> maintainers need to know about to stop plugins breaking. 
>
> Yes, this is a good thing to do, especially in the case of the 2.277.x 
> release when many users were affected.
> +1 for that, especially if we aggregate all key upcoming changes in a 
> single digest.
>
>
>
>
> On Monday, March 22, 2021 at 4:12:06 AM UTC+1 Mark Waite wrote:
>
>> Sounds like a good idea to me.
>>
>> On Sun, Mar 21, 2021 at 5:29 PM Oleg Nenashev  
>> wrote:
>>
>>> Hi all,
>>>
>>> As a follow-up to the discussions in the Advocacy SIG, I would 
>>> like to propose creating a new low-traffic mailing list for distributing 
>>> news and contributor announcements.
>>>
>>> The main reason for this mailing list is creating a channel of 
>>> contacting contributors and plugin maintainers who do not regularly read 
>>> the developer mailing list and whom we would like to contact in the case of 
>>> major community events (hackathons, contributor summits, elections, etc.). 
>>> Right now we have only a few options like using LDAP accounts and SendGrid, 
>>> which is not very convenient for community organizers and does not offer 
>>> contributors a way to opt-out.
>>>
>>> I propose to use a new Google Group, e.g. 
>>> "jenkins-contributor-announcements". Then we can update the website to 
>>> reference it, and announce it through other channels. Not sure how 
>>> effective it will be, but I think it worth trying. What do you think?
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>>
>>>
>>>
>>>
>>> -- 
>>> 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/CAPfivLCdrdvvZH1a6UC-We%2BmkGRs0WfNXq-BC-XihR-p%3DsQyyQ%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/b38334d4-0a51-4227-b2a7-33302992207en%40googlegroups.com.

Re: Microsoft is going to retire Azure plugins?

['Olblak' via Jenkins Developers]

hold on, 2024 is pretty far for the Jenkins infra project and as Timja says, it 
just means that Microsoft won't support them anymore

On Thu, Feb 11, 2021, at 2:22 PM, Tim Jacomb wrote:
> I think it just means that Microsoft are going to stop 'officially' 
> supporting them
> 
> I assume someone else could adopt them
> 
> 
> 
> On Thu, 11 Feb 2021 at 12:59, Mark Waite  wrote:
>> New topic for the Jenkins infra team, planning the migration of 
>> ci.jenkins.io from Azure cloud to another cloud provider.  The ci.jenkins.io 
>> instance relies on:
>>  * Azure Container Agents plugin
>>  * Azure VM Agents plugin
>>  * Azure Storage plugin
>> I've added the topic to the Jenkins infra meeting agenda.
>> 
>> On Thu, Feb 11, 2021 at 3:53 AM hr@gmail.com  wrote:
>>> Looks like Microsoft wants to retire, whatever that means, most of the 
>>> Jenkins plugins for Azure on  February 29, 2024.
>>> 
>>> https://docs.microsoft.com/en-us/azure/developer/jenkins/plug-ins-for-azure
>>> 
>>> Is this just another way of putting plugins up for adoption?
>>> 

>>> -- 
>>> 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/440bea32-2091-43d7-8dc7-47cd50b8f628n%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/CAO49JtFYUX%2BFVwUZ6OdRUvWxafLfHthHatJ46uF4XWwiqJ1G1Q%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/CAH-3Bicng4ECuJAjBdf%2BTOc_dzsCaqcg5u%3Dv1AXBCd3pBJ-iiw%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/5e91233e-36ef-442d-ac82-b01f2858db98%40www.fastmail.com.

Re: 2021 priorities for Jenkins - Security

['Olblak' via Jenkins Developers]

Thanks, Oleg for putting down this, I would definitely be interested to chat 
during the contributor summit about this topic.

On Thu, Jan 21, 2021, at 1:48 PM, Oleg Nenashev wrote:
> Just a quick follow-up to this thread, there is ongoing discussion about 
> hosting a contributor summit after FOSDEM.
> Should it happen, I suggest having a security track/section there. We had a 
> similar one last year in Brussels, and IIRC it went quite well.
> 
> Ideas/comments and topic suggestions are welcome :)
> 
> 
> On Tuesday, January 19, 2021 at 9:02:51 AM UTC+1 Oleg Nenashev wrote:
>> Hi all,
>> 
>> To follow-up on the Jenkins Governance meeting 
>> 
>>  we had last week, I'd like to continue the discussion about Jenkins 
>> security which was suggested as one of 2021 priorities. In this thread I 
>> propose to discuss ideas w.r.t improving security of Jenkins components and 
>> software supply chains. NOTE: Please do not reference unfixed security 
>> issues in this thread (reporting vulnerabilities 
>> ). 
>> 
>> *Current state*. Jenkins Security Team is doing a great job w.r.t. 
>> addressing security issues. In 2020 we had 19 security advisories with 198 
>> fixed vulnerabilities and 72 disclosed ones. There were great additions to 
>> devtools: Dependabot, GitHub CodeQL, Find-Sec-Bugs, etc. Also, new plugin 
>> hosting requests now get on-demand security reviews before being published. 
>> All of that is a great progress compared to the state we had several years 
>> ago.
>> 
>> *What’s next?* With all the recent events, security of the software delivery 
>> chain is in the spotlight for the many organizations. Jenkins is a key part 
>> of this chain for many users, and for sure we want to keep it that way. It 
>> is not “just” about timely fixing security issues and preventing 
>> misconfiguration. We are also interested to keep our own delivery processes 
>> in the best possible shape.
>> 
>> Some ideas we discussed at the meeting:
>>  * Growing security awareness among contributors so that the new code and 
>> documentation get developed with security in mind.
>>  * Expanding developer tooling. It would help to automate, and, when 
>> relevant, enforce preferred security practices in Jenkins components.
>>* Examples: release automation infrastructure, adopting more analysis 
>> tools in the default pipelines. With a great start in previous years, we 
>> could definitely do more by using available tools and sponsorships.
>>  * Getting more contributors involved in the security effort. It is not only 
>> about delivering the security fixes. Many topics could be discussed publicly 
>> in SIGs and sub-projects, e.g. hardening Docker images, demonstrating 
>> security tools with Jenkins, and so on. Contributors could also help with 
>> security reviews
>>  * // Add your ideas in replies!
>> What do you think about these items? Would you like to suggest more 
>> additional areas where we could improve? Any feedback would be appreciated.
>> 
>> Best regards,
>> Oleg Nenashev
> 

> -- 
> 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/ea30b90e-c2ee-433f-868d-384793350481n%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/735b71c9-6321-41a0-b3cc-7c13177ac66e%40www.fastmail.com.

Re: Jenkinc-ci account recovery

['Olblak' via Jenkins Developers]

Hi, 

I just reverted your email address to the gmail.com one.
If you try to reset your password from https://beta.accounts.jenkins.io
An email should be sent to your Gmail email address.

Regarding your neuvector.com email, I had a look at our Sendgrid account, and 
it appears that the emails send to maintai...@neuvector.com were dropped 
because that email was on a bounced list, I just remove it from the list.

Cheers


On Mon, Dec 14, 2020, at 7:37 AM, long song wrote:
> hi,
> 
> I am the maintainer of the Jenkins Plugin: 
> https://github.com/jenkinsci/neuvector-vulnerability-scanner-plugin
> 
> 
> I need to release a new version of Jenkins plugin, but I can't login 
> https://beta.accounts.jenkins.io with the userid "neuvector"
> 
> Can someone help to change the recovery email to songlon...@gmail.com for 
> "neuvector" userid ?
> 
> My github account is https://github.com/songlongcn
> 
> Thanks!
> 
> Best regards,
> Long
> 
> 
> On Fri, Dec 11, 2020 at 11:26 AM long song  wrote:
>> hi Gavin,
>> 
>> I think there may be some restrictions on the recovery email address.
>> 
>> Would you help to change the recovery email back to songlon...@gmail.com ?
>> 
>> Thanks,
>> Long
>> 
>> On Fri, Dec 11, 2020 at 9:38 AM long song  wrote:
>>> hi Gavin,
>>> 
>>> I tried https://beta.accounts.jenkins.io , but don't receive the password 
>>> recovery email.
>>> 
>>> Thanks,
>>> Long
>>> 
>>> On Fri, Dec 11, 2020 at 8:52 AM 'Gavin Mogan' via Jenkins Developers 
>>>  wrote:
>>>> Can you try again with https://beta.accounts.jenkins.io
>>>> 
>>>> On Fri., Dec. 11, 2020, 1:27 a.m. long song,  wrote:
>>>>> Hi there,
>>>>> 
>>>>> My login account is neuvector. The login password isn't working when I 
>>>>> change the recovery email address from songlon...@gmail.com to 
>>>>> maintai...@neuvector.com. 
>>>>> 
>>>>> 
>>>>> My new recovery email address doesn't receive any reset password email 
>>>>> from jenkins when I tried to reset it at 
>>>>> https://accounts.jenkins.io/passwordReset.
>>>>> 
>>>>> How can I recover it ?
>>>>> 
>>>>> Thanks in advance!
>>>>> 
>>>>> Cheers,
>>>>> Long
>>>>> 
>>>>> On Thu, Oct 1, 2020 at 12:52 PM long song  wrote:
>>>>>> The account is recovered and the password gets reset.
>>>>>> 
>>>>>> Thanks very much!
>>>>>> 
>>>>>> 
>>>>>> On Wed, Sep 30, 2020, 11:32 PM 'Olblak' via Jenkins Developers 
>>>>>>  wrote:
>>>>>>> __
>>>>>>> Hi Long,
>>>>>>> 
>>>>>>> Your request seems legit to me so I updated your email address, can I 
>>>>>>> ask you to reset your password on https://beta.accounts.jenkins.io
>>>>>>> 
>>>>>>> Cheers
>>>>>>> 
>>>>>>> On Thu, Oct 1, 2020, at 4:32 AM, long song wrote:
>>>>>>>> hi Mark,
>>>>>>>> 
>>>>>>>> X Sun left last year and does not contribute to 
>>>>>>>> https://github.com/jenkinsci/neuvector-vulnerability-scanner-plugin 
>>>>>>>> anymore.
>>>>>>>> 
>>>>>>>> I contacted him but he can't remember the email address and the 
>>>>>>>> credentials.
>>>>>>>> 
>>>>>>>> I am currently the maintainer of 
>>>>>>>> neuvector-vulnerability-scanner-plugin. 
>>>>>>>> 
>>>>>>>> My identity can be verified at Github 
>>>>>>>> https://github.com/jenkinsci/neuvector-vulnerability-scanner-plugin in 
>>>>>>>> the contributor list.
>>>>>>>> 
>>>>>>>> Would you help to reset the email address ?
>>>>>>>> 
>>>>>>>> Thanks!
>>>>>>>> Long
>>>>>>>> 
>>>>>>>> On Wed, Sep 30, 2020 at 5:51 PM Mark Waite  
>>>>>>>> wrote:
>>>>>>>>> That account is associated with a hotmail account for X Sun.  I don't 
>>>>>>>>> think that I'm allowed to reset the pa

Re: Jenkins 3.x

['Olblak' via Jenkins Developers]

> Aren’t we are a little bit late for it, since these changes are already part 
> of 2.x? Additionally, wouldn’t it be helpful if we have some groundbreaking 
> user visible changes in 3.x as well (as we had in 2.x)? 
I would say it's still fine as long as those changes aren't in the LTS

> 
> Anyway, I would like, when the time comes, to introduce semantic versioning 
> , adding a third number to 
> the version and using them according to this way of versioning. In the future 
> we can extend it to plugins and add some features in core to support / check 
> / leverage this.
Isn't it already the case for Lts releases? 
Do we often have weekly releases that only contain bugfixes?


On Thu, Nov 26, 2020, at 12:53 PM, Manuel Ramón León Jiménez wrote:
> Hi.
> 
> I don't have a strong opinion although I tend to think more like Ulrich. 
> Maybe the UI revamp would be a good inflection point, in addition to these 
> breaking changes..
> 
> Anyway, I would like, when the time comes, to introduce semantic versioning 
> , adding a third number to 
> the version and using them according to this way of versioning. In the future 
> we can extend it to plugins and add some features in core to support / check 
> / leverage this.
> 
> Thanks!
> 
> On Thu, Nov 26, 2020 at 12:56 PM Ullrich Hafner  
> wrote:
>> Aren’t we are a little bit late for it, since these changes are already part 
>> of 2.x? Additionally, wouldn’t it be helpful if we have some groundbreaking 
>> user visible changes in 3.x as well (as we had in 2.x)? 
>> 
>>> Am 26.11.2020 um 09:47 schrieb Arnaud Héritier :
>>> 
>>> I think it's a good idea.
>>> In the same spirit than 1.x -> 2.x (We justify the bump by the risk to 
>>> impact a large number of plugins)
>>> 
>>> 
>>> 
>>> On Thu, Nov 26, 2020 at 9:29 AM Ivan Fernandez Calvo 
>>>  wrote:
 +1000 to considered those changes as a major change
 
 El miércoles, 25 de noviembre de 2020 a las 17:37:21 UTC+1, James Nord 
 escribió:
> Hi all,
> 
> with the recent weeklies we have a couple of changes (Acegi 
> upgrade/table-to-div) that break compatibility in plugins.
> 
> Whilst many open source plugins have been updated and made compatible 
> with the old and new version by the people making the changes (and 
> compatability layers have been added as far as possible), there can be 
> closed source ones that we have no sight of that can be broken.
> 
> Given this is an API compatibility breakage, I am wondering why don't we 
> bump the version number to Jenkins 3.x  to signify the breaking API?
> 
> Regards
> 
> /James
 
 -- 
 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/3929b9b0-d36b-4eb7-bc46-81fc01e7c21en%40googlegroups.com
  
 .
>>> 
>>> 
>>> -- 
>>> Arnaud Héritier
>>> Twitter/Skype : aheritier
>>> 
>>> -- 
>>> 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/CAFNCU-8n8qzP0NZrAazGkg-U7Anf2Mrz1ZCgbUoqiJjz4LeWCA%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/7E4AA979-7FBB-4712-BCE6-B24C28840F50%40gmail.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/CADN1OJ25c1K%2BrRbX9zf3oKBdrbsU3sSBYOiGLVA4pgW18QKrNw%40mail.gmail.com
>  
> 

Re: Jenkins Governance Meeting, Nov 18, 2020

['Olblak' via Jenkins Developers]

Hi  Oleg,

I am sorry to hear about that, that time is definitely really bad for me as 
well.  

On Wed, Nov 18, 2020, at 7:15 PM, Oleg Nenashev wrote:
> The meeting did not happen, because it was only me on the call. I kindly ask 
> board members and officers to reject the meeting invitations in their 
> calendars if they do not plan to attend. The timing for these meeting is 
> quite bad for me, and it puts pressure on my family obligations. If I know 
> that nobody plans to join in advance, I won't be staying in the office for a 
> few extra hours, and spend them with my family instead. Thanks for 
> understanding.
> 
> On Wednesday, November 18, 2020 at 6:10:33 PM UTC+1 Oleg Nenashev wrote:
>> Hi all,
>> 
>> In 1 hour we will have a regular Jenkins Governance Meeting (starts at 6PM 
>> UTC). Everyone is welcome to join us and to participate in the discussion. 
>> Meeting link: 
>> https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 
>> 
>> Draft agenda:
>>  * News!
>>  * Jenkins elections status update
>>  * LTS schedule update
>>  * Google Summer of Code 2021
>>  * Jenkins K8s Operator updates
>> If you would like to add more topics, please suggest changes here 
>> .
>> 
>> Best regards,
>> Oleg Nenashev
>> 
> 

> -- 
> 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/18072109-74c2-4cd6-9faf-15c04700826bn%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/d6468cf2-40c4-47b5-94a1-24f1e1e42b74%40www.fastmail.com.

Re: Request using the certificate file of the official Jenkins Update Center

['Olblak' via Jenkins Developers]

I am wondering what it would take to directly use get.jenkins.io instead of 
update-center.
update-center.json is available from the mirror as well  as you can see here 
-> https://get.jenkins.io/updates/current/update-center.json?mirrorlist

The challenge is because the json is potentially generated every 3 minutes, 
it's hard for mirrors to stay up to date but we still control some of them. If 
no mirrors have the file with the correct checksum, then it fallback to a 
hardcode mirror that we configured.

We could also ask mirrors maintainers to sync "/updates" every three minutes, 
it doesn't represent a lot of files.
Also, we must ensure that mirrorbits scan files from /updates every few minutes 
to generate file hashes.



On Tue, Nov 17, 2020, at 7:03 PM, Daniel Beck wrote:
> 
> 
> > On 17. Nov 2020, at 15:01, Rick  wrote:
> > 
> > 
> > You mean generate two or more versions of update-cener.json files? For 
> > example, update-center.json and update-center-zh.json ? Am I right?
> 
> Basically this, yes.
> 
> Re mirrors, did you test using the regular update site recently, and 
> still encounter performance issues? I think we used a pretty badly 
> outdated Geo IP DB until a few months ago, so if you haven't checked in 
> a while, it makes sense to retry using the regular URLs to see how well 
> this works now.
> 
> -- 
> 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/C975C702-599F-4504-B833-942BE2A3B177%40beckweb.net.
>

-- 
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/ca31583c-7c7a-4ec3-a9f0-8752a5ccfd03%40www.fastmail.com.

Re: Request using the certificate file of the official Jenkins Update Center

['Olblak' via Jenkins Developers]

> Because all plugins URL point to 
> https://updates.jenkins.io/download/plugins/xxx instead of the mirror.  

And then you are redirected to mirrors

curl -I -L 
https://get.jenkins.io/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi
HTTP/1.1 302 Found
Date: Tue, 17 Nov 2020 14:50:34 GMT
Server: Mirrorbits/v0.5.1
Cache-Control: private, no-cache
Content-Type: text/html; charset=utf-8
Link: 
;
 rel=duplicate; pri=1; geo=nl
Link: 
;
 rel=duplicate; pri=2; geo=us
Link: 
;
 rel=duplicate; pri=3; geo=us
Link: 
;
 rel=duplicate; pri=4; geo=us
Link: 
;
 rel=duplicate; pri=5; geo=us
Link: 
;
 rel=duplicate; pri=6; geo=cn
Link: 
;
 rel=duplicate; pri=7; geo=jp
Location: 
https://ftp.halifax.rwth-aachen.de/jenkins/plugins/plugin-util-api/1.4.0/plugin-util-api.hpi
Via: 1.1 get.jenkins.io

HTTP/2 200
server: nginx/1.14.2
date: Tue, 17 Nov 2020 14:50:35 GMT
content-type: application/octet-stream
content-length: 613574
last-modified: Fri, 16 Oct 2020 07:26:25 GMT
accept-ranges: bytes





On Tue, Nov 17, 2020, at 3:44 PM, Rick wrote:
> 
> 
> Because all plugins URL point to 
> https://updates.jenkins.io/download/plugins/xxx instead of the mirror.  
> 
> 
> 
> 
> 
> On 11/17/2020 22:40，Tim Jacomb wrote：
>> Why don’t the regular files work? Users should be directed to a Chinese 
>> mirror already, is it the distance to get the redirect?
>> 
>> On Tue, 17 Nov 2020 at 14:02, Rick  wrote:
>>> 
>>> Yes, we just need to change the URL of plugins.
>>> 
>>> You mean generate two or more versions of update-cener.json files? For 
>>> example, update-center.json and update-center-zh.json ? Am I right?
>>> 
>>> 
>>> 
>>> 
>>> On 11/17/2020 21:57，Daniel Beck wrote：
 
 
> On 17. Nov 2020, at 14:48, Rick  wrote:
> 
> I try to modify the URL plugins into a mirror one. But it's unavailable 
> due
> to security reasons. Jenkins will do the validation with 
> update-center.json
> file. In order to fix this, I just make my own certificate file. Before
> using it, you need to download the certificate file into your Jenkins. 
> It's
> still very inconvenient for many users.
> 
> So, I was wondering if I can get permission of accessing the official
> certificate file. People just don't need to do anything besides changing
> the URL of the update center. I know this file should not share with
> someone who is not a member of the Jenkins infra team. Because it's very
> important for all Jenkins users. An alternative solution is that we store
> the certificate file in a safe place. For example, store it in the GitHub
> secret.
 
 If the only change is download URLs that point to a site in China, we can 
 look into generating appropriately modified files in the regular update 
 center which you can then pull without modification.
 
 -- 
 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/D60E8D5F-A3E0-4FB1-A815-F0A28B7FEA37%40beckweb.net.
>>> 
>>> 

>>> -- 
>>> 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/44f497ab.6a8f.175d683041f.Coremail.zxjlwt%40126.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/CAH-3BieGO-irB1C7U0ct4eZ%2BXabp1Jy4Mfsu0Wy8JUPjLKznOA%40mail.gmail.com
>>  
>> 

Re: Jenkins Jira migration has started

['Olblak' via Jenkins Developers]

Hey  Francisco

Can you give it another try?


On Tue, Nov 10, 2020, at 8:48 AM, Francisco Javier Fernandez wrote:
> Mark, I'm trying to log in but I always get an error message as if my user 
> and/or password are invalid. Are you aware of any any issue with the 
> authentication or did I miss any step I should have taken?
> 
> El lunes, 9 de noviembre de 2020 a las 15:13:24 UTC+1, Mark Waite escribió:
>> As previously announced, Jenkins Jira is now offline for scheduled 
>> maintenance.  Expected maintenance window is 4 hours.  At conclusion of the 
>> maintenance window, we expect to be online and running Jira 8, hosted on a 
>> server managed by the Linux Foundation.
>> 
> 

> -- 
> 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/2a908fb8-f7b1-48f0-9282-90699d5a1f23n%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/62eeef92-fd5a-47d0-acde-62b68249a218%40www.fastmail.com.

2020/11/09 - 2 PM UTC - issues.jenkins-ci.org - Maintenance Window

['Olblak' via Jenkins Developers]

Hi Everybody,


I am excited to announce that after a week of testing, we are ready to migrate 
our ticket service, issues.jenkins-ci.org, to the Linux Foundation by next 
Monday, the 9th of November 2020. The maintenance window will start at 2 PM UTC 
and we expect it to last for 3hours.


We’ll do the following actions during the maintenance window:


 1. We'll stop the Apache service so we are sure that nobody updates 
issues.jenkins-ci.org contents on the old machine.

 2. We'll back up the service.

 3. We’ll restore the backup on the Linux foundation machine.

 4. We’ll update the DNS record to redirect traffic to the Linux Foundation 
machine.

 5. I’ll drink a glass of hops juice to celebrate when everything is done.



Remark: Like it should have been since a while, the new official URL will be 
issues.jenkins.io instead of issues.jenkins-ci.org, and the later one will 
become a redirect.

If everything goes well, next Monday at 5 PM UTC, the Jenkins project will be 
offloaded for one of his major websites which have been around since the 17th 
of February 2011, according to our sponsored Atlassian license.


This service is being used to track issues or ongoing work related to the 
Jenkins project

It’s a critical service for the project and represents several hundreds of 
Gigabytes of traffic per month. But at the same time, the Jenkins project keeps 
growing month after month and it has become difficult to find the time needed 
to correctly maintain this service at the scale the Jenkins project is running. 
The Linux foundation offered to maintain it and we took this opportunity so we 
could focus on other areas.


I already want to thank the Linux foundation for taking ownership of this 
service but also the OSUOSL organization that provided the machine and the 
managed database for running this service at scale for that long and of course 
I can't forget all the people who helped maintain this service.


Thanks to Kohsuke Kawaguchi, Tyler Croy, Tim Jacomb, Mark Waite, Arnaud 
Heritier, Andrew Bayer, Daniel Beck, Oleg Nenashev, and my rubber duck.


Cheers,


Olivier

-- 
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/de7d37dc-e8a1-429a-ac17-4af5ce870fdf%40www.fastmail.com.

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

['Olblak' via Jenkins Developers]

Quick update here, the sponsoring plan has been validated on Docker side but 
atm there is nothing on the inferface which tell that we are using an OSS plan.

Regarding, the "Document that Docker Engine or Docker Desktop are required to 
run their whitelisted images", I have been told that's it's an issue.

On Mon, Nov 2, 2020, at 11:31 AM, 'Olblak' via Jenkins Developers wrote:
> Hi Richard,
> 
> Thanks for your input, you are raising a good concern which need 
> clarification. I'll ask the question and I'll share what I found here once I 
> get it.
> 
> On Mon, Nov 2, 2020, at 9:25 AM, Richard Bywater wrote:
>> Not sure if it's just me, but does "Document that Docker Engine or Docker 
>> Desktop are required to run their whitelisted images" concern anyone else?
>> 
>> I mean as a supplier who is providing "free" stuff to an open source project 
>> I agree they should get full attribution etc. for providing their services, 
>> but having to document something which says that using Docker products is 
>> required to run the images seems a bit anti-competitive. 
>> 
>> Perhaps it's just me having a bad day or reading way too much into it :)
>> 
>> Richard.
>> 
>> On Mon, 2 Nov 2020 at 20:22, 'Olblak' via Jenkins Infrastructure 
>>  wrote:
>>> __
>>> Hey, 
>>> Considering that the Dockerhub sponsoring way is ongoing, I didn't pay for 
>>> anythin  and  I prepare to wait few days. 
>>> So if something goes wrong, we know where to look
>>> 
>>> On Sat, Oct 31, 2020, at 9:14 AM, 'Olblak' via Jenkins Infrastructure wrote:
>>>> Hi Everybody, 
>>>> 
>>>> It seems that things are moving positively for us on the sponsoring 
>>>> program side. I just received this email from Docker.
>>>> Obviously I asked to move forward with our application but at this stage, 
>>>> I don't know when it will be effective.
>>>> 
>>>> Anyway I am going to do some clean up in the Dockerhub organisation member.
>>>> 
>>>> Cheers
>>>> 
>>>> 
>>>>> Hello Olivier,
>>>>> 
>>>>> Congratulations! After reviewing your submission for the Docker Open 
>>>>> Source Community Application, we are pleased to inform you that we are 
>>>>> moving forward with your application.  We appreciate your taking the time 
>>>>> to fill out this application, and apologize that it has taken us this 
>>>>> long to get back to you.  The policies that we announced in August will 
>>>>> create a significant impact for the entire Docker community, and we thank 
>>>>> you for your patience as we went through the process of learning how 
>>>>> these policies affect the different cohorts within our community.  

>>>>> Docker New Image Retention and Data Egress Policies

>>>>> In August, we announced to our dedicated community that we are creating 
>>>>> new policies for image retention 
>>>>> <https://www.docker.com/blog/scaling-dockers-business-to-serve-millions-more-developers-storage/>
>>>>>  and data pull rates 
>>>>> <https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/>.
>>>>>   We made these changes to make Docker a sustainable business for the 
>>>>> long term, so that we can continue supporting the community and ecosystem 
>>>>> that depends on the Docker platform.  We got great feedback from our 
>>>>> extensive user base, and adjusted 
>>>>> <https://www.docker.com/blog/docker-hub-image-retention-policy-delayed-and-subscription-updates/>
>>>>>  our policies to suspend the policies on image retention.  The plan for 
>>>>> data pull rates is moving forward, and starting on Nov 2 - 

>>>>>  * Unauthenticated users will be restricted to 100 pulls every 6 hours

>>>>>  * Authenticated free users will be restricted to 200 pulls every 6 hours

>>>>> Docker Open Source Policy

>>>>> Docker remains highly committed to providing a platform where the 
>>>>> non-commercial open source developers can continue collaborating, 
>>>>> innovating and pushing this industry into new directions.  For the 
>>>>> approved, non-commercial, open source namespaces, Docker will suspend 
>>>>> data pull rate restrictions, with no egress restrictions applying to any 
>>>>> Docker users pulling images from those namespa

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

['Olblak' via Jenkins Developers]

e license 
>>>> <https://opensource.org/licenses/alphabetical>

>>>>  * Produce Docker images used to run applications

>>>> Review and Approval

>>>> The process for applying for Open Source status is summarized below -

>>>>  * The Publisher submits the Open Source Community Application form 
>>>> <https://www.docker.com/community/open-source/application>. 

>>>>  * Docker reviews the form, and determines if the Publisher qualifies for 
>>>> open source status.

>>>>* If the Partner qualifies, Docker will waive the pull rate policy for 
>>>> the Publisher’s namespace, for a period of one year

>>>>  * Every 12 months, Docker will review if the Publisher’s namespace 
>>>> qualifies with the Docker Open Source project criteria, and extend the 
>>>> Open Source project status for another 12 months.  

>>>>  * Docker may, at its discretion, also review eligibility criteria within 
>>>> the 12-months period

>>>>  * The publisher may have other namespaces, that either partially comply 
>>>> or do not comply with open source policy requirements, and therefore, will 
>>>> not qualify for open source status

>>>> Joint Marketing Programs

>>>> While the publisher retains the Open Source project status, the Publisher 
>>>> agrees to -

>>>>  * Become a Docker public reference for press releases, blogs, webinars, 
>>>> etc

>>>>  * Create joint blogs, webinars and other marketing content 

>>>>  * Create explicit links to their Docker Hub repos, with no ‘wrapping’ or 
>>>> hiding sources of their images

>>>>  * Document that Docker Engine or Docker Desktop are required to run their 
>>>> whitelisted images

>>>>  * Give Docker full attribution  

>>>> 
>>>> Please let me know if you have any questions on anything in this letter.

>>>> 
>>>> Please reply to this email if your open source project complies with the 
>>>> above criteria, and if you would like to move forward with your Docker 
>>>> Open Source Project.

>>>> 
>>>> Thank you for all your support for Docker and the Docker community.

>>>> 
>>>> Many thanks

>>>> William Quiviger

>>>> Sr. Community Relations Manager

>>> 
>>> 
>>> On Fri, Oct 30, 2020, at 4:09 PM, Baptiste Mathus wrote:
>>>> LGTM. I'm not active anymore on the infra side these days.
>>>> 
>>>> Thanks
>>>> 
>>>> On Fri, Oct 30, 2020 at 2:58 PM Tim Jacomb  wrote:
>>>>> Fixing infra mailing list cc
>>>>> 
>>>>> On Fri, 30 Oct 2020 at 13:57, Tim Jacomb  wrote:
>>>>>> +1
>>>>>> 
>>>>>> On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers 
>>>>>>  wrote:
>>>>>>> Hi Everybody,
>>>>>>> 
>>>>>>> The Dockerhub policy change start on Sunday unfortunately I couldn't 
>>>>>>> make significant progress on this.
>>>>>>> Either by being sponsored by Docker or having a proper way to be 
>>>>>>> reimbursed by LF.
>>>>>>> 
>>>>>>> I would like to pay (be reimbursed) for at least the first month and 
>>>>>>> remove the none critical people in order to reduce the cost.
>>>>>>> 
>>>>>>> I would remove the following people:
>>>>>>> * Kohsuke Kawaguchi
>>>>>>> * Nicolas Deloof
>>>>>>> * Baptiste Mathus
>>>>>>> * Tyler Croy
>>>>>>> * Carlos Sanchez
>>>>>>> * Jesse Glick
>>>>>>> * Michael Neale
>>>>>>> * Oliver Gondza
>>>>>>> 
>>>>>>> Cheers
>>>>>>> 
>>>>>>> -- 
>>>>>>> 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 
>>>>>>> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid

Re: [jenkins-infra] Re: Paying for Dockerhub pro plan

['Olblak' via Jenkins Developers]

press releases, blogs, webinars, etc

>>  * Create joint blogs, webinars and other marketing content 

>>  * Create explicit links to their Docker Hub repos, with no ‘wrapping’ or 
>> hiding sources of their images

>>  * Document that Docker Engine or Docker Desktop are required to run their 
>> whitelisted images

>>  * Give Docker full attribution  

>> 
>> Please let me know if you have any questions on anything in this letter.

>> 
>> Please reply to this email if your open source project complies with the 
>> above criteria, and if you would like to move forward with your Docker Open 
>> Source Project.

>> 
>> Thank you for all your support for Docker and the Docker community.

>> 
>> Many thanks

>> William Quiviger

>> Sr. Community Relations Manager

> 
> 
> On Fri, Oct 30, 2020, at 4:09 PM, Baptiste Mathus wrote:
>> LGTM. I'm not active anymore on the infra side these days.
>> 
>> Thanks
>> 
>> On Fri, Oct 30, 2020 at 2:58 PM Tim Jacomb  wrote:
>>> Fixing infra mailing list cc
>>> 
>>> On Fri, 30 Oct 2020 at 13:57, Tim Jacomb  wrote:
>>>> +1
>>>> 
>>>> On Fri, 30 Oct 2020 at 13:50, 'Olblak' via Jenkins Developers 
>>>>  wrote:
>>>>> Hi Everybody,
>>>>> 
>>>>> The Dockerhub policy change start on Sunday unfortunately I couldn't make 
>>>>> significant progress on this.
>>>>> Either by being sponsored by Docker or having a proper way to be 
>>>>> reimbursed by LF.
>>>>> 
>>>>> I would like to pay (be reimbursed) for at least the first month and 
>>>>> remove the none critical people in order to reduce the cost.
>>>>> 
>>>>> I would remove the following people:
>>>>> * Kohsuke Kawaguchi
>>>>> * Nicolas Deloof
>>>>> * Baptiste Mathus
>>>>> * Tyler Croy
>>>>> * Carlos Sanchez
>>>>> * Jesse Glick
>>>>> * Michael Neale
>>>>> * Oliver Gondza
>>>>> 
>>>>> Cheers
>>>>> 
>>>>> -- 
>>>>> 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 
>>>>> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/5804a3e6-ebf2-4707-9824-90eb02fcc6ad%40www.fastmail.com.
>>> 

>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Infrastructure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to jenkins-infra+unsubscr...@googlegroups.com.
>>> To view this discussion on the web, visit 
>>> https://groups.google.com/d/msgid/jenkins-infra/CAH-3BifxsfSmBo2K%3D1T5whoHTsBQ0Ts3EpnZXHHrqgZkvFVfjQ%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkins-infra/CAH-3BifxsfSmBo2K%3D1T5whoHTsBQ0Ts3EpnZXHHrqgZkvFVfjQ%40mail.gmail.com?utm_medium=email_source=footer>.
>> 

>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Infrastructure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins-infra+unsubscr...@googlegroups.com.
>> To view this discussion on the web, visit 
>> https://groups.google.com/d/msgid/jenkins-infra/CAPyTVp07Po2su%2B-DSc2G52-gF97NPXL8aoymjbv1%3DT%3DnNcjUGQ%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkins-infra/CAPyTVp07Po2su%2B-DSc2G52-gF97NPXL8aoymjbv1%3DT%3DnNcjUGQ%40mail.gmail.com?utm_medium=email_source=footer>.
> 
> 

> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Infrastructure" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkins-infra+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/jenkins-infra/56f9d6b1-2e6e-4062-a841-3b2ad928066d%40www.fastmail.com
>  
> <https://groups.google.com/d/msgid/jenkins-infra/56f9d6b1-2e6e-4062-a841-3b2ad928066d%40www.fastmail.com?utm_medium=email_source=footer>.

-- 
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/950effd9-d9c5-494c-ba31-52dfea021e8f%40www.fastmail.com.

Re: Paying for Dockerhub pro plan

['Olblak' via Jenkins Developers]

This would be 7$ per month paid for following users:
on Jenkinsci (21$) 
* me
* oleg Nenashev
* jenkinsinfraadmin

I also would like to pay for jenkins-infra organisation for following people
on Jenkins-infra (21$)
* me
* Mark Waite
* jenkinsinfraadmin

I wouldn't pay for jenkinsci4eval

Again I more see this as a temporary solution while we find a better solution 
 
> +1
> 
> > On Oct 30, 2020, at 6:49 AM, 'Olblak' via Jenkins Developers 
> >  wrote:
> > 
> > Hi Everybody,
> > 
> > The Dockerhub policy change start on Sunday unfortunately I couldn't make 
> > significant progress on this.
> > Either by being sponsored by Docker or having a proper way to be reimbursed 
> > by LF.
> > 
> > I would like to pay (be reimbursed) for at least the first month and remove 
> > the none critical people in order to reduce the cost.
> > 
> > I would remove the following people:
> > * Kohsuke Kawaguchi
> > * Nicolas Deloof
> > * Baptiste Mathus
> > * Tyler Croy
> > * Carlos Sanchez
> > * Jesse Glick
> > * Michael Neale
> > * Oliver Gondza
> > 
> > Cheers
> > 
> > --
> > 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/5804a3e6-ebf2-4707-9824-90eb02fcc6ad%40www.fastmail.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/0DB00077-3A87-4D90-B7AB-2BF1F553035B%40gmail.com.
> 
> Attachments:
> * signature.asc

-- 
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/f6b4014b-d3ad-44c0-8a8c-1ada957b7c1c%40www.fastmail.com.

Re: Availability of Oliver Gondža in late 2020 and onward

['Olblak' via Jenkins Developers]

Hi Oliver,

Thanks for all contributions you did to the project. You are totally right to 
step back.
The adventure you are going to live is way more important and enjoyable if you 
free yourself from less important distractions.

I wish all the best to you and your second half.

Cheers


On Wed, Oct 21, 2020, at 12:38 PM, Victor Martinez wrote:
> Congrats Oliver for the awesome news. Thanks for all the work you have done 
> for the Jenkins project, that's quite impressive, again thanks! <3 
> 
> On Tuesday, 20 October 2020 at 17:50:04 UTC+1 marky.r...@gmail.com wrote:
>> Oliver, 
>> I first and foremost want to say congratulations on the upcoming additions 
>> to the family. This really is a joyous time and I am so happy for you. 
>> Next, I want to thank you for all that you have done over the years as well 
>> as for your mentorship. This project would not be where it is without you. 
>> If there is anything I can take on to help the transition, please do not 
>> hesitate to call on me. 
>> 
>> 
>> > On Oct 20, 2020, at 1:24 AM, Oliver Gondža  wrote: 
>> > 
>> > Hey Folks, After all those years with the project doing my best here and 
>> > there (Release and LTS officer, reviewer and maintainer of a number of 
>> > components), I have chosen to step back a bit. Partially as my focus is 
>> > shifting away slowly, but mostly to direct my attention to my family and 
>> > the twins expected to be born in a couple of weeks. 
>> > 
>> > Because of that: 
>> > 
>> > - I will not be a candidate for a Release officer nor a Board member this 
>> > year. 
>> > - I will no longer maintain jenkinsci/acceptance-test-harness. 
>> > - The responsibility for leading LTS will be gradually transferred to some 
>> > community member interested. 
>> > 
>> > I have truly enjoyed those 8 years in a company of so many talented and 
>> > engaged engineers. It is not that I am leaving never to show up again, but 
>> > this housekeeping is long overdue, and I owe doing this to the project and 
>> > to myself. 
>> > 
>> > Thanks! 
>> > -- 
>> > oliver 
>> > 
>> > -- 
>> > 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/0a98fdb2-6f21-d55d-c197-0b32745628ed%40gmail.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/f04211f4-8785-41bc-bea5-26f1a38c8c82n%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/2562dcee-59a6-44ea-b99a-6ffd86eba82f%40www.fastmail.com.

Re: Request to be added as Twitter admin

['Olblak' via Jenkins Developers]

+1 

On Wed, Oct 21, 2020, at 10:49 PM, Slide wrote:
> Big +1
> 
> On Wed, Oct 21, 2020 at 11:06 AM Arnaud Héritier  wrote:
>> +1
>> 
>> Le mer. 21 oct. 2020 à 19:48, Marky Jackson  a 
>> écrit :
>>> +1 from me
>>> 
>>> 
 On Oct 21, 2020, at 10:47 AM, Alyssa Tong  wrote:
 
 Hello,
 
 I'd like to request to be added as admin for Twitter so I may help with 
 tweets.  I am currently the Events officer for the project and driving the 
 Jenkins is the Way initiative.
 
 Thank you,
 alyssa 
 
 --
 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/CAC9wNazqRzr2O-jFtXV7b6KGOnDk3kPVnysnQJH60XrMotODhA%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/18210F7C-E9F9-4181-B6F1-6CFBA01A87C1%40gmail.com
>>>  
>>> .
>> -- 
>> Arnaud Héritier
>> Twitter/Skype : aheritier
>> 

>> --
>> 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/CAFNCU-9PZpYa44dr5voNi-addBfxiBKnmLvMiFQ%2Bw4RzGn5G_g%40mail.gmail.com
>>  
>> .
> 
> 
> -- 
> Website: http://earl-of-code.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/CAPiUgVeLW04B8UyeZvV1c4AOXw153v8OEqiB7WO%3DEYg5CcK%3Dbg%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/736ac704-3e53-43ce-9be9-9d8b672c1eda%40www.fastmail.com.

Jenkins weekly release outage

['Olblak' via Jenkins Developers]

Dear All,

I would like to do a quick postmortem for yesterday’s Jenkins weekly release 
outage that lasted for about 6h30.  The weekly release Jenkins 2.263 was listed 
on www.jenkins.io as available but was not available to download.

Since April 2020, the weekly release is fully automated and triggered every 
Tuesday by this job 

 

It runs two Jenkins jobs from a specific jenkins instance:
1) Build maven artifacts then publish them on repo.jenkins-ci.org, like on 
repo.jenkins-ci.org 

2) Build distribution packages using the jenkins.war from the maven repository 
then update our mirror infrastructure

Yesterday, the second stage failed on the window package step which resulted in 
no distribution packages published at all.

But because a new version has been published on our maven repository by the 
first job, every Jenkins instance was notified that a new weekly version was 
available. And because we didn't update our mirror infrastructure, nobody was 
able to fetch the update. It took us 6h30 before fixing it, fortunately enough, 
the second stage is pretty quick, +-15min versus the 2h needed for the first 
stage, so we rerun the job without windows packaging.

Remark: At the moment the windows package is still not published due to a 
Windows issue in the infrastructure

This outage reminded us that we still have work to do and help is definitely 
more than welcome :)

*Issues**
*

* [INFRA-2538 ] -> To fix the 
windows packaging issue
* We wrote a python script to detect the latest version from 
maven-metadata.xml, for some reason the metadata 

 file we rely on, still references the previous weekly release 2.262 while all 
the other maven-metadata.xml are correct. :/

*Monitoring*

6h30 is way too long to detect such issue, fatigue habit is a thing and we must 
detect when something went wrong as fast as possible 
[INFRA-2027] -> I started working on a python script that we could use with 
Datadog but I haven't had the time to finish it yet

*Artifact Promotion*
 
While it would have not solved the current problem, we could have published the 
maven release to a temporary maven repository then only promote the artifacts 
once every distribution package is available.
So people would not have been notified, considering that we mainly rely on 
people monitoring this would have probably delayed even more the release. We 
already have that logic in place as it's needed for the security release 
anyway, we just have to agree on a staging repository.

We’ll be working on those improvements and will share our progress as the 
improvements become available.

Cheers,

Olblak

-- 
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/4c4cc1b0-ee5e-4faf-ac7e-677e50dd36f5%40www.fastmail.com.

Re: Proposal: Updating Jenkins officer role definitions ahead of the election

['Olblak' via Jenkins Developers]

Hi Oleg,

I totally agree with you, officer role are not one man jobs. I find it more 
accurate to highlight that they are about coordinating the different 
initiatives and finding contributors than being the person who's suppose to 
work on those.


> 
> I will add the topics to the today's governance meeting
> 
> Best regards,
> Oleg
> 
> On Wednesday, October 7, 2020 at 12:43:49 PM UTC+2 Oleg Nenashev wrote:
>> Dear all,
>> 
>> As discussed at the previous Governance meeting, I suggest to revise the 
>> definition of Jenkins Officer roles listed on this page 
>> . These roles were defined in 
>> 2015-2016 as a part of the original officers proposal, and the effective 
>> responsibilities have drifted from the original descriptions. It would be 
>> great to update the role definitions ahead of the elections, so that the 
>> nominees and voters can see actual responsibilities.
>> 
>> A few changes I would like to suggest:
>>  * Shift roles from doing the administrative/maintenance work on their own 
>> to coordinating the work inside the teams and SIGs led by the officers. 
>> While officers are responsible to ensure that the mission-critical community 
>> processes work, they are not expected to work on them single-handedly. More 
>> delegation and sharing responsibilities is a good thing for project 
>> sustainability.
>>  * Set expectations about onboarding new contributors to the teams, 
>> knowledge sharing, and facilitating contributions to the area of 
>> responsibility. All teams would benefit from having more contributors and 
>> clear requirements/ladder for those who want to take roles within the teams.
>>  * TBD: The bullet above might be even extended to having "shadow" or 
>> "deputy" officers as it was proposed by contributors in the past. Such 
>> approach could help to ensure healthy officer rotation in the project, with 
>> opportunity for officers to move on to other roles or to take a break when 
>> needed.
>>  * Add expectation about facilitating initiatives within the scope of the 
>> responsibility, and maintaining the team's roadmap.
>> A while ago I submitted 
>> https://github.com/jenkins-infra/jenkins.io/pull/2943 for the event officer 
>> definition (follow-up to the previous PR by Alyssa Tong and Mark Waite). I 
>> suggest using it for collaborative editing of the role definitions. Please 
>> feel free to propose any changes in this thread or in the pull request.
>> 
>> Best regards,
>> Oleg Nenashev
>> 
> 

> --
> 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/dbd6b25d-66a2-4907-9b7b-4ad73cd7df7cn%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/95e5479e-b906-4d25-891f-b2aed94aeea7%40www.fastmail.com.

Re: Events Officer Role

['Olblak' via Jenkins Developers]

That was a pleasure to work with you on Jenkins area meetups, Fosdem 
organization, and many other stuff. 
You did an amazing work to shape what Jenkins is today so thank you for energy.




On Mon, Oct 5, 2020, at 6:20 PM, Alyssa Tong wrote:
> Thank you Oleg
> 
> On Mon, Oct 5, 2020 at 5:49 AM Oleg Nenashev  wrote:
>> Hi Alyssa,
>> 
>> Indeed it has been a *VERY *long term. On behalf of the Jenkins board and 
>> the community, I would like to thank you for all contributions you've made 
>> during your tenure! Your efforts in organizing and coordinating the 
>> community evens/conferences have been essential to the Jenkins project's and 
>> the community's well-being and future. Jenkins World, FOSDEM, Scale, JAMs 
>> and other events... All of them have been essential to promote the project, 
>> and to attract new users and contributors. There have been a lot of other 
>> community events and outreach programs organized over the past years. Thank 
>> you!
>> 
>> Looking forward to continue working with you in Advocacy! Whomever 
>> will be the next Events officer (nominations are welcome!), your 
>> contributions will be much appreciated! 
>> 
>> Best regards,
>> Oleg Nenashev
>> 
>> P.S: Hopefully we will be able to maintain the current trend and to make the 
>> events organization/logistics more and more distributed effort within the 
>> SIG. With it and with consolidating some events on the CDF level, we have an 
>> opportunity to make the events less time demanding, and to start gradually 
>> switching the officer role from "just" events to outreach in general. A lot 
>> to be done on this front. Thanks to Alyssa, we have already handed over some 
>> tedious administration tasks to CDF. 
>> 
>> On Friday, October 2, 2020 at 11:41:12 PM UTC+2 alytong13 wrote:
>>> Am happy to work with great people with a great cause  :)
>>> 
>>> 
>>> On Fri, Oct 2, 2020 at 1:40 PM Mark Waite  wrote:
 Thanks so much for your work as events officer and your continuing efforts 
 to promote Jenkins!
 
 On Fri, Oct 2, 2020 at 12:13 PM Alyssa Tong  wrote:
> Hi All,

> 

> As I've been Events Officer for quite some time now, I would like to step 
> down from this role at the end of my tenure on 3 December 2020. I feel 
> giving others a chance to fulfill this role will bring new insights and 
> creativity.

> 
> I will continue to contribute to the Jenkins project by ways of 
> participation in the Advocacy and Outreach SIG, drive the Jenkins is the 
> Way initiative, assist the new Events Officer in the transition and in 
> events related activities.

> 
> Thank you,
> alyssa
> 

> --
> 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/CAC9wNaw1Ai4rw3%2BkNLa5DhLghqyBcJe%3D9sY0AMdH5abdRYZzTQ%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 discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH2XVkRE1bAVGhbYLFOQn0T06G5h%2B-gAUD1BX4gwmUvGA%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/e01f703c-e0bd-4587-9784-b8b42e2e7083n%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/CAC9wNaxW58W%3DQTZj%2Bz%3DQsYHrP%2Bye%3DW1ESFn3x1W%2BOdsrFezURQ%40mail.gmail.com
>  
> 

Re: Governance Board

['Olblak' via Jenkins Developers]

Hi Alex,

Congratulation on your new role change and thanks for all the things you did.
I really enjoyed working with you.

Mmmmh I'll better find a windows expert to protect my mental health :D 

>> 
>> First of all, thanks a lot for all your contributions to the Jenkins 
>> project! You've been doing A LOT for the community as a governance board 
>> member, and it is much appreciated. I totally understand your decision,  and 
>> I am looking forward to continue working with you on other areas of the 
>> Jenkins community . I will do my best to assist with whatever transition 
>> steps required for the board member role and other roles if you decide to 
>> step down from them.
>> 
>> Best wishes to you in the new role! 
>> 
>> Best regards.,
>> Oleg
>> On Monday, September 28, 2020 at 8:07:25 PM UTC+2 slide wrote:
>>> Thanks Marky!
>>> 
>>> 
>>> On Mon, Sep 28, 2020 at 10:36 AM Marky Jackson  wrote:
 I want to thank you for all that you have given to this community while 
 being on the board Alex. Your commitment is so valued and I am personally 
 so thankful for you.
 
 On Monday, September 28, 2020 at 10:31:24 AM UTC-7 slide wrote:
> Hi Everyone,
> 
> Just wanted to send out an email announcing that I will be resigning from 
> the Jenkins Governance Board after a one year term (instead of two 
> years). This will open up two spots for Governance Board members during 
> the elections this year. My role at work is changing and I will not have 
> the time to work on Jenkins as much as I would like. I feel that other 
> people who do have the time would be more of a benefit to the project and 
> community. 
> 
> Thanks!
> 
> Alex Earl
> 
> -- 
> Website: http://earl-of-code.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 discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/18afcc45-edd6-4ee8-ad54-fd94f54fbb44n%40googlegroups.com
  
 .
>>> 
>>> 
>>> -- 
>>> Website: http://earl-of-code.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/f0c87d20-e7b6-4f2e-9b1c-74f0a7fd8865n%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/8a22bff2-7943-48c7-8adc-63ec2ca58654%40www.fastmail.com.

Re: Jenkinc-ci account recovery

['Olblak' via Jenkins Developers]

Hi Long,

Your request seems legit to me so I updated your email address, can I ask you 
to reset your password on https://beta.accounts.jenkins.io

Cheers

On Thu, Oct 1, 2020, at 4:32 AM, long song wrote:
> hi Mark,
> 
> X Sun left last year and does not contribute to 
> https://github.com/jenkinsci/neuvector-vulnerability-scanner-plugin anymore.
> 
> I contacted him but he can't remember the email address and the credentials.
> 
> I am currently the maintainer of neuvector-vulnerability-scanner-plugin. 
> 
> My identity can be verified at Github 
> https://github.com/jenkinsci/neuvector-vulnerability-scanner-plugin in the 
> contributor list.
> 
> Would you help to reset the email address ?
> 
> Thanks!
> Long
> 
> On Wed, Sep 30, 2020 at 5:51 PM Mark Waite  wrote:
>> That account is associated with a hotmail account for X Sun.  I don't think 
>> that I'm allowed to reset the password or change control of that account to 
>> a different person without some evidence from the other person that they are 
>> willing to surrender that account.  Can you work with the person that 
>> controls that hotmail account and have them assist you with the password 
>> reset process?
>> 
>> On Wed, Sep 30, 2020 at 6:17 PM long song  wrote:
>>> hi Mark,
>>> 
>>> The account is neuvector.
>>> 
>>> Thanks!
>>> Long
>>> 
>>> On Wed, Sep 30, 2020 at 4:39 PM Mark Waite  
>>> wrote:
 You did not mention the userid of your account on jenkins.io.  I made the 
 assumption of `songlongcn` based on the entry in the pom file 
 ,
  but there is no such user.  I did find a user with a similar user name 
 (but not the same) with a yahoo.com email address.  Do you have access to 
 that email account?
 
 On Wed, Sep 30, 2020 at 5:30 PM long song  wrote:
> Hi there,
> 
> I have been the maintainer of the Jenkins neuvector vulnerability scanner 
> Plugin for a while. I was just trying to do a release when I faced the 
> biggest problem some of us sometimes face: I forgot my password for the 
> accounts.jenkins.io
> 
> The account was created by a former employee and he can't remember what 
> was the signup email address. Now it seems that the reset password email 
> went to an unknown email.
> 
> Question is: how can I recover that?
> 
> To confirm my identity, please check -> 
> https://github.com/jenkinsci/neuvector-vulnerability-scanner-plugin
> Thanks in advance !
> 
> Cheers,
> Long
> 

> --
> 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/48e38f75-689e-48c8-878b-41f4a11aa9aen%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/CAO49JtHQuP_L_SN_pE9e9PhjrC%3DOQpXtBUXd3kgi4KY5aS0Zmg%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/CANDLext9uFbVT%2Bj6Hn%3DoJAsK-hhFYWnTmfc2P36H6pJpcNoHDg%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/CAO49JtGmN1s5SS6um%2BMVUk9TAK5yxLbhrOk7RB1d3hcTi35htQ%40mail.gmail.com
>>  
>> .
> 

Re: Jenkins Elections Process Question

['Olblak' via Jenkins Developers]

> We are using a Google Form for the sign-up and it provides a mechanism to 
> collect email addresses, but it requires users to login to a Google account 
> when using the Google Forms mechanism. It does allow us to reduce the 
> possibility of duplicate voting.
It hurts me to say that but we already ask contributors to use a google account 
to follow discussion happening here so asking people to use their google 
account to vote shouldn't be a major concerned. But we would have no way to 
match a google account with a jenkins account...

Otherwise we already have oauth-proxy integrated with our ldap database, so we 
could write a small application that read the username field from the oauth 
token generated once we go to something like 'register.jenkins.io'.

IMHO asking people to register to a mailing list like 
jenkinsci-electi...@googlegroups.com  seems the 
easier and more sustainable solution. We could by default block new 
registrations during the pre- election period, several weeks before  and we 
would only accepted people who can show a contribution done before the 
pre-election period.   



On Wed, Sep 23, 2020, at 12:11 AM, Oleg Nenashev wrote:
> It would make sense, though I am not sure how another email domain would make 
> a difference there. Sending emails to Google addresses is not blocked in 
> China from what I know. CDF might be able to set up an email for us, but I am 
> not sure about timing. If we want to start the sign-up process on Sep 24 as 
> planned, it would be quite a challenge to get the email in time. 
> 
> Any thoughts from others?
> 
> On Tue, Sep 22, 2020 at 8:12 PM 'Gavin Mogan' via Jenkins Developers 
>  wrote:
>> > jenkins-2020-elections@googlegroup
>> > It will definitely help contributors in areas where Google services are 
>> > blocked 
>> 
>> Wouldn't it make sense for the fallback email to be something other than 
>> google then?
>> 
>> cd.foundation is using mailgun (according to MX records), so maybe they 
>> could setup jenkins-2020-elections@cd.foundation that forwards to google/the 
>> board, so there's no issues.
>> 
>> Gavin
>> 
>> On Tue, Sep 22, 2020 at 11:01 AM Oleg Nenashev  
>> wrote:
>>> As an additional mitigation, we can also add a "send a sign-up email to 
>>> jenkins-2020-elections@googlegroups" fallback process to the announcement. 
>>> It will definitely help contributors in areas where Google services are 
>>> blocked
>>> 
>>> On Tue, Sep 22, 2020, 19:00 Mark Waite  wrote:
 
 
 On Tue, Sep 22, 2020 at 4:28 AM Oleg Nenashev  
 wrote:
> >   it requires users to login to a Google account when using the Google 
> > Forms mechanism. It does allow us to reduce the possibility of 
> > duplicate voting.  
> 
> Apart from duplicate voting, it also prevents from submitting voting 
> sign-up forms for other individuals. If we do not use a Google account or 
> any other authentication service, anyone will be able to submit a form 
> for anyone else, including doing submissions for participants who may not 
> want their emails to be stored and who do not want to receive 
> communications from the Jenkins project. It increases the risk of abuse 
> for the voting sign-up system.
> 
> We do not want to rely solely on Jenkins LDAP, but I think we need some 
> kind of identity management. Google Auth could bridge the gap, as one of 
> the options we can rollout quickly. We de-facto require it for many other 
> contribution areas.
> 
 
 I think we should use Google Auth to bridge the gap as you've suggested.
  
> 
> Best regards,
> Oleg
> 
> 
> On Monday, September 21, 2020 at 10:15:23 PM UTC+2 Richard Bywater wrote:
>> Personally I don't think we should be forcing people to sign up for 
>> third-party services just to be able to vote on Jenkins related matters. 
>> There may be good reasons that people have for not wanting to create a 
>> Google account.
>> 
>> Richard. 
>> 
>> 
>> On Tue, 22 Sep 2020, 3:15 AM Slide,  wrote:
>>> Hi Everyone,
>>> 
>>> The Jenkins Governance Board Elections Committee is currently 
>>> implementing the process which has been defined for Governance Board 
>>> and Officer Elections. As part of this, we are creating the form that 
>>> will be used for signing up to participate in the elections. We need to 
>>> collect email addresses as part of the process. We are using a Google 
>>> Form for the sign-up and it provides a mechanism to collect email 
>>> addresses, but it requires users to login to a Google account when 
>>> using the Google Forms mechanism. It does allow us to reduce the 
>>> possibility of duplicate voting. We will not keep the data after the 
>>> voting. Another option would be to just have a short text input that 
>>> accepts an email address and we would collect it that way. We 

Re: Need to unlock jenkins.ci account to publish plugin

['Olblak' via Jenkins Developers]

To save both of us time, I updated your profile to use the yahoo.com one feel 
free to reset the password on https://beta.accounts.jenkins.io 

On Sun, Aug 16, 2020, at 2:48 PM, 'Olblak' via Jenkins Developers wrote:
> Hi Marc, 
> The account is currently using a fastmail.fm email address but based on 
> `issues.jenkins-ci.org` information there is also a yahoo one associated to 
> your username so If you prefer I could update your profile to use the 
> yahoo.com one
> 
> 
> On Sun, Aug 16, 2020, at 12:36 PM, Marc Carter wrote:
>> Lapsed Plugin develop here. I cannot release a compatibility fix for my 
>> https://github.com/jenkinsci/ez-templates-plugin as my Jenkins account 
>> 'drekbour' appears to be locked. Since the usual self-help unlocking isn't 
>> sending me any emails, I'm presuming the address associated with it is a 
>> long-defunct one from when Fastmail was still free.
>> 
>> You can observe the authenticity of my gmail account through Github since I 
>> own the repo.
>> 
>> What do you advise?
>> 
>> Marc
>> 

>> --
>> 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/2ec4540f-bfed-4dc2-97ee-ce78e3103cf7o%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/2ec4540f-bfed-4dc2-97ee-ce78e3103cf7o%40googlegroups.com?utm_medium=email_source=footer>.
> 
> 

> --
> 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/62be0135-4c57-4057-a3f6-20d9a7a49003%40www.fastmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/62be0135-4c57-4057-a3f6-20d9a7a49003%40www.fastmail.com?utm_medium=email_source=footer>.

-- 
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/54ceb2d2-3e23-43ce-9604-1d5db1fb5615%40www.fastmail.com.

Re: Need to unlock jenkins.ci account to publish plugin

['Olblak' via Jenkins Developers]

Hi Marc, 
The account is currently using a fastmail.fm email address but based on 
`issues.jenkins-ci.org` information there is also a yahoo one associated to 
your username so If you prefer I could update your profile to use the yahoo.com 
one


On Sun, Aug 16, 2020, at 12:36 PM, Marc Carter wrote:
> Lapsed Plugin develop here. I cannot release a compatibility fix for my 
> https://github.com/jenkinsci/ez-templates-plugin as my Jenkins account 
> 'drekbour' appears to be locked. Since the usual self-help unlocking isn't 
> sending me any emails, I'm presuming the address associated with it is a 
> long-defunct one from when Fastmail was still free.
> 
> You can observe the authenticity of my gmail account through Github since I 
> own the repo.
> 
> What do you advise?
> 
> Marc
> 

> --
> 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/2ec4540f-bfed-4dc2-97ee-ce78e3103cf7o%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/62be0135-4c57-4057-a3f6-20d9a7a49003%40www.fastmail.com.

Re: buildPlugin() now with Warnings NG and GitHub checks

['Olblak' via Jenkins Developers]

Well done \o/

On Thu, Aug 6, 2020, at 8:54 AM, Tim Jacomb wrote:
> Hi all

> 
> I’m happy to announce that the `buildPlugin()` library step that is used by 
> almost all plugins on ci.jenkins.io now uses the Warnings NG plugin 
>  for static code analysis reporting 
> and quality control.

> 
> We have set default quality gate for:

>  * No new spotbugs issues

>  * No checkstyle issues

> Note: in order for spotbugs to calculate your initial issues you will need 
> your master branch ran once to establish a baseline

> 
> You can customise the quality gates, however you wish (enable / disable them, 
> or adjust the severity of the warnings), see the documentation for the 
> pipeline-library 
>  and 
> the Warnings NG  documentation.

> 
> On top of the Warnings NG addition we have switched ci.jenkins.io over to 
> GitHub app authentication (mailing list post 
> ). 
> This gives us much higher rate limits and access to the GitHub checks API.

> 
> Lastly we have installed the GitHub checks 
>  plugin which is a GSoC 2020 
> project by Kezhi Xiong which exposes an API allowing consuming plugins to 
> publish checks results and annotations to GitHub.

> 
> 

> 

> 
> See Kezhi’s GSoC phase 2 demo on YouTube 
> .

> 
> Next steps:

>  * We hope to soon land support for the Code Coverage API plugin in 
> `buildPlugin()` - Code Coverage API plugin already has support for the GitHub 
> checks plugin. - Pull request 
> .

>  * Kezhi and I will be hosting a Jenkins online meetup Mid August on GitHub 
> app authentication and the GitHub checks integration.

>  * Possibly some tuning of severity on some issues - see discussion 
> 

> 
> Feedback

> 
> We would love any feedback, please feel free to provide it either here, in 
> Gitter  or in the issue 
> tracker for the respective component.

> 
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bidxq1BJi8LYzj-ftWfzSkevYro4Z%2B38Bnpx-jqpsDNAsw%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/e8f770f1-a504-4139-bc51-5bb286739ca4%40www.fastmail.com.

Windows packaging back on track

['Olblak' via Jenkins Developers]

Hello, 

I am happy to share that shipping Jenkins MSI packages is now back on track.
I built the MSI for the latest weekly version and once this PR 
 is merged, it will be the 
default behaviour again.

Thanks Alex, Tim, Oleg and Mark for your work on this. 

Cheers

-- 
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/2067caf3-2db2-47b7-82ab-42407cacd3e1%40www.fastmail.com.

Re: timja would like to join Jenkins Infra's Hosting team

['Olblak' via Jenkins Developers]

+1 :-) 

On Fri, Jul 24, 2020, at 8:57 AM, Ullrich Hafner wrote:
> +1
> 
>> Am 23.07.2020 um 20:28 schrieb Mark Waite :
>> 
>> +1
>> 
>> On Thu, Jul 23, 2020 at 9:24 AM Slide  wrote:
>>> +1
>>> 
>>> On Thu, Jul 23, 2020 at 8:16 AM Xiong Kezhi  wrote:
 +1 from me :)
 
 在2020年7月23日星期四 UTC+8 下午11:10:29 写道：
> +1
> 
> 
> 
> On Thu, Jul 23, 2020 at 5:02 PM Oleg Nenashev  wrote:
>> +1 from me
>> 
>> On Thu, Jul 23, 2020 at 4:55 PM Tim Jacomb  wrote:
>>> Hi
>>> 
>>> I would like to join the hosting team 
>>> (https://www.jenkins.io/project/teams/hosting/#requesting-membership)
>>> I believe I meet all the requirements, and have been helping with it 
>>> already in IRC / PRs
>>> 
>>> Thanks
>>> Tim
>>> 
>>> On Thu, 23 Jul 2020 at 15:36, Oleg Nenashev  wrote:
 +1 from me, maybe needs a mirror message to the dev list
 
 On Thu, Jul 23, 2020 at 4:33 PM Jenkins Infra  
 wrote:
> timja has requested to join Jenkins Infra’s Hosting team.
> 
> You may approve or deny this request here:
> 
> https://github.com/orgs/jenkins-infra/teams/hosting/members
>> 
>> -- 
>> 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/CAPfivLDQhtJ_g9-jTow0fiRhkmzcwRhf4TyHNaRjORDOY1_HNQ%40mail.gmail.com
>>  
>> .
> 
> 
> -- 
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
 
 --
 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/3be188d8-e266-45a6-b34d-cf490f686015n%40googlegroups.com
  
 .
>>> 
>>> 
>>> -- 
>>> Website: http://earl-of-code.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/CAPiUgVffR5PQZbRuZ0O0xOfTXsoE3jDE34w73_sGZcDFm6Km0Q%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/CAO49JtHjMrh6jR0fJ0FG95jnc0y0vdwFsm4WaGbavk82Db7%2B-A%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/E40AC6BB-B8D3-4496-8A4C-416965AA70D7%40gmail.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/84c2d822-9b2c-4e5a-af75-dbeee81047f1%40www.fastmail.com.

Re: LTS next week to change repo signing keys

['Olblak' via Jenkins Developers]

Obviously I am fully in for releasing the next LTS from the new release 
environment.


On Thu, Jul 23, 2020, at 8:51 AM, Oliver Gondža wrote:
> I like the idea of dry-running the release procedure with no fixes 
> included. Also, thanks Mark and Olivier for working around you schedules 
> to get this implemented sooner rather than later.
> 
> Do I understand correctly that you suggest to otherwise continue with 
> 2.235 line as it was planned, 2.235.4 RC on 29th of July and 2.235.4 
> Release on 12th of August?
> 
> Are there any objections to Mark's proposal?
> 
> On 22/07/2020 22.16, Vlad Silverman wrote:
> > Thank you Mark for issuing this proposal and clarifying the steps.
> > +1 from me as well.
> > 
> > Please don’t hesitate to ask if any help is needed.
> > 
> > Thx, Vlad
> > 
> >> On Jul 22, 2020, at 12:58 PM, Tim Jacomb  >> > wrote:
> >>
> >> +1 would be great to do one release while Olivier is around.
> >>
> >> Would be good to have at least one user facing change in it, but I 
> >> guess not required.
> >>
> >> Thanks
> >> Tim
> >>
> >> On Wed, 22 Jul 2020 at 20:29, Mark Waite  >> > wrote:
> >>
> >> The core release automation process has been used to deliver
> >> weekly releases since mid-April.  It was used to deliver the
> >> weekly security release recently.  We are ready to deliver the
> >> Long Term Support (LTS) releases with core release automation.
> >>
> >> Olivier Vernin has been the lead implementer of core release
> >> automation work.  He'll be unavailable in August.  We'd like to
> >> deliver an LTS next week, while he is still available.  We'll use
> >> that delivery to train others and verify the release process
> >> documentation.  We'll then run future core releases entirely from
> >> the core release automation.
> >>
> >> *Proposal:*
> >>
> >> Create Jenkins 2.235.3 LTS release the week of July 27 using core
> >> release automation.  We'll use the current tip of the stable-2.235
> >> branch.  build the same code as was used for Jenkins 2.235.2 with
> >> a single .  The changes between 2.235.2 and 2.235.3 would be:
> >>
> >>   * Increment the version number from 2.235.2 to 2.235.3
> >>   * Use the new repository signing key for the Debian/Ubuntu, Red
> >> Hat/CentOS, and OpenSUSE repositories
> >>   * Use acceptance test harness version as committed on the
> >> stable-2.235 branch
> >>
> >> We've been using the new repository signing keys with weekly
> >> builds for the last several months.  It is now time to switch to
> >> the new repository signing keys for the long term support releases.
> >>
> >> *Proposed steps:*
> >>
> >>   * Oliver Gondza approve the plan (as release officer)
> >>   * Mark Waite prepare a blog post announcing the change of
> >> repository signing keys and the steps administrators must take
> >> to install the new repository keys
> >>   * Mark Waite prepare the changelog and upgrade guide for Jenkins
> >> 2.235.3 with instructions for administrators to install the
> >> new repository keys
> >>   * Olivier Vernin and Mark Waite generate the 2.235.3 LTS build
> >> July 27, 28, or 29 using the core release automation based on
> >> the current contents of the stable-2.235 branch
> >>
> >> Comments, concerns, questions?
> >>
> >> Thanks,
> >> Mark Waite
> >>
> >> -- 
> >> 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/53818c9b-b9b6-462a-9dcf-9a320fed192en%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/CAH-3BictR95ZGdaFh%2BmXjXq_P9Ofx6e08A-icPmO4hXdz6pnkw%40mail.gmail.com
> >>  
> >> .
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Jenkins Developers" group.
> > To unsubscribe from this group and 

Re: Proposal: Jenkins CDF Graduation July 28th

['Olblak' via Jenkins Developers]

Well done Oleg, you did a really great work to have crystal clear and 
well-summarized answers to the various questions asked here and I am really 
happy that based on the questions asked you identified lack of 
documentation and addressed them.

On Thursday, 9 July 2020 at 23:07:38 UTC+2 Mark Waite wrote:

> I've reviewed the security checklist document and am ready to be a member 
> of the Jenkins bug triage team.
>
> As a Jenkins developer, I agree that we're read to send the official 
> graduation request to the CDF TOC.
>
> Mark Waite
>
> On Thursday, July 9, 2020 at 10:50:17 AM UTC-6 Oleg Nenashev wrote:
>
>> Hi all,
>>
>> Status update: We have completed the CDF Graduation checklist 
>> .IMHO
>>  
>> we are ready to proceed and initiate the graduation process on the 
>> Continuous Delivery Foundation side. 
>>
>> Status details:
>>
>>- Jenkins Code of Conduct was updated, and now it is compliant with 
>>CDF requirements: https://www.jenkins.io/project/conduct/
>>- A new listing of Jenkins adopters was introduced on jenkins.io:  
>>https://www.jenkins.io/project/adopters/
>>   - Please do not hesitate to submit pull requests and to add your 
>>   companies there!
>>- Jenkins Weekly Release line is now documented on jenkins.io:  
>>https://www.jenkins.io/download/weekly/
>>- Jenkins Main repository was updated to include references to all 
>>the pages above:  
>>https://github.com/jenkinsci/jenkins/blob/master/README.md
>>- The default Jenkins contributing template was updated by Tim 
>>Jacomb:  
>>https://github.com/jenkinsci/.github/blob/master/CONTRIBUTING.md. 
>>More contributions are always welcome!
>>- Core infrastructure Initiative checklist is in progress, but it is 
>>not a blocker for graduation
>>   - A Security Checklist has been submitted for review today. 
>>   Reviewers: Jenkins Security Team, Jenkins Infrastructure and 
>> Documentation 
>>   officers
>>   - We have an initial agreement about creating a Jenkins Bug Triage 
>>   Team, I will proceed with the implementation next week 
>>
>> If the Jenkins developers and board members agree, I will send an 
>> official request to CDF TOC on behalf of the Jenkins project. I would 
>> appreciate any feedback!
>>
>> Thanks in advance,
>> Oleg Nenashev
>>
>>
>> On Tue, Jun 16, 2020 at 11:17 PM Vlad Silverman  
>> wrote:
>>
>>> +1 from me on achieving CDF Graduation by July 28 based on listed 
>>> Criteria Checklist
>>>
>>> Thx, Vlad
>>>
>>> On Jun 12, 2020, at 6:43 AM, Oleg Nenashev  wrote:
>>>
>>> I have started a Google Doc with a checklist: 
>>> https://docs.google.com/document/d/1Ldmtny6OfEtQlCqdFWqq9Z25cxkZFX6yNiRqOOxo77c/edit?usp=sharing
>>> Please feel free to contribute and suggest changes!
>>>
>>> Best regards,
>>> Oleg
>>>
>>> On Friday, June 12, 2020 at 12:16:35 AM UTC+2, Marky Jackson wrote:

 +1 from me

 On Jun 11, 2020, at 2:39 PM, Tracy Miranda  
 wrote:

 All,

 Last year Jenkins became a CD.Foundation  
 project. The Technical Oversight Committee (TOC) of CDF set out a 
 project lifecycle 
 
  
 for projects as part of the governance model. CDF is proposing Jenkins be 
 the first project to go through the process and "graduate" i.e. 
 demonstrate 
 it has met the acceptance criteria 
 
 .

 Dan Lorenc, the current TOC Chair, joined the Jenkins Governance 
 meeting  this month for an overview of 
 the process and we had a discussion around the criteria. In short, there 
 are a few housekeeping things to do for Jenkins to graduate, and the 
 process has already been beneficial to the project health (e.g. helping 
 identify that we need to strengthen the triage team, update 
 Code-of-Conduct, etc). Project graduation will also be an opportunity to 
 promote the Jenkins project via CDF channels and highlight how the project 
 goes from strength to strength. 

 I would like to propose that the Jenkins Community commit to graduating 
 by the end of July, i.e. on July 28th 2020 at the CDF TOC meeting, we show 
 how we've met the criteria and ask for a vote. 

 (Note: this schedule allows CDF to graduate Jenkins as the first 
 project but also in a timely way so other CDF projects may also graduate 
 in 
 2020.)

 Please go ahead and vote/comment on this proposal.

 Regards,

 Tracy


 -- 
 You received this message because you are subscribed to the Google 
 Groups "Jenkins Developers" group.
 To unsubscribe from this group and 

Re: GitHub issues option in HOSTING

['Olblak' via Jenkins Developers]

Hi,

I think this mail discussion is a proof that we won't easily find a consensus 
any time soon.
I just want to add that we started discussing with Linux foundation infra team 
to see if they could maintained a managed version of Jira for us, more 
information in this email 
.

So please keep discussing about Jira and/or Github Issues here and things 
specific to how we maintain issues.jenkins-ci.org on the other thread.

Cheers 

On Fri, Jun 19, 2020, at 12:58 PM, Radosław Antoniuk wrote:
> On Fri, Jun 19, 2020 at 12:30 PM Tim Jacomb  wrote:
>> On Fri, 19 Jun 2020 at 10:36, Daniel Beck  wrote:
>>> Having a screen like 
>>> https://github.com/jenkinsci/configuration-as-code-plugin/issues/new/choose 
>>> could help here, but that's far from universal right now. Is this something 
>>> that could be defined via .github? Having a screen similar to this would be 
>>> the bare minimum for GH issue tracking already today.
>> 
>> Yes that is possible, I've just tested it out:
>> https://github.com/timja-org/.github/tree/master/.github/ISSUE_TEMPLATE
>> https://github.com/timja-org/jenkins-scripted-test/issues/new/choose
>> 
>> (I don't have the security file in my org but it would show up if it was 
>> configured)
> 
> Nice, exactly that.
> So, security report via a template, that auto-adds "security" label, that can 
> be pulled into (or referenced) a central security project.
> https://help.github.com/en/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository
> 
> 

> --
>  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/CAPe2pWgJKcz6nmLU9fR3-tYnrcermc%3DTNK7p9Et4LSA%2BmKtUYQ%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/016c48f3-1c26-4d43-9abb-897560659eab%40www.fastmail.com.

Re: ANN: Jenkins release artifacts uploads blockage on June 09, and a temporary downloads issue

['Olblak' via Jenkins Developers]

Hi Radek,

Thanks for your feedback

> PS. I am unable to reset my password on *Jira/accounts.jenkins.io* ATM - no 
> password reset email is coming to me.
If you send me your username and email address, I could have a look to it.

> I don't know what (tools/process) Linux Foundation is using
They are using https://identity.linuxfoundation.org/ and migrating to Auth0 but 
in both cases they allow you to use social accounts like Github

> - we need to know what are the limitations (would they allow for managing 
> groups for different access levels e.g. plugin maintainers vs infra 
> maintainers vs normal reporters)
This is something that need to be clarify indeed, as far as I understood it at 
the moment LF identity management can only be used for services that they 
manage on the opposite is true as well if we ask they to manage our Jira they 
will probably need to also manage the identity, but indeed this is something 
that need clarification.

Ps: We continued the discussion about keycloak on the jenkins infrastructure 
mailing list here 
<https://groups.google.com/d/msgid/jenkins-infra/CAO49JtFG1yAn6SJgFDb5b4fSF1fiGRM_s-bjhBnMVXczrMgY-w%40mail.gmail.com?utm_medium=email_source=footer>
 



On Thu, Jun 18, 2020, at 12:59 PM, Radosław Antoniuk wrote:
> On Thu, Jun 18, 2020 at 10:41 AM 'Olblak' via Jenkins Developers 
>  wrote:
>> Hi Everybody, 
>> 
>> Some updates regarding this topics, while almost everything is back to 
>> normal, we decided to not pursue with the "every user password reset" as we 
>> announced initially but instead we focused on maintainers and administrators 
>> access.
>> The reason for that is because we don't have ready to use tooling so it 
>> requires us to write custom scripts.
>> While we initially tried to go down that path, we reset +-30% of the 
>> database, we realized that because of the amount of garbage we have in that 
>> database, it was hard and time-consuming to finish this so we decided to 
>> look after alternatives for accounts.jenkins.io.
>> 
>> At the moment we have two promising alternatives:
>> 
>> Keycloak as a replacement for accounts.jenkins.io.
>> keycloak is an opensource identity management tool, which supports many 
>> integrations like Github SSO or LDAP.
>> It's deployed and only available from our VPN at the moment, configuration 
>> is defined here <https://github.com/jenkins-infra/charts/pull/256>.
>> It uses a RDS PostgreSQL database running on AWS and containers are running 
>> on our AKS cluster.
>> It was easy to deploy, configured, *seems* easy to maintain, and its 
>> database is running on a managed service.
>> It sounds very promising as it does exactly everything that 
>> accounts.jenkins.io do with a lot more like:
>> * Enforce email verification
>> * OTP 
>> * Safe reset password workflow 
>> * Using your social account like Github for login
>> * And many more
>> So we could stop losing our time patching our custom identity management 
>> tool.
>> 
>> The second option would be to totally or partially delegate identity 
>> management to the Linux Foundation infrastructure team.
>> We had a first exploratory meeting with them this week and we have another 
>> one planned next week
>> The whole idea is the vast majority of Jenkins account are used to 
>> report/update issues while the smallest amount of accounts are used by 
>> plugin maintainers (+-1700)and Jenkins administrators(+-20).
>> So if we can delegate the management of Jira to them, we wouldn't need to 
>> maintain an identity management tool anymore.
>> While implementation details still need to be discussed with them what seems 
>> to be clear at the moment are: 
>> * Identify management would be a black box, as it would also contain other 
>> Linux Foundation accounts.
>> * We could use it for Artifactory (repo.jenkins-ci.org) as they are already 
>> doing the same for other communities that they are managing.
>> While we would lose flexibility on this, we wouldn't have to maintain it or 
>> care about GDPR.
>> Therefore it will give us more time to focus on other initiatives.
>> 
>> If you have any advice, questions, concerns on this topic, feel free to 
>> raise them.
>> 
>> Thanks for your patience
>> 
>> Olivier
> 
> Hi Olivier,
> 
> Thanks a lot for thorough update, both options sound really interesting. 
> 
> I think it would be easier to rely on an external identity provider and each 
> of the Cloud providers now provide this (e.g. AWS SSO, Azure AD etc.). I 
> believe that most people using Jenkins have GH or FB accounts. Sounds like 
> this is 

Re: ANN: Jenkins release artifacts uploads blockage on June 09, and a temporary downloads issue

['Olblak' via Jenkins Developers]

Hi Everybody, 

Some updates regarding this topics, while almost everything is back to 
normal, we decided to not pursue with the "every user password reset" as we 
announced initially but instead we focused on maintainers and 
administrators access.
The reason for that is because we don't have ready to use tooling so it 
requires us to write custom scripts.
While we initially tried to go down that path, we reset +-30% of the 
database, we realized that because of the amount of garbage we have in that 
database, it was hard and time-consuming to finish this so we decided to 
look after alternatives for accounts.jenkins.io.

At the moment we have two promising alternatives:

Keycloak as a replacement for accounts.jenkins.io.
keycloak is an opensource identity management tool, which supports many 
integrations like Github SSO or LDAP.
It's deployed and only available from our VPN at the moment, configuration 
is defined here .
It uses a RDS PostgreSQL database running on AWS and containers are running 
on our AKS cluster.
It was easy to deploy, configured, *seems* easy to maintain, and its 
database is running on a managed service.
It sounds very promising as it does exactly everything that 
accounts.jenkins.io do with a lot more like:
* Enforce email verification
* OTP 
* Safe reset password workflow 
* Using your social account like Github for login
* And many more
So we could stop losing our time patching our custom identity management 
tool.

The second option would be to totally or partially delegate identity 
management to the Linux Foundation infrastructure team.
We had a first exploratory meeting with them this week and we have another 
one planned next week
The whole idea is the vast majority of Jenkins account are used to 
report/update issues while the smallest amount of accounts are used by 
plugin maintainers (+-1700)and Jenkins administrators(+-20).
So if we can delegate the management of Jira to them, we wouldn't need to 
maintain an identity management tool anymore.
While implementation details still need to be discussed with them what 
seems to be clear at the moment are: 
* Identify management would be a black box, as it would also contain other 
Linux Foundation accounts.
* We could use it for Artifactory (repo.jenkins-ci.org) as they are already 
doing the same for other communities that they are managing.
While we would lose flexibility on this, we wouldn't have to maintain it or 
care about GDPR.
Therefore it will give us more time to focus on other initiatives.

If you have any advice, questions, concerns on this topic, feel free to 
raise them.

Thanks for your patience

Olivier



On Wednesday, 17 June 2020 at 16:59:31 UTC+2 Oleg Nenashev wrote:

> Duly noted about the Documentation.
> I will migrate https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins to 
> jenkins.io and extend it to cover the use-case tonight
>
> On Wed, Jun 17, 2020 at 4:53 PM  wrote:
>
>> Hm, that does not work. I am using the Gradle JPI plugin. It does not 
>> seem to pick up ~/.m2/settings.xml nor ~/.jenkins-ci.org.
>>
>>
>> On June 17, 2020 at 15:52:17, Tim Jacomb (timja...@gmail.com) wrote:
>>
>> it's just the same as a password to maven, so use the api key instead of 
>> a password.
>>
>> On Wed, 17 Jun 2020 at 14:39,  wrote:
>>
>>> Hi,
>>>
>>> thanks for the advice. Hm, my ~/.m2/settings.xml had my encrypted 
>>> password. The docs (
>>> https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org)
>>>  
>>> don’t mention the API key. How can I configure Maven to use the API key 
>>> instead?
>>>
>>> Many thanks.
>>> Karsten.
>>>
>>>
>>> On June 17, 2020 at 14:53:22, Mark Waite (mark.ea...@gmail.com) wrote:
>>>
>>>
>>>
>>> On Wed, Jun 17, 2020 at 6:44 AM Karsten Jeschkies  
>>> wrote:
>>>
 Hi,

 thanks for you hard work. I reset my password successfully but cannot 
 upload a release for the Mesos plugin. Are releases still blocked?


>>> Releases are not blocked but a password reset will also reset your 
>>> password to the artifact repository.  If you're receiving an HTTP 401 when 
>>> you try to `mvn release perform` you may need to update your password in 
>>> the ~/.m2/settings.xml.
>>>
>>> I had to do that in order to release a new version of a plugin 
>>> yesterday.  I logged into the Jenkins Artifactory instance and had it 
>>> generate an encrypted password from my profile page on that server.  I 
>>> inserted that encrypted password into my ~/.m2/settings.xml file.  I'm not 
>>> sure if that is the preferred way to do it, but it worked for me.
>>>
>>> Mark Waite
>>>  
>>>
 Best.
 Karsten.

 On Tuesday, June 9, 2020 at 5:00:25 PM UTC+2, Oleg Nenashev wrote:
>
> Dear all,
>
> As you may have noticed, the release artifact uploads are currently 
> blocked in the Jenkins Artifactory instances (
> https://repo.jenkins-ci.org/). We are doing a security 

Re: Locked out of account

['Olblak' via Jenkins Developers]

Hi Matt,

I see that you account exist and it's using a major corporate domain name.
But it's not the same address that you are using here.

Could you send you me in private the first part (before @) of the email address

Maybe you changed your email address over the last months?



On Wed, Jun 17, 2020, at 12:55 PM, Matt Murphy wrote:
> I'm guessing my problem is related to the recent issues described in 
> https://groups.google.com/forum/#!msg/jenkinsci-dev/3UvrCTflXGk/gWT_tH7VAgAJ, 
> but I still do not have access to my account. My user name is mattmurp if 
> someone can please re-enable my account or reset my password, I would 
> appreciate it.
> 
> On Tuesday, June 16, 2020 at 4:25:44 PM UTC-4, Matt Murphy wrote:
>> Hi,
>> 
>> I cannot get into my account (password is not working), so I tried resetting 
>> it, but the email never comes. I've checked spam, etc. and it's not there. 
>> What's the process to unlock an account? I need to fix a plugin and publish 
>> a new version.
>> 
>> Thanks,
>> Matt
>> 
> 

> --
>  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/e21e1ab1-bf6c-4840-82b4-8a757d65d7f7o%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/2a47176c-1e8a-4fd3-a0ee-5a16cbaea532%40www.fastmail.com.

Re: ANN: Jenkins release artifacts uploads blockage on June 09, and a temporary downloads issue

['Olblak' via Jenkins Developers]

Dear all,

We are ready to proceed with restoration of the Jenkins account database. 
Today we are going to restore user LDAP accounts that were created since 
the First of February 2020 based on the data from Jenkins Jira and the 
repository Permission Manager metadata data. We will also reset passwords 
for all users registered in the database.

Step 1. All users who lost their account will receive an email saying that 
their accounts were re-created. There will be no temporary password in 
these emails, but there will be information pointing to this thread.

Step 2. We’ll reset every user password from the LDAP database, it is more 
than 100 000 users. Once done, you’ll receive an email telling you that 
your password was reset with a reason containing a link to this mail thread.

Step 3. We will delete accounts of users who requested such deletion 
between February and June 2020. These users were restored from the backup, 
so we have to delete them again.The list of users is based on Jira tickets 
and private messages to the Jenkins Infra officer. If for some reason you 
notice that your account still exists, feel free to raise a ticket in Jenkins 
Jira  (project=INFRA, component=account).

Please do not hesitate to contact us using the #jenkins-infra channel on 
Freenode IRC or the Jenkins Infrastructure mailing list if you have any 
questions or suggestions. If you see a security issue related to the 
accounts, please follow the vulnerability reporting guidelines 
.

Best regards,

Olivier Vernin && Jenkins Infrastructure Team


On Tuesday, 9 June 2020 17:00:25 UTC+2, Oleg Nenashev wrote:
>
> Dear all,
>
> As you may have noticed, the release artifact uploads are currently 
> blocked in the Jenkins Artifactory instances (https://repo.jenkins-ci.org/). 
> We are doing a security investigation due to a partial user database loss 
> on June 02. Today we blocked releases to the Jenkins artifactory, and there 
> also was a temporary outage of the Artifactory downloads which was a 
> collateral damage of the temporary permissions. You can find more details 
> about it in this Jenkins Infra Thread 
>  and 
> in this Dev List thread 
> .
>
> Current status:
>
>- 
>
>Downloads are restored for all artifacts on 
>https://repo.jenkins-ci.org/, Jenkins core historical releases, 
>Remoting library and Windows Service Wrapper which were among ones 
> reported 
>by Jenkins users.
>- 
>
>Uploads: Jenkins artifact uploads are blocked for the most of Jenkins 
>plugin maintainers and contributors. It affects releases of Jenkins 
>plugins, Jenkins core and modules, developer tools and all libraries 
> hosted 
>on https://repo.jenkins-ci.org/. Incremental and Snapshot deployments 
>are not affected.
>
>
> Quick summary: 
>
>- 
>
>Jun 02 - There was a Kubernetes Cluster outage on June 02. During this 
>outage we had to rebuild the cluster from scratch to get some services 
>working again.
>- 
>
>Jun 02 - After the recovery we lost three months of LDAP changes. It 
>has happened due to the broken backup of the LDAP database.
>- 
>
>Jun 02 - We identified a number of potential security risks which may 
>be caused by the LDAP outage. Account overtake and malicious upload was 
> one 
>of the identified risks. FTR this issue is tracked as SECURITY-1895 as a 
>follow-up to these discussions. Only the Security team members have access 
>to it, so I am not sharing a link here.
>- 
>
>Jun 09 - After the security risk was independently reported in public 
>by a plugin maintainer in the dev list thread 
>, we decided 
>to block uploads of release artifacts to the Jenkins Artifactory instance.
>- 
>
>Jun 09, 8:50AM UTC - All uploads of release artifacts were blocked 
>(plugins, Jenkins core and modules, developer tools, etc.). Downloads of 
>some binaries were also blocked as an unexpected collateral damage. 
> Jenkins 
>core historical releases, Remoting library and Windows Service Wrapper are 
>among the affected binaries
>- 
>
>Jun 09, 10AM UTC - We finished reviews of all artifact releases to 
>https://repo.jenkins-ci.org/, which happened between the infra outage 
>on June 02 and the blockage of the releases. There are no maliciously 
>uploaded artifacts. Note that the common plugin release flow requires 
>access to GitHub in order to push the release commits, so a malicious 
>attacker would need to overtake both Jenkins and GitHub accounts of a 
>single user to submit a legitimately-looking release.
>- 
>
>Jun 09, ~1PM UTC - 

Re: Jenkins Jira restart today at 10PM UTC

['Olblak' via Jenkins Developers]

Thanks Mark for taking care of this. 

On Thu, Jun 4, 2020, at 8:44 PM, Mark Waite wrote:
> The Jenkins Jira instance is having disc space issues that appear to be best 
> solved by restarting the service.
> 
> I'll stop the Jira service at 22:00 UTC today (about 3 hours from now), June 
> 4, 2020. I hope to keep the down time to less than 30 minutes.
> 
> Reply to me if that downtime will cause a critical issue for you.
> 
> Thanks,
> Mark Waite
> 

> --
>  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/CAO49JtHh5%3DiwN5mDz4jqkbcw4yFtdqjOCydpos2w4vNv49pFdw%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/2b33b9ae-6a63-4287-813d-7f558f81250e%40www.fastmail.com.

Re: accounts.jenkins.io can't login or use password reset

['Olblak' via Jenkins Developers]

> If that account is not in current db, can we re-register providing the same 
> id?
Yes you can, in your case I see that there is already account in the database

On Thu, Jun 4, 2020, at 10:19 AM, Michał Malicki wrote:
> Hi Oleg,
> I have similiar situation, can't log in into account with id "deviniti". I'd 
> appreciate if you could try to reset that one as well.
> If that account is not in current db, can we re-register providing the same 
> id?
> Regards,
> Michał
> 
> On Wednesday, June 3, 2020 at 6:56:59 PM UTC+2, Oleg Nenashev wrote:
>> Hi Johan,
>> 
>> This is related to the yesterday's INFRA outage: 
>> https://groups.google.com/forum/#!topic/jenkins-infra/zRqdiyarLDE . " Ldap 
>> database backup stopped in February 2020 which means that we lost three 
>> months of ldap changes.". We restored the latest available backup, so recent 
>> changes are lost. We are looking into possible options to fully or partially 
>> restore the changes, but no good news right now. 
>> 
>> If you provide your account ID, I will try to reset it manually. If you have 
>> registered less than 3 months ago, then you may need to re-register
>> 
>> Best regards,
>> Oleg
>> 
>> On Wednesday, June 3, 2020 at 5:30:10 PM UTC+2, Johan Cornelissen wrote:
>>> Up until two days ago I was able to log into Jenkins LDAP without issues.
>>> Now if I try to login it says invalid password, and a password reset 
>>> attempt on https://accounts.jenkins.io/ isn't working (I receive no email, 
>>> even though password resets have worked for me in the past).
>>> 
>>> Could someone help take a look? I'll send my username privately.
> 

> --
>  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/91df7050-6b00-41c2-8354-520370d16caf%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/4615f0c4-83b7-435e-b0b5-e4ed070eeb42%40www.fastmail.com.

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

['Olblak' via Jenkins Developers]

+1 

On Wed, May 20, 2020, at 5:10 PM, Tim Jacomb wrote:
> +1000
> 
> On Wed, 20 May 2020 at 14:51, Mark Waite  wrote:
>> +1 from me.
>> 
>> On Wed, May 20, 2020 at 7:38 AM Oleg Nenashev  wrote:
>>> Hi all,
>>> 
>>> I am working on a repository for the UI/UX online hackfest 
>>>  next week. This 
>>> repository would be used for tracking and visualizing contributions during 
>>> the Hackfest, with help from the All Contributors 
>>>  GitHub App and additional tooling. 
>>> Work-in-progress repository draft: 
>>> https://github.com/oleg-nenashev/jenkins-uiux-hackfest-2020
>>> 
>>> I would like to have this repository hosted within the jenkinsci 
>>>  GitHub organization so that it is a part of 
>>> the Jenkins project. All Contributors app is already installed for the 
>>> organization. Would everyone be fine with moving the repo to our GitHub org?
>>> 
>>> Thanks in advance,
>>> Oleg
>>> 
>>> P.S: I have added this subject to the today's Governance meeting agenda
>>> 
>>> 

>>> --
>>>  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/CAPfivLBEnyjwQj9%2BFZkfq3m2tNy_SV4Ww%2Bc5j6i6hvR6C9R54g%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/CAO49JtFmf1OqS7ED1T23vO3PZ4SO8E_v0NkHi6EZQ-CPmMy2pg%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/CAH-3BicK9Y6B9s%3DkB_evXaB-4bC9QPMrKLOKXMF-50rgOMVN9Q%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/b4ff3c1d-9bb4-40f8-a123-30e14f2ff0e8%40www.fastmail.com.