Re: Migration path to spring security with credentials plugin UI

['Gavin Mogan' via Jenkins Developers]

I think there's helper functions for this

I want to say

https://github.com/search?q=org%3Ajenkinsci+StandardListBoxModel=code
https://github.com/jenkinsci/huaweicloud-mastermonitor-plugin/blob/b96e0fb3649dfbd69e0f0a2184c4d66c232af57c/src/main/java/com/huawei/devcloud/global_configuration/DevCloudGlobalConfiguration.java#L117

might help out a bit?

On Mon, Sep 27, 2021 at 4:21 PM Tim Van Holder 
wrote:

> Hi,
>
> I'm looking at bumping my plugin from Jenkins 249.1 to 289.1 (plus
> plugin-parent from 4.19 to 4.27 and the BOM from 2.249.x/887.vae9c8ac09ff7
> to 2.289.x/950.v396cb834de1).
>
> This all works fine, except I get a warning about deprecated code.
>
> I have a helper method to populate a list box (a ) with string
> credentials (NuGet API keys).
> These will be used on configuration for build steps (both via the classic
> job UI, and via the snippet generator for use in pipelines).
>
> @NonNull
> static ListBoxModel getStringCredentialsList(@CheckForNull Jenkins context, 
> boolean allowEmpty) {
>   AbstractIdCredentialsListBoxModel StandardCredentials> model = new StandardListBoxModel();
>   if (allowEmpty) {
> model = model.includeEmptyValue();
>   }
>   if (context == null || !context.hasPermission(CredentialsProvider.VIEW)) {
> return model;
>   }
>   model = model.includeMatchingAs(ACL.SYSTEM, context, 
> StringCredentials.class, Collections.emptyList(), 
> CredentialsMatchers.always());
>   return model;
> }
>
>
> While ACL.SYSTEM says to use ACL.SYSTEM2 instead, that is of a different
> type, and there are no overloads on the list box model that accept it.
>
> So I have two questions:
> 1) Was this the correct way of doing this to begin with, or should I have
> been getting a user-specific credential list?
> 2) What is the new way of doing this, using the Spring Security types? I
> don't see any use of the spring security packages, so I guess the
> credentials plugin just hasn't been updated yet?
>
> --
> 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/CAKMi--BpJWaeY-4Ghf4coF6RuTMJjpnLJXSWcCkSxh1wf%2BygaA%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_DuuWqhhnWU2DOc22dpM0ofQALgaT3p9h5mGxzdH8CzXkAQ%40mail.gmail.com.

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

['Gavin Mogan' via Jenkins Developers]

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 <
>> wfollon...@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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CACmp6kpV8vE-8C%3D7mAE3DgcAA3O84Fgyqg0CpXUPCq5-CrZxpw%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/CANWgJS6ReuCQTxfcw52pEYL8PK-mB8rXdREAe5uywrwT%2B6HCCA%40mail.gmail.com
> 
> .
>

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

Migration path to spring security with credentials plugin UI

[Tim Van Holder]

Hi,

I'm looking at bumping my plugin from Jenkins 249.1 to 289.1 (plus
plugin-parent from 4.19 to 4.27 and the BOM from 2.249.x/887.vae9c8ac09ff7
to 2.289.x/950.v396cb834de1).

This all works fine, except I get a warning about deprecated code.

I have a helper method to populate a list box (a ) with string
credentials (NuGet API keys).
These will be used on configuration for build steps (both via the classic
job UI, and via the snippet generator for use in pipelines).

@NonNull
static ListBoxModel getStringCredentialsList(@CheckForNull Jenkins
context, boolean allowEmpty) {
  AbstractIdCredentialsListBoxModel model = new StandardListBoxModel();
  if (allowEmpty) {
model = model.includeEmptyValue();
  }
  if (context == null || !context.hasPermission(CredentialsProvider.VIEW)) {
return model;
  }
  model = model.includeMatchingAs(ACL.SYSTEM, context,
StringCredentials.class, Collections.emptyList(),
CredentialsMatchers.always());
  return model;
}


While ACL.SYSTEM says to use ACL.SYSTEM2 instead, that is of a different
type, and there are no overloads on the list box model that accept it.

So I have two questions:
1) Was this the correct way of doing this to begin with, or should I have
been getting a user-specific credential list?
2) What is the new way of doing this, using the Spring Security types? I
don't see any use of the spring security packages, so I guess the
credentials plugin just hasn't been updated yet?

-- 
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/CAKMi--BpJWaeY-4Ghf4coF6RuTMJjpnLJXSWcCkSxh1wf%2BygaA%40mail.gmail.com.

Re: Safe ways to handle extraction of features into new plugins

['Jesse Glick' via Jenkins Developers]

On Mon, Sep 27, 2021 at 7:18 AM Chris Kilding <
chris+jenk...@chriskilding.com> wrote:

> some 3rd party Jenkins management tools […] do not download transitive
> plugin dependencies when they install a plugin.
>

So fix them, or advise your users to avoid them?

-- 
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/CANfRfr1U_%2BgmS7Sx2rAZs2KhYqrhh%3D42R-aexCJPffc3pUPmuQ%40mail.gmail.com.

Re: Safe ways to handle extraction of features into new plugins

['Daniel Beck' via Jenkins Developers]

On Mon, Sep 27, 2021 at 1:53 PM Chris Kilding <
chris+jenk...@chriskilding.com> wrote:

> As long as both extracting a feature and adding a feature with a
> dependency would cause Jenkins to stop with an early initialisation error,
> so that the admin knows they've got to go and install the extra dependency,
> then yes I'd see them as equivalent.
>

Jenkins is more tolerant than that, but it will log errors and show admin
monitors about failed plugins in both cases.

-- 
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/CAMo7Pt%2BN_6qyaSxnphr%2Bptd_%3D4z1%3DKjGuDibf8-kT3fD33DXpg%40mail.gmail.com.

Re: Safe ways to handle extraction of features into new plugins

[Chris Kilding]

As long as both extracting a feature and adding a feature with a dependency 
would cause Jenkins to stop with an early initialisation error, so that the 
admin knows they've got to go and install the extra dependency, then yes I'd 
see them as equivalent.

Chris

On Mon, 27 Sep 2021, at 12:28 PM, 'Daniel Beck' via Jenkins Developers wrote:
> 
> 
> On Mon, Sep 27, 2021 at 1:17 PM Chris Kilding  > wrote:
>> However there is a problem that some 3rd party Jenkins management tools 
>> (i.e. not Jenkins' own tools like Plugin Installation Manager CLI) do not 
>> download transitive plugin dependencies when they install a plugin.
>> 
>> …
>> 
>> These tools usually offer plugin version pinning which mitigates the worst 
>> effects. However it would seem that as soon as step 3 happens and the 
>> Jenkins admin updates A, the extracted feature effectively disappears on 
>> their installation, unless they have somehow learned that they should also 
>> install B.
> 
> This doesn't seem any different from adding a new feature or integration to a 
> plugin with a new, non-optional dependency on another plugin, or is it? If 
> you plugin fails to load because of an unsatisfied dependency, it doesn't 
> matter whether the feature's code is present or not.
> 
> 
> -- 
> 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/CAMo7PtJNOjyCB4T1RTq%3DGNE4GaW_uk7-6JXBUGh-MKB8W5DfUQ%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/07f734d8-9591-4885-9b99-f5d7fedea0e0%40www.fastmail.com.

Re: Safe ways to handle extraction of features into new plugins

['Daniel Beck' via Jenkins Developers]

On Mon, Sep 27, 2021 at 1:17 PM Chris Kilding <
chris+jenk...@chriskilding.com> wrote:

> However there is a problem that some 3rd party Jenkins management tools
> (i.e. not Jenkins' own tools like Plugin Installation Manager CLI) do not
> download transitive plugin dependencies when they install a plugin.
>
> …
>
> These tools usually offer plugin version pinning which mitigates the worst
> effects. However it would seem that as soon as step 3 happens and the
> Jenkins admin updates A, the extracted feature effectively disappears on
> their installation, unless they have somehow learned that they should also
> install B.


This doesn't seem any different from adding a new feature or integration to
a plugin with a new, non-optional dependency on another plugin, or is it?
If you plugin fails to load because of an unsatisfied dependency, it
doesn't matter whether the feature's code is present or not.

-- 
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/CAMo7PtJNOjyCB4T1RTq%3DGNE4GaW_uk7-6JXBUGh-MKB8W5DfUQ%40mail.gmail.com.

Safe ways to handle extraction of features into new plugins

[Chris Kilding]

Hi,

I'm wondering what techniques people have used to safely extract features from 
existing plugins into new plugins.

At first glance a phased approach intuitively makes sense:

1. Plugin A exists.
2. Extract feature from A into new plugin B. Release B.
3. Delete feature code from A. Make A depend on B (to transitively inherit the 
feature). Release A.
4. Wait a while for adoption of new A version.
5. Remove the B dependency from A. Release A.

However there is a problem that some 3rd party Jenkins management tools (i.e. 
not Jenkins' own tools like Plugin Installation Manager CLI) do not download 
transitive plugin dependencies when they install a plugin.

One such example is the Puppet Jenkins module: 
https://forge.puppet.com/modules/puppet/jenkins#plugin-dependencies

These tools usually offer plugin version pinning which mitigates the worst 
effects. However it would seem that as soon as step 3 happens and the Jenkins 
admin updates A, the extracted feature effectively disappears on their 
installation, unless they have somehow learned that they should also install B. 
So for this group of users there is no phased migration.

(Yes, Jenkins admins using these tools *should* run a non-production copy of 
Jenkins to test their changes before deploying, and yes they *should* read 
release notes before incrementing any plugin version... but this doesn't always 
happen.)

Do we consider these use cases when extracting features? If so do we employ any 
techniques to help e.g. major version increments?

Chris

-- 
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/e6a5d416-2e75-447a-bdf0-d807ce4b8096%40www.fastmail.com.

Re: Release team members

[raihaan...@gmail.com]

+1 I'd be happy to help where I can

On Monday, 27 September 2021 at 17:16:55 UTC+8 timja...@gmail.com wrote:

> Thanks all.
>
> I've added it to the people who have replied so far:
>
> [image: image.png]
>
> Cheers
> Tim
>
> On Mon, 27 Sept 2021 at 07:52, 'wfoll...@cloudbees.com' via Jenkins 
> Developers  wrote:
>
>> Good initiative Tim, thank you :) 
>>
>> (yes you can add me ^^)
>>
>> Wadeck
>>
>> On Friday, September 24, 2021 at 9:52:30 AM UTC+2 Ildefonso Montero wrote:
>>
>>> No issues from my side :-) Thanks for driving this Tim!
>>>
>>> On Thu, Sep 23, 2021 at 9:29 PM Mark Waite  wrote:
>>>
 I would like to be a member of that group.

 On Wed, Sep 22, 2021 at 11:49 PM 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:
>
>
>- 
>
>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-de...@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-de...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFtg4-tYwuqB%3DqnA0tvR4MDiL2j%3D_QhaFHtnC8%3DrCmHPQ%40mail.gmail.com
  
 
 .

>>>
>>>
>>> -- 
>>>
>>> Ildefonso Montero Pérez
>>> Senior Software Engineer
>>>
>>> CloudBees, Inc
>>>
>>>
>>>
>>> E: imon...@cloudbees.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/2bda6d62-3252-4bb7-97fc-29980ed32465n%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/ef8366d6-d4eb-41f2-a638-8505034e0390n%40googlegroups.com.

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

[Baptiste Mathus]

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 <
> wfollon...@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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CACmp6kpV8vE-8C%3D7mAE3DgcAA3O84Fgyqg0CpXUPCq5-CrZxpw%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/CANWgJS6ReuCQTxfcw52pEYL8PK-mB8rXdREAe5uywrwT%2B6HCCA%40mail.gmail.com.

Re: Release team

[Tim Jacomb]

Thanks Daniel, I've sorted the jenkinsci side out

On Mon, 27 Sept 2021 at 10:13, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
>
> On Mon, Sep 27, 2021 at 10:07 AM Tim Jacomb  wrote:
>
>> Can someone create the GitHub team please and make me maintainer?
>>
>
> Do it yourself? :P
>
>
> (FTR I made Tim an owner of jenkinsci, seemed silly for him not to be.)
>
> --
> 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/CAMo7PtKynibnpJo4GWZYW2h1b%3DQ%3DgJuABRybDz6%3D%2Bv1%2BsLy5bQ%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-3BidFX9o2MyDG9eWLUfifEUtZDt1izC_6K0si_ELKK6_1Dw%40mail.gmail.com.

Re: Release team members

[Tim Jacomb]

Thanks all.

I've added it to the people who have replied so far:

[image: image.png]

Cheers
Tim

On Mon, 27 Sept 2021 at 07:52, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> Good initiative Tim, thank you :)
>
> (yes you can add me ^^)
>
> Wadeck
>
> On Friday, September 24, 2021 at 9:52:30 AM UTC+2 Ildefonso Montero wrote:
>
>> No issues from my side :-) Thanks for driving this Tim!
>>
>> On Thu, Sep 23, 2021 at 9:29 PM Mark Waite  wrote:
>>
>>> I would like to be a member of that group.
>>>
>>> On Wed, Sep 22, 2021 at 11:49 PM 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:


-

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-de...@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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFtg4-tYwuqB%3DqnA0tvR4MDiL2j%3D_QhaFHtnC8%3DrCmHPQ%40mail.gmail.com
>>> 
>>> .
>>>
>>
>>
>> --
>>
>> Ildefonso Montero Pérez
>> Senior Software Engineer
>>
>> CloudBees, Inc
>>
>>
>>
>> E: imon...@cloudbees.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/2bda6d62-3252-4bb7-97fc-29980ed32465n%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-3BifnZQdwW5pQt-aPEGtvTeQmPn7EAOes2xdd%2Brs4HTad8w%40mail.gmail.com.

Re: Release team

['Daniel Beck' via Jenkins Developers]

On Mon, Sep 27, 2021 at 10:07 AM Tim Jacomb  wrote:

> Can someone create the GitHub team please and make me maintainer?
>

Do it yourself? :P


(FTR I made Tim an owner of jenkinsci, seemed silly for him not to be.)

-- 
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/CAMo7PtKynibnpJo4GWZYW2h1b%3DQ%3DgJuABRybDz6%3D%2Bv1%2BsLy5bQ%40mail.gmail.com.

Re: Release team

[Tim Jacomb]

Can someone create the GitHub team please and make me maintainer?

On Wed, 22 Sept 2021 at 10:07, Oleg Nenashev  wrote:

> +1 from me. I will implement the Jenkinsci GitHub repo part it tomorrow if
> no negative feedback
>
> On Tuesday, September 21, 2021 at 8:43:51 PM UTC+2 ullrich...@gmail.com
> wrote:
>
>> +1
>>
>> Am 21.09.2021 um 11:32 schrieb Tim Jacomb :
>>
>> Hello
>>
>> I would like to propose a release team in the Jenkins GitHub org.
>> The role and permissions are documented in
>> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles
>> but they don’t actually exist in the jenkinsci GitHub org.
>>
>> In jenkins-infra we have a release team which current has:
>>
>>- Mark Waite
>>- Daniel Beck
>>- Olivier Vernin
>>- Wadeck Follonier
>>- Oleg Nenashev
>>- Myself
>>
>>
>> I would like to have a release team in JenkinsCI that has write
>> permissions on jenkinsci/jenkins and jenkinsci/packaging created, with
>> myself (release officer) as the maintainer of the team.
>>
>> I’ll post a list proposing people separately if people are happy with
>> this idea.
>>
>> People gaining core access here should be using their permissions for
>> release activities, e.g. backporting, build fixes.
>>
>> Ideally the jenkinsci/jenkins-infra teams should be synced as well, this
>> would grant write access to the ‘jenkins-infra/release’ repository, which
>> will be helpful for:
>>
>>- Any release team member will be able to update the release checklist
>>- Merging of PRs updating next release version / stable line
>>
>>
>> The people joining the team should also be either (thoughts?):
>>
>>1. Added to the LDAP group ‘release-core’
>>2. Join the LDAP group when acting as a release lead and be removed
>>after
>>
>>
>> Any feedback?
>>
>> Thanks
>> Tim
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic1AHThGLJoR%2Bb3bP1pKZHDZTDePOE1p3CAx%2B7aa_qCew%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/54eda6f0-43d7-4962-9685-32b3c01392a4n%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-3BifStdUGSu-RY5xVBS3iNuo6U-i49a3u7mRcPNwcxtez6w%40mail.gmail.com.

Re: Plugin Adoption Request: subversion-plugin

[Tim Jacomb]

Hello

As this is up for adoption we can proceed straight away.
Please send a PR to
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-subversion.yml

Thanks
Tim

On Mon, 27 Sept 2021 at 08:35, Diego Diez  wrote:

> Hi, I would like to adopt the subversion plugin
>
> Plugin: https://github.com/jenkinsci/subversion-plugin
> PR: https://github.com/jenkinsci/subversion-plugin/pull/262
> GitHub username: *didiez* https://github.com/didiez
> Jenkins infra User ID: *didiez*
>
> Thanks!
> Diego
>
> --
> 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/CAGsgRRVqZH8QDJ4ZxQTvZngrE687yHwd-_mVRTKdbGgeVNh%3DMQ%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-3BieC3nYBBzVOaOv_JVwtV96UEr8NpS%2BPH8ARyGDkROtmqg%40mail.gmail.com.

Plugin Adoption Request: subversion-plugin

[Diego Diez]

Hi, I would like to adopt the subversion plugin

Plugin: https://github.com/jenkinsci/subversion-plugin
PR: https://github.com/jenkinsci/subversion-plugin/pull/262
GitHub username: *didiez* https://github.com/didiez
Jenkins infra User ID: *didiez*

Thanks!
Diego

-- 
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/CAGsgRRVqZH8QDJ4ZxQTvZngrE687yHwd-_mVRTKdbGgeVNh%3DMQ%40mail.gmail.com.

Re: Release team members

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

Good initiative Tim, thank you :) 

(yes you can add me ^^)

Wadeck

On Friday, September 24, 2021 at 9:52:30 AM UTC+2 Ildefonso Montero wrote:

> No issues from my side :-) Thanks for driving this Tim!
>
> On Thu, Sep 23, 2021 at 9:29 PM Mark Waite  wrote:
>
>> I would like to be a member of that group.
>>
>> On Wed, Sep 22, 2021 at 11:49 PM 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:
>>>
>>>
>>>- 
>>>
>>>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-de...@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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFtg4-tYwuqB%3DqnA0tvR4MDiL2j%3D_QhaFHtnC8%3DrCmHPQ%40mail.gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
>
> Ildefonso Montero Pérez
> Senior Software Engineer
>
> CloudBees, Inc
>
>
>
> E: imon...@cloudbees.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/2bda6d62-3252-4bb7-97fc-29980ed32465n%40googlegroups.com.