Re: Proposal: Remove inactive core-pr-reviewers from the team

[Mark Waite]

On Monday, February 19, 2024 at 1:18:57 PM UTC-7 Alexander Brandes wrote:

Hey everyone,

While onboarding Stefan Spieker into the core-pr-reviewers team 
, I noticed a 
plenty of inactive members in the team, who haven’t engaged with core in 
years.

The team grants triage permission to set labels and update changelog 
entries in Jenkins core and is largely used for notifications in core PRs 
directly.
To maintain an active team, whose members actively engage with core PRs and 
respond to requested reviews, I would propose to remove team members, who 
have not interacted with core within one year.


I am +1 for the idea of removing individuals from the team who have not 
interacted with core in a year or more.

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/95cb3942-cb7f-4179-90cd-01a6345afea9n%40googlegroups.com.

Proposal: Remove inactive core-pr-reviewers from the team

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

While onboarding Stefan Spieker into the core-pr-reviewers team 
, I noticed a plenty 
of inactive members in the team, who haven’t engaged with core in years.

The team grants triage permission to set labels and update changelog entries in 
Jenkins core and is largely used for notifications in core PRs directly.
To maintain an active team, whose members actively engage with core PRs and 
respond to requested reviews, I would propose to remove team members, who have 
not interacted with core within one year.

Access can easily be restored with minimal inconvenience if someone chooses to 
return.

Best,
Alex

-- 
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/4CCF1196-C57F-49A4-919E-54E16E15AA2D%40notmyfault.dev.

Re: Proposal: Stefan Spieker to join the core PR reviewers team

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

During today’s governance board meeting, Ulli agreed alongside Basil, Mark and 
me to Stefan’s addition, according to the ladder outlined in the Maintainers 
doc: 
https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#ladder

Welcome aboard, Stefan :)

> On 19. Feb 2024, at 13:49, Kris Stern  wrote:
> 
> +1
> From: jenkinsci-dev@googlegroups.com  on 
> behalf of Basil Crow 
> Sent: 19 February 2024 05:10
> To: jenkinsci-dev@googlegroups.com 
> Subject: Re: Proposal: Stefan Spieker to join the core PR reviewers team
>  
> +1
> 
> On Sun, Feb 18, 2024 at 10:07 PM Mark Waite  > wrote:
> 
> 
> On Sunday, February 18, 2024 at 9:30:35 AM UTC-7 Alexander Brandes wrote:
> Hey everyone,
> 
> I would like to propose Stefan Spieker (@StefanSpieker 
> ) to join the core PR reviewers team.
> 
> Stefan has been a core contributor since October 2022, and filed 172 
>  
> pull requests, where 171 PRs have been merged.
> Additionally, he has been active in reviewing core PRs and has voiced his 
> opinion in almost 300 
> 
>  pull requests.
> 
> I would welcome him as an addition to the core pr team :)
> 
> +1 from me.
> 
> 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/28e931e5-26e9-47c4-80c7-87871a4a929en%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/CAFwNDjrpBy1cWe%3DXGyhub1jKnExrd-Zr6GD%3Dn2KT3ObvgTRTBg%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/TY1P286MB31711224BADB05E5E0D8F882A1512%40TY1P286MB3171.JPNP286.PROD.OUTLOOK.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/346A81EF-4657-4A22-8B7B-C3C46B70A5B2%40notmyfault.dev.

Re: February 19, 2024 Governance Board Agenda

['Gavin Mogan' via Jenkins Developers]

If Jenkins needs more AI processing, Digital Ocean (sponsor) has
https://www.digitalocean.com/products/paperspace

Would recommend the super long running issues (eg, retiring chinese site)
gets broken up into issues somewhere so multiple people can work on it, I
know there's some super enthusiastic students looking to help out.

On Mon, Feb 19, 2024 at 9:19 AM Mark Waite 
wrote:

> The Jenkins board meeting starts at 7:00 PM UTC (about 6 hours from now).
> Zoom  link is
> https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09
>
> Here is the draft agenda:
>
> News
>
>- Ampere Computing  has lent 2 servers
>to the Jenkins project
>   - Special thanks
>  - Bruno Verachten arranged the loan to the Jenkins project
>  - Aaron Williams
>   arranged the
>  loan from Ampere Computing
>  - Mark Waite is hosting the machines at his house (donating
>  electricity and networking)
>  - CloudBees will be asked to donate disc drives and other
>  components as needed
>   - Next generation of the Jenkins project involvement with ARM64
>  - Oracle Cloud confirmed in 2021
>  
> 
>  that
>  Jenkins works well with ARM64
>  - Jenkins infrastructure continues transition to ARM64 servers
>  
> 
>
> Action Items
>
>- Basil create the attribution entries for the downloads page
>   - Jenkins sponsors have changed
>  - DigitalOcean donated over $20k USD last year and has donated
>  $20k in 2024
>  - AWS donation request has been submitted. Answer in 30 days. If
>  no donation, then should remove AWS from root page
>  
>   - Kevin Martens retire the Chinese Jenkins site
>   - Mark needs to do more Kubernetes setup, then Kevin and Mark will
>   meet with Damien
>   - More work after FOSDEM
>- Stefan Spieker to join the core-pr-reviewer team:
>https://groups.google.com/g/jenkinsci-dev/c/Wkhrs3nNEEU @NotMyFault
>
>   - Per the maintainer's doc, the board can vote on the decision:
>   
> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#ladder
>   - @NotMyFault  is in favor, he has
>   been a great help reviewing core PRs and contributing to core before
>   - @MarkEWaite is in favor
>   - @basil is in favor
>
> Community
> activity
>
>- Contributor summit results
>   - Slides
>   
> 
>  from
>   the summit
>   - @kmartens27 preparing a summary blog post
>   - @MarkEWaite extend the Java 2+2+2 support plan JEP
>    with results from summit
>- Java 11, 17, and 21 in Jenkins - Mark Waite
>   - Contributor summit provided additional information
>  - HPI plugin has been extended to prepare for Java 11 end of
>  life - PR-578
>   from
>  Vincent Latombe
> - HPI plugin not yet released with the change
>  - 2+2+2 Java support plan - Jenkins enhancement proposal
>   
> 
>submitted
>  - Include the steps of the Java migration as part of the JEP
>  (work estimate, tasks, etc.)
> - Mark has much more work to do here
>- Dropping support for a Java version (refer to Java 11
>for ideas)
>- Adding a Java version (use Java 21 addition as the
>pattern)
>- Making a Java version the recommended version (use Java
>17 as the pattern)
> - Further refinements to be done in the JEP
>  - Key dates
>  - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
>  - Oct 30, 2024 - First Jenkins LTS to require Java 17
>  - Oct 31, 2024 - end of Java 11 support by Jenkins project
>
> Governance
> Topics
>
>- Jenkins awards - Mark Waite
>   - Nominations close today, 19 Feb 2024
>   - Overview of the Jenkins awards
>  - CDF hosts the nominations
>  - Most valuable advocate
>   -
>  speaking, promoting, training, 

February 19, 2024 Governance Board Agenda

[Mark Waite]

The Jenkins board meeting starts at 7:00 PM UTC (about 6 hours from now).  
Zoom  link is 
https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09 

Here is the draft agenda: 

News

   - Ampere Computing  has lent 2 servers to 
   the Jenkins project
  - Special thanks
 - Bruno Verachten arranged the loan to the Jenkins project
 - Aaron Williams  
arranged 
 the loan from Ampere Computing
 - Mark Waite is hosting the machines at his house (donating 
 electricity and networking)
 - CloudBees will be asked to donate disc drives and other 
 components as needed
  - Next generation of the Jenkins project involvement with ARM64
 - Oracle Cloud confirmed in 2021 
 

 that 
 Jenkins works well with ARM64
 - Jenkins infrastructure continues transition to ARM64 servers 
 

  
Action Items
   
   - Basil create the attribution entries for the downloads page
  - Jenkins sponsors have changed
 - DigitalOcean donated over $20k USD last year and has donated 
 $20k in 2024
 - AWS donation request has been submitted. Answer in 30 days. If 
 no donation, then should remove AWS from root page 
 
  - Kevin Martens retire the Chinese Jenkins site
  - Mark needs to do more Kubernetes setup, then Kevin and Mark will 
  meet with Damien
  - More work after FOSDEM
   - Stefan Spieker to join the core-pr-reviewer team: 
   https://groups.google.com/g/jenkinsci-dev/c/Wkhrs3nNEEU @NotMyFault 
   
  - Per the maintainer's doc, the board can vote on the decision: 
  
https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#ladder
  - @NotMyFault  is in favor, he has 
  been a great help reviewing core PRs and contributing to core before
  - @MarkEWaite is in favor
  - @basil is in favor
   
Community 
activity
   
   - Contributor summit results
  - Slides 
  

 from 
  the summit
  - @kmartens27 preparing a summary blog post
  - @MarkEWaite extend the Java 2+2+2 support plan JEP 
   with results from summit
   - Java 11, 17, and 21 in Jenkins - Mark Waite
  - Contributor summit provided additional information
 - HPI plugin has been extended to prepare for Java 11 end of life 
 - PR-578  from 
 Vincent Latombe
- HPI plugin not yet released with the change
 - 2+2+2 Java support plan - Jenkins enhancement proposal 
  

   submitted
 - Include the steps of the Java migration as part of the JEP (work 
 estimate, tasks, etc.)
- Mark has much more work to do here
   - Dropping support for a Java version (refer to Java 11 for 
   ideas)
   - Adding a Java version (use Java 21 addition as the pattern)
   - Making a Java version the recommended version (use Java 17 
   as the pattern)
- Further refinements to be done in the JEP
 - Key dates
 - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
 - Oct 30, 2024 - First Jenkins LTS to require Java 17
 - Oct 31, 2024 - end of Java 11 support by Jenkins project
  
Governance 
Topics
   
   - Jenkins awards - Mark Waite
  - Nominations close today, 19 Feb 2024
  - Overview of the Jenkins awards
 - CDF hosts the nominations
 - Most valuable advocate 
  - 
 speaking, promoting, training, tutoring
 - Most valuable contributor 
  - 
 features, fixes, and more
 - Security MVP 
  - 
 security reports and fixes for security issues
  - Nomination process for Jenkins awards
 - Nomination through GitHub issues
- Most valuable advocate 

   - 1 nomination currently, more 

Re: CI problem

[Mark Waite]

On Monday, February 19, 2024 at 8:42:37 AM UTC-7 Michael wrote:

Hi all 

I'm getting some problem on verification build 
16:39:14 Cannot contact jnlp-maven-17-wxw3t: 
hudson.remoting.ChannelClosedException: Channel 
"hudson.remoting.Channel@583d05db:JNLP4-connect connection from 
ec2-3-18-53-88.us-east-2.compute.amazonaws.com/3.18.53.88:38039": 


We use spot instances for many of our builds with automatic retry if a spot 
instance is reclaimed by the cloud provider.  That can result in agent 
failures, though they should retry automatically.

One the GitHub checks page 
, you should see 
a "Re-run" action that will allow you to start a ci.jenkins.io job again.

-- 
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/0517b5cb-535d-48ec-b1ed-2ae0e0654e9cn%40googlegroups.com.

CI problem

[Michael Nazzareno Trimarchi]

Hi all

I'm getting some problem on verification build
16:39:14  Cannot contact jnlp-maven-17-wxw3t:
hudson.remoting.ChannelClosedException: Channel
"hudson.remoting.Channel@583d05db:JNLP4-connect connection from
ec2-3-18-53-88.us-east-2.compute.amazonaws.com/3.18.53.88:38039":
Remote call on JNLP4-connect connection from
ec2-3-18-53-88.us-east-2.compute.amazonaws.com/3.18.53.88:38039
failed. The channel is closing down or has closed down

Are people aware of this?

Michael


-- 
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
mich...@amarulasolutions.com
__

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
i...@amarulasolutions.com
www.amarulasolutions.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/CAOf5uwn%2B9uzFzhCEzRSOhxZ2XZ%3DusD8zv3GViTsacLJ%3DUXi3Ng%40mail.gmail.com.

Re: nomad-plugin merge maxconcurrentjobs

['Alexander Brandes' via Jenkins Developers]

If an existing plugin maintainer decided to abandon the plugin, you are welcome 
to adopt the plugin to take care of it: 
https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/#abandoned-plugins

> On 19. Feb 2024, at 15:25, Kamil Cukrowski 
>  wrote:
> 
> Hi.
> The pull requests
> https://github.com/jenkinsci/nomad-plugin/pull/196
> https://github.com/jenkinsci/nomad-plugin/pull/170
> are open.
> It would be great to merge them,.
> Following the suggestion, I am writing here for direction.
> Thanks.
> Kamil Cukrowski
> 
> -- 
> 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/a7b6a592-b938-42b6-8712-cd81df2a68b8n%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/A60F9B7B-827D-43A1-91AD-99BE1947C930%40notmyfault.dev.

Re: Adoption request for jenkins-multijob-plugin

['Alexander Brandes' via Jenkins Developers]

> I would like to be able to release without bugging busy people :)

No worries, you didn’t bug me at all :)

Welcome aboard

> On 19. Feb 2024, at 13:51, Victor Balakine  wrote:
> 
> It was released as a favor by a core developer. I would like to be able to 
> release without bugging busy people :)
> 
> On Friday, February 16, 2024 at 7:42:12 PM UTC+2 Alexander Brandes wrote:
>> Hey,
>> 
>> Thanks for your interest in the plugin, but the PR you linked has already 
>> been merged and released, for your information.
>> 
>> 
>>> On 15. Feb 2024, at 09:58, Victor > wrote:
>>> 
>> 
>>> I'd like to be added to the maintainers of jenkins-multijob-plugin which is 
>>> deprecated, but still actively used in my company.
>>> Link to the plugin: https://plugins.jenkins.io/jenkins-multijob-plugin/
>>> The status of the plugin: appears abandoned
>>> Link to pull request I wanted to deliver: 
>>> https://github.com/jenkinsci/tikal-multijob-plugin/pull/352
>>> GitHub username: balakine
>>> Jenkins infrastructure account id: victor_yousician
>>> Repository Permission Updater PR: 
>>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3774
>>> 
>>> 
>> 
>>> -- 
>>> 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/CAH9cVJQGaVMHE%3D6RRDTNZB3NGK%2BEB3_YF34YMaJ-C7bEvQinDw%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/1c2ee579-74bc-4d82-94bf-2600d73d803en%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/EFBF7D0C-6925-40AD-B603-9D51730F8FBC%40notmyfault.dev.

nomad-plugin merge maxconcurrentjobs

[Kamil Cukrowski]

Hi.
The pull requests
https://github.com/jenkinsci/nomad-plugin/pull/196
https://github.com/jenkinsci/nomad-plugin/pull/170
are open.
It would be great to merge them,.
Following the suggestion, I am writing here for direction.
Thanks.
Kamil Cukrowski

-- 
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/a7b6a592-b938-42b6-8712-cd81df2a68b8n%40googlegroups.com.

Re: Adopt plugin openid-plugin

[Michael Nazzareno Trimarchi]

Hi Daniel, all

On Mon, Feb 19, 2024 at 2:12 PM 'Daniel Beck' via Jenkins Developers
 wrote:
>
>
> On Sun, Feb 18, 2024 at 5:56 PM Adrien Lecharpentier 
>  wrote:
>>
>> Please note that the plugin has multiple public security issues. I'm sure 
>> the security team will require you to resolve them before any release can be 
>> deployed.
>
>
> While we definitely prefer that (new) maintainers address unresolved 
> vulnerabilities as early as possible, we do not generally require that for 
> new releases, with two exceptions:
>
> * Plugins blocked from releasing because we identified a vulnerability 
> introduced since the latest release. Look for "releaseblock" in RPU for 
> examples.
> * Unsuspending plugins. In terms of security, we consider that to be similar 
> to new plugin hosting, so to restore publication, we ask that security issues 
> (publicly known or not) be addressed first.
>
> For anything else, the security warnings shown in Jenkins and on the plugins 
> site will remain active even for new releases.
>
> Some (few) plugins are actively maintained while not addressing previously 
> announced security vulnerabilities. Administrators can make an informed 
> decision on whether they want to install (or keep installed) such plugins.
>
> --
> 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/CAMo7PtLDhhbUEHA-YvAARisdpvdAq59CC4Wkn8ET771bvoFSXw%40mail.gmail.com.

Working to address vulnerabilities.

Michael


-- 
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
mich...@amarulasolutions.com
__

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
i...@amarulasolutions.com
www.amarulasolutions.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/CAOf5uw%3D4L1jz7-pxq_MNv7mYOApTLcZEA7%3DVdOKONQB%3DKdRsUw%40mail.gmail.com.

Re: Adopt plugin openid-plugin

['Daniel Beck' via Jenkins Developers]

On Sun, Feb 18, 2024 at 5:56 PM Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> wrote:

> Please note that the plugin has multiple public security issues. I'm sure
> the security team will require you to resolve them before any release can
> be deployed.
>

While we definitely prefer that (new) maintainers address unresolved
vulnerabilities as early as possible, we do not generally require that for
new releases, with two exceptions:

* Plugins blocked from releasing because we identified a vulnerability
introduced since the latest release. Look for "releaseblock" in RPU for
examples.
* Unsuspending plugins. In terms of security, we consider that to be
similar to new plugin hosting, so to restore publication, we ask that
security issues (publicly known or not) be addressed first.

For anything else, the security warnings shown in Jenkins and on the
plugins site will remain active even for new releases.

Some (few) plugins are actively maintained while not addressing previously
announced security vulnerabilities. Administrators can make an informed
decision on whether they want to install (or keep installed) such plugins.

-- 
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/CAMo7PtLDhhbUEHA-YvAARisdpvdAq59CC4Wkn8ET771bvoFSXw%40mail.gmail.com.

Re: Adoption request for jenkins-multijob-plugin

[Victor Balakine]

It was released as a favor by a core developer. I would like to be able to 
release without bugging busy people :)

On Friday, February 16, 2024 at 7:42:12 PM UTC+2 Alexander Brandes wrote:

> Hey,
>
> Thanks for your interest in the plugin, but the PR you linked has already 
> been merged and released, for your information.
>
> On 15. Feb 2024, at 09:58, Victor  wrote:
>
> I'd like to be added to the maintainers of jenkins-multijob-plugin which 
> is deprecated, but still actively used in my company.
> Link to the plugin: https://plugins.jenkins.io/jenkins-multijob-plugin/
> The status of the plugin: appears abandoned
> Link to pull request I wanted to deliver: 
> https://github.com/jenkinsci/tikal-multijob-plugin/pull/352
> GitHub username: balakine
> Jenkins infrastructure account id: victor_yousician
> Repository Permission Updater PR: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3774
>
>
> -- 
> 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/CAH9cVJQGaVMHE%3D6RRDTNZB3NGK%2BEB3_YF34YMaJ-C7bEvQinDw%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/1c2ee579-74bc-4d82-94bf-2600d73d803en%40googlegroups.com.

Re: Proposal: Stefan Spieker to join the core PR reviewers team

[Kris Stern]

+1

From: jenkinsci-dev@googlegroups.com  on behalf 
of Basil Crow 
Sent: 19 February 2024 05:10
To: jenkinsci-dev@googlegroups.com 
Subject: Re: Proposal: Stefan Spieker to join the core PR reviewers team

+1

On Sun, Feb 18, 2024 at 10:07 PM Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:


On Sunday, February 18, 2024 at 9:30:35 AM UTC-7 Alexander Brandes wrote:
Hey everyone,

I would like to propose Stefan Spieker 
(@StefanSpieker) to join the core PR 
reviewers team.

Stefan has been a core contributor since October 2022, and filed 
172 
pull requests, where 171 PRs have been merged.
Additionally, he has been active in reviewing core PRs and has voiced his 
opinion in almost 
300
 pull requests.

I would welcome him as an addition to the core pr team :)

+1 from me.

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/28e931e5-26e9-47c4-80c7-87871a4a929en%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/CAFwNDjrpBy1cWe%3DXGyhub1jKnExrd-Zr6GD%3Dn2KT3ObvgTRTBg%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/TY1P286MB31711224BADB05E5E0D8F882A1512%40TY1P286MB3171.JPNP286.PROD.OUTLOOK.COM.