Re: Adopt unity3d plugin

['Alexander Brandes' via Jenkins Developers]

You linked the wrong RPU PR, but welcome aboard, and thanks for adopting the 
plugin :)

> On 12. May 2024, at 06:28, Bob Du  wrote:
> 
> Hi,
> I would like to adopt a plugin:
> 
> Link: https://github.com/jenkinsci/unity3d-plugin
> Pull requests (optional): 
> https://github.com/jenkinsci/unity3d-plugin/pull/23
> Status: for abandoned 
> GitHub Username: BobDu
> Jenkins Infrastructure ID: bobdu
> Repository Permission Updater PR: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3763
> 
> 
> https://forum.unity.com/threads/automating-builds-with-jenkins.319169/
> 
> Original author lacostej has announced that it will completely hand over 
> maintenance rights to the jenkins community.
> I also noticed that he has left the jenkins team in github.
> 
> So I think the plugin is in fact in adoption status even though it's not 
> explicitly marked.
> 
> Best regards,
> 
> -- 
> 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/d2fa047b-dda1-44d3-ae0e-fd15b5d8d14bn%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/E5BDA396-659D-450E-A704-C88A4924294F%40notmyfault.dev.

Backporting for Jenkins 2.452.1 has started

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

Backporting for 2.452.1 has started, and the RC is scheduled for 01.05.2024.

Candidates: https://issues.jenkins.io/issues/?filter=12146
Fixed: 
https://issues.jenkins.io/browse/JENKINS-72954?jql=labels%20%3D%202.452.1-fixed
Rejected: 
https://issues.jenkins.io/browse/JENKINS-72954?jql=labels%20%3D%202.452.1-rejected

Cheers,
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/AF52236D-7905-45BA-9423-DE725A96E36E%40notmyfault.dev.

Re: Missing publication of plugin oic-auth releases in maven repository

['Alexander Brandes' via Jenkins Developers]

Hey,

mvnrepository.com  is just a frontend displaying 
metadata obtained from various repositories. It doesn’t host content, nor can 
you publish content there.

To see if a release of a Jenkins plugin exists, I recommend checking the 
corresponding plugin site, in this case 
https://plugins.jenkins.io/oic-auth/releases/
Otherwise, I would always recommend browsing the maven repository directly to 
see if an artifact has been published, instead of relying on third parties.

Best,
Alex

> On 21. Apr 2024, at 14:16, Michael Doubez  wrote:
> 
> Hello,
> 
> I have noticed that the release of oic-auth plugin have stopped being 
> published on maven repository.
> https://mvnrepository.com/artifact/org.jenkins-ci.plugins/oic-auth?repo=jenkins-releases
> 
> It is not a big deal but I don't see why that would happen. Other JEP-229 
> enabled plugins (like plain-credentials) have their releases in maven repo. 
> And release 3.0 which was the last one done manually doesn't appear as well.
> 
> I didn't see anything in the build logs reporting a failure to upload to 
> maven repo.
> 
> Did I miss something ?
> 
> 
> -- 
> 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/d68220e6-40a1-4ec8-9a7e-a2b97ec01014n%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/E63565A1-58E7-438B-A45C-DEFEB0F161D9%40notmyfault.dev.

2.452.1 release lead

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

I am volunteering to be the release lead for the upcoming LTS release, 2.452.1

The RC is scheduled for the 1st of May, final release for the 15th of May.

BR,
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/65C1456A-0035-49D8-888B-F246AD997073%40notmyfault.dev.

Re: Modernize device-watcher-plugin

['Alexander Brandes' via Jenkins Developers]

Given the plugin is up for adoption and there is no active maintainer left, I 
can only recommend adopting 
 the 
plugin, to move on with your PR.

~ Alex

> On 7. Apr 2024, at 09:58, Srikanth Jana  wrote:
> 
> Hi,
> Iam trying modernize device-watcher-plugin. I added Jenkinsfile to it and 
> raise PR but seems the build is not triggered.
> Can some suggest what could be wrong?
> 
> PR: https://github.com/jenkinsci/device-watcher-plugin/pull/2
> 
> Thanks,
> Jana
> 
> -- 
> 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/CAJxAiNBXFy%2BpJTxhjiL6iUGQvuAq7B0n%2BG0QS_XrJ_gXad6umg%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/E609BC67-8803-4F60-9246-2768DA67832C%40notmyfault.dev.

Re: Adopt msbuild plugiin

['Alexander Brandes' via Jenkins Developers]

Added, welcome aboard :)

> On 2. Apr 2024, at 18:00, Mark Waite  wrote:
> 
> This is great.  Thanks very much for adopting the plugin!
> 
> On Tuesday, April 2, 2024 at 9:53:14 AM UTC-6 tilalx wrote:
>> Hi,
>> 
>> the msbuild plugin is up for adoption. I'd like to adopt it in order to 
>> deliver some features.
>> 
>> plugin pull request: https://github.com/jenkinsci/msbuild-plugin/pull/118
>> RPU pull request: 
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3868
>> GitHub username: tilalx
>> Jenkins username: tilalx
>> 
>> Regards,
>> Tilo
> 
> 
> -- 
> 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/0b02657d-4e25-4027-b9c2-0590bc4cc4dan%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/0D6CF16D-191B-4272-AE15-2255F0A4210F%40notmyfault.dev.

Re: 2.452 as May 15, 2024 LTS baseline?

['Alexander Brandes' via Jenkins Developers]

+1 for 2.452

> On 3. Apr 2024, at 17:23, Mark Waite  wrote:
> 
> We should select the baseline today for the long term support release that 
> will be delivered May 15, 2024.
> 
> I propose Jenkins 2.452  as the 
> next LTS baseline.  It was released yesterday Apr 3, 2024.
> 
> Feedback is positive on the release.  It is running on weekly.jenkins.io 
>  and I'm using on my weekly installation.  The 
> last 10+ weekly releases have good ratings with no serious open regressions.
> 
> 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/f4607e94-03cd-433c-9fe2-ce9efbb24482n%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/B27E6C8A-9DDC-4A35-A891-F401E8943257%40notmyfault.dev.

Building Jenkins core and plugins with Java 22

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

I released an update for the Jenkins parent poms for plugins (>= 4.80) and 
libraries (>= 1.112), making sure, that building a component on Java 22 via 
`mvn clean verify package` does no longer fail on the “license” step, which was 
a blocker before.

Plugins and Jenkins core I built with Java 21 before, I can now build and run 
with Java 22, and I didn’t locate any issues yet.

Don’t forget to merge your dependabot PRs, when you’re moving on with your 
tests :)

~ 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/A1D5D458-5303-4B3E-B008-A40A0352823E%40notmyfault.dev.

Re: Adoption request for scmskip plugin

['Alexander Brandes' via Jenkins Developers]

Added, welcome aboard :)

> On 24. Mar 2024, at 16:10, zbyne...@gmail.com  wrote:
> 
> Hi,
> 
> the scmskip plugin is up for adoption. I'd like to adopt it in order to 
> deliver some bugfixes.
> 
> plugin pull request: https://github.com/jenkinsci/scmskip-plugin/pull/25
> RPU pull request: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3831
> GitHub username: zbynek (alrady member of jenkinsci organization)
> Jenkins username: zbynek
> 
> Cheers,
> Zbynek
> 
> -- 
> 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/75c1df3b-0399-47b0-a465-0e40470f9afdn%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/63147CA9-91D5-4CBA-B6BA-E10741407F33%40notmyfault.dev.

Re: Adopt email-ext plugin

['Alexander Brandes' via Jenkins Developers]

Added, welcome aboard :)

> On 28. Mar 2024, at 18:56, Adrien Lecharpentier 
>  wrote:
> 
> Funny thing: link to the pull request is not correct but it's text is. 
> 
> Link is 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3851
> 
> Le jeu. 28 mars 2024, 18:55, Adrien Lecharpentier 
> mailto:adrien.lecharpent...@gmail.com>> a 
> écrit :
>> +1 from me.
>> Basil is listed as maintainer but the repo has the adopt-this-plugin topic. 
>> Don't know if +1 are really required here.
>> 
>> Le jeu. 28 mars 2024, 18:00, Kris Stern > > a écrit :
>>> +1
>>> From: jenkinsci-dev@googlegroups.com 
>>>  >> > on behalf of Verachten Bruno 
>>> mailto:gount...@gmail.com>>
>>> Sent: 29 March 2024 00:58
>>> To: jenkinsci-dev@googlegroups.com  
>>> mailto:jenkinsci-dev@googlegroups.com>>
>>> Subject: Re: Adopt email-ext plugin
>>>  
>>> +1 from me.
>>> 
>>> On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins Developers 
>>> mailto:jenkinsci-dev@googlegroups.com>> 
>>> wrote:
>>> +1 from me!
>>> 
>>> On Thu, Mar 28, 2024 at 11:58 AM Alex Earl >> > wrote:
>>> Howdy,
>>> 
>>> The email-ext plugin is up for adoption. I'd like to re-adopt it (been a 
>>> few years so I may be a little rusty :) )
>>> 
>>> RPU pull request: 
>>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3851 
>>> 
>>> GitHub username: slide (already member of jenkinsci organization)
>>> Jenkins username: slide_o_mix
>>> 
>>> Thanks
>>> 
>>> 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/ee3bd5a5-ca18-4642-94c5-3a3b83640515n%40googlegroups.com
>>>  
>>> .
>>> 
>>> 
>>> -- 
>>> Kevin Martens
>>> 
>>> Technical Content Developer
>>> CloudBees, Inc.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> E:
>>> kmart...@cloudbees.com 
>>> Pronouns: He/Him/His
>>> 
>>> 
>>> 
>>> -- 
>>> 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/CAP92yNeKCGoyWDtYh%2B1pQMzi-cXKx2O5ntjRSm6LLVC05qVz1g%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/CACtV%3DdcnuLN4c1U-qESD1U7nNrTiLw4vPO6pO31ULhmfnTeZ_g%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/TYVP286MB316625A66F0976ABCFF929DDA13B2%40TYVP286MB3166.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/CAKwJSvzCqG42ZDNYQQqgy3zPTUmd7JYgZ5UKUydLsFFuSCuydQ%40mail.gmail.com
>  
> 

Re: Retire some of my old plugins

['Alexander Brandes' via Jenkins Developers]

No objections from me.

To mark the plugins as EOL, I recommend adding the “deprecated” topic to the 
GitHub repositories, adding a note to the README that the plugin is EOL, 
closing open PRs and archiving the GH repository.
Finally, you can remove yourself from the repository-permission-updater file.

> On 17. Mar 2024, at 02:13, 'Gavin Mogan' via Jenkins Developers 
>  wrote:
> 
> https://plugins.jenkins.io/html5-notifier-plugin/ - Code wasn't updated for 
> html to div project, nobody complained. The html5 notifications apis have 
> changed. While I do have a working branch, there's been no complaints, so I 
> think we should just archive the plugin
> 
> https://plugins.jenkins.io/graphql-server/ - Failed attempt at trying to 
> create graphql interface for jenkins. Graphql just doesn't handle class 
> inheritance well enough for it to work nicely with all the plugin interfaces. 
> Someone could take it over, but since its an incomplete prototype, I think 
> its worth archiving them.
> 
> Is there any objections? Also how would I go about officially marking them 
> depreciated/achieved?
> 
> -- 
> 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_DutK1ArKbCo3JbaPOz1V9DYFL_jtzeV4Cv4t5fMAdz%3D0uw%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/FA603023-0D1A-4387-B914-0484B47ACABB%40notmyfault.dev.

Re: Adopt scoring-load-balancer and additional-identities-plugin

['Alexander Brandes' via Jenkins Developers]

Welcome aboard :)On 12. Mar 2024, at 08:54, 'Bruno Verachten' via Jenkins Developers  wrote:Thanks.That's a +1 from me.Welcome, Michael.On Tue, Mar 12, 2024 at 8:51 AM 'Michael Kriese' via Jenkins Developers  wrote:Yes, I like to modernize both and enable CD after that, so it needs less attention.I've already prepared one PR long time ago, will update it after i've proper permissions.https://github.com/jenkinsci/additional-identities-plugin/pull/5goun...@gmail.com schrieb am Dienstag, 12. März 2024 um 08:47:55 UTC+1:Hello Michael,

Are there any plans to modernize these plugins?
Any PR you have in mind?
Thanks for proposing this.

Best regards,

Bruno Verachten

On Mon, Mar 11, 2024 at 10:41 PM Michael Kriese
 wrote:
>
> Hi all,
>
> I like to adopt these plugins which don't have maintainers
> - https://github.com/jenkinsci/scoring-load-balancer-plugin
> - https://github.com/jenkinsci/additional-identities-plugin
>
> My GitHub account
> - https://github.com/viceice
>
> PR for permissions
> - https://github.com/jenkins-infra/repository-permissions-updater/pull/3807
> - https://github.com/jenkins-infra/repository-permissions-updater/pull/3808
>
> Regards
> Michael Kriese
>
> --
> 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/de948c7c-8898-4fc2-a449-bb7682132615n%40googlegroups.com.



-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a0571838-5c03-4998-9b67-501ed9aec09cn%40googlegroups.com.
-- Bruno VerachtenSr Developer RelationsCloudBees, Inc.
P: +33.632.934.165 | GMT+1E: bverach...@cloudbees.comTwitter: https://twitter.com/PoddingueLinkedIn: https://www.linkedin.com/in/poddingue/Pronouns: he/his



-- 
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/CAFbR2rr_azp%2B%3DqGEyFmrwvw3qukhOpKe2tySXUELbjLWKuumbw%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/44488547-EDA8-4045-90C3-00BE7943DCE7%40notmyfault.dev.

Re: Remove Suggestimate from issues.jenkins.io?

['Alexander Brandes' via Jenkins Developers]

+1

> On 11. Mar 2024, at 14:48, Mark Waite  wrote:
> 
> The Jenkins Jira instance  uses a Jira datacenter 
> license that is donated to the Jenkins project by Atlassian.
> 
> The Suggestimate plugin 
> 
>  is installed on the Jenkins Jira instance and is reporting that its license 
> has expired.  The Suggestimate pricing page 
> 
>  says that the plugin would cost $4500 per year based on the number of users 
> of our Jira instance.  The question and answer section indicates that our 
> donated Jira Datacenter license does not include the license for the plugin.
> 
> I propose that we should remove that plugin from issues.jenkins.io rather 
> than pay a licensing fee for the plugin.
> 
> Any objections to the removal of that plugin from issues.jenkins.io?
> 
> 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/a96f9c00-ff28-47fb-a3eb-210826ae5d7dn%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/9350BA98-7F99-436F-A888-A33CC3187645%40notmyfault.dev.

Re: Adoption of delivery-pipeline-plugin

['Alexander Brandes' via Jenkins Developers]

Thanks and welcome aboard :)

> On 4. Mar 2024, at 12:33, Verachten Bruno  wrote:
> 
> Welcome, René, and best of luck for the adoption.
> 
>> On Mon, Mar 4, 2024 at 11:56 AM René Zanner  wrote:
>> 
>> Hi everyone,
>> 
>> I'm about to adopt the delivery-pipeline-plugin, mainly to fix current 
>> incompatibility issues with the promoted-builds-plugin (see 
>> https://issues.jenkins.io/browse/JENKINS-72527).
>> I work in a Munich tech company (still) heavily using 
>> delivery-pipeline-plugin together with the promoted-builds-plugin - so this 
>> is my main motivation to get this fixed... ;-)
>> 
>> I was picking up https://issues.jenkins.io/browse/JENKINS-70687 to get the 
>> source code transferred to the jenkinsci organization on GitHub and 
>> Alexander Brandes was so kind to guide me through the process so far.
>> 
>> This here is the official "notification email to the Jenkins Developers 
>> mailing list" as requested on 
>> https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin:
>> 
>> Link to a plugin you want to adopt: 
>> https://plugins.jenkins.io/delivery-pipeline-plugin/
>> 
>> The status of the plugin ("for adoption" or "abandoned") - (inofficially) 
>> abandoned - there was no response from the existing maintainers after 
>> pinging them in GitHub, so Alexander Brandes told me to go ahead and change 
>> the RPU repo to replace them with me and my colleague as new maintainers.
>> 
>> Link(s) to pull requests you want to deliver, if applicable: since we're 
>> about to modernize it first, there's no PR, yet
>> 
>> Your GitHub username/id (e.g. oleg-nenashev for 
>> https://github.com/oleg-nenashev/) - rzanner
>> 
>> Your Jenkins infrastructure account id. Create your account if you don’t 
>> have one. - rzanner
>> 
>> The link to the "Repository Permission Updater" PR described below - 
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3792 
>> (already merged by Alexander Brandes)
>> 
>> Kudos to Alexander Brandes for assisting me and Mark Waite to get me going. 
>> ;-)
>> 
>> Cheers,
>> René
>> 
>> --
>> 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/f826c190-cc2e-47b5-9ad1-be63336b1a12n%40googlegroups.com.
> 
> 
> 
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CACtV%3DdfqmfwwXAmRY776JovPyaY5LN-jq7gQG7EhXvt60Hp1gg%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/C26AE0B9-EF07-48E2-8E4B-AA7CC15BDB10%40notmyfault.dev.

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  <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 
> <https://github.com/StefanSpieker>) to join the core PR reviewers team.
> 
> Stefan has been a core contributor since October 2022, and filed 172 
> <https://github.com/jenkinsci/jenkins/pulls?q=is:pr+author:stefanspieker> 
> 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 
> <https://github.com/jenkinsci/jenkins/pulls?q=is:pr+reviewed-by:stefanspieker>
>  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 
> <mailto: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
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/28e931e5-26e9-47c4-80c7-87871a4a929en%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 
> <mailto: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
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrpBy1cWe%3DXGyhub1jKnExrd-Zr6GD%3Dn2KT3ObvgTRTBg%40mail.gmail.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 
> <mailto: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
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/TY1P286MB31711224BADB05E5E0D8F882A1512%40TY1P286MB3171.JPNP286.PROD.OUTLOOK.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/346A81EF-4657-4A22-8B7B-C3C46B70A5B2%40notmyfault.dev.

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
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH9cVJQGaVMHE%3D6RRDTNZB3NGK%2BEB3_YF34YMaJ-C7bEvQinDw%40mail.gmail.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 
> <mailto: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
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/1c2ee579-74bc-4d82-94bf-2600d73d803en%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/EFBF7D0C-6925-40AD-B603-9D51730F8FBC%40notmyfault.dev.

Re: Adopt plugin openid-plugin

['Alexander Brandes' via Jenkins Developers]

Additionally to bumping the jenkins.version, don’t forget to modernise the 
plugin to our standards for maintained plugins: 
https://github.com/jenkinsci/archetypes/tree/master/common-files (ignoring 
archetype-post-generate.groovy)

> On 18. Feb 2024, at 21:41, Michael Nazzareno Trimarchi 
>  wrote:
> 
> Hi
> 
> Solved this way
> 
> +
> +  org.jenkins-ci.plugins
> +  junit
> +  1119.1121.vc43d0fc45561
> +  test
> +
> +
> +  org.jenkins-ci.plugins
> +  script-security
> +  1175.v4b_d517d6db_f0
> +  test
> +
> 
> Is this the correct way?
> 
> Michael
> 
> On Sun, Feb 18, 2024 at 9:05 PM Michael Nazzareno Trimarchi
>  wrote:
>> 
>> Hi all
>> 
>> I have some lack of experience but how can I resolve a problem like this?
>> 
>> 20:04:25  Caused by: java.io.IOException: Failed to load: Matrix
>> Project Plugin (matrix-project 785.v06b_7f47b_c631)
>> 20:04:25   - Update required: JUnit Plugin (junit 1.3) to be updated
>> to 1119.1121.vc43d0fc45561 or higher
>> 
>> Is something that is connected to the pom.xml?
>> 
>> Michael
>> 
>> 
>> 
>> On Sun, Feb 18, 2024 at 6:15 PM Adrien Lecharpentier
>>  wrote:
>>> 
>>> The jenkins.version you set in your pom requires java 11 minimum 
>>> (https://www.jenkins.io/doc/book/platform-information/support-policy-java/).
>>> However, the jenkinsfile still tries to build the plugin using java 8 on 
>>> windows.
>>> 
>>> As you are not the maintainer for now, changing the Jenkinsfile wouldn't 
>>> change anything as it wouldn't be used.
>>> 
>>> Once you're the maintainer, I'd suggested to open a pull request updating 
>>> the jenkinsfile configuration (there is a open rewrite recipe to help you). 
>>> Merge that PR and then you can work more deeply on the plugin.
>>> 
>>> Le dim. 18 févr. 2024, 18:07, Michael Nazzareno Trimarchi 
>>>  a écrit :
 
 Hi
 
 On Sun, Feb 18, 2024 at 5:56 PM Adrien Lecharpentier
  wrote:
> 
> Even if the plugin is not mark as up for adoption, it currently has no 
> maintainer listed in the RPU. So +1 for me.
> 
> 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.
> 
 
 Ok I see, mostly my problem is even resolve CI build on jenkins CI too
 
 Michael
 
> Le dim. 18 févr. 2024, 16:35, Michael Nazzareno Trimarchi 
>  a écrit :
>> 
>> Hi all
>> 
>> https://github.com/jenkinsci/openid-plugin/pull/24
>> 
>> My github account
>> https://github.com/panicking
>> 
>> Pull request for the permission
>> 
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3776
>> 
>> Michael
>> 
>> --
>> 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/CAOf5uwnO4r%2B-upaC-5wCMXbez-bsBd3LajxyU483ftm%2BMLYq2A%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/CAKwJSvyP%3DkpWEcumyRLhzYBrn4rfB9NguybafT4MwxnTq4f12g%40mail.gmail.com.
 
 
 
 --
 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/CAOf5uwnQTw0z2bO3RRK6xvorCNmBUojQirg%2BpDJR%2BS3h81RxCg%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/CAKwJSvy-ozNe95WkobFbDEidjFz%3DzCeN2rVw_uY_YKY-21kHaw%40mail.gmail.com.
>> 
>> 
>> 
>> --
>> Michael Nazzareno Trimarchi
>> Co-Founder & Chief Executive 

Proposal: Stefan Spieker to join the core PR reviewers team

['Alexander Brandes' via Jenkins Developers]

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 :)

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/C1B318DE-5D1F-44F9-B0D3-2CE7CF584352%40notmyfault.dev.

Re: Jenkins 2.440.1-rc has been released

['Alexander Brandes' via Jenkins Developers]

A new RC is available at 
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.440.1-rc34550.408915024528/jenkins-war-2.440.1-rc34550.408915024528.war
 

> On 9. Feb 2024, at 12:35, Mark Waite  wrote:
> 
> 
> 
> On Thursday, February 8, 2024 at 5:47:35 AM UTC-7 Alexander Brandes wrote:
> Hey everyone,
> 
> Jenkins 2.440.1 RC has been released and is ready to be tested.
> 
> Please report issues found in this thread.
> 
> The final release is scheduled for 21.02.2024.
> 
> Download the release candidate from artifactory: 
> https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/jenkins-war/2.440.1-SNAPSHOT/jenkins-war-2.440.1-20240208.123517-1.war
>  
> 
> 
> I'm using it in my test environment and have found no issues yet.
>  
> 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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/ec73d542-7e79-4456-9cc6-6147712a6a02n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/ec73d542-7e79-4456-9cc6-6147712a6a02n%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/E69D000E-62E0-486C-9185-8268D1149C66%40notmyfault.dev.

Re: Adoption request for jenkins-multijob-plugin

['Alexander Brandes' via Jenkins Developers]

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-dev+unsubscr...@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/3A8FC972-C398-48C0-B758-270A62558D72%40notmyfault.dev.

Re: Build p4-plugin using gradle.

['Alexander Brandes' via Jenkins Developers]

> Any insights or suggestions

I would suggest staying with the maven toolchain, given the JPI plugin is 
feature stalled and we stopped onboarding plugins using Gradle over Maven more 
than a year ago.
If loss of functionality, stability, and support is no concern, you may use 
Gradle.

> On 13. Feb 2024, at 10:02, Sandeep Kumar  wrote:
> 
> Hi Team,
> 
> In the p4-plugin, I have made the switch from Maven to Gradle as the build 
> tool using "gradle-jpi-plugin" 
> (https://github.com/jenkinsci/gradle-jpi-plugin).
> 
> Before publishing, I want to gather feedback from the community to address 
> any potential issues that may have been overlooked during this migration. 
> 
> The Gradle file for the plugin can be found here: 
> https://github.com/jenkinsci/p4-plugin/blob/master/build.gradle. Any insights 
> or suggestions from the community would be highly appreciated.
> 
> Also, Which repository should be prioritized for publishing artifacts: 
> https://repo.jenkins-ci.org/public/ or https://repo.jenkins-ci.org/releases?
> 
> P4-Plugin: https://github.com/jenkinsci/p4-plugin
> 
> Thanks
> Sandeep Kumar
> sku...@perforce.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/1e67637a-6da6-499e-9e0c-5c746d746ff6n%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/6403749B-05E2-49EA-82F6-864E57FE5CE1%40notmyfault.dev.

Jenkins 2.440.1-rc has been released

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

Jenkins 2.440.1 RC has been released and is ready to be tested.

Please report issues found in this thread.

The final release is scheduled for 21.02.2024.

Download the release candidate from artifactory: 
https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/jenkins-war/2.440.1-SNAPSHOT/jenkins-war-2.440.1-20240208.123517-1.war
 

After the final release, the upgrade guide and changeling will be updated 
accordingly.

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/B26218E6-421E-4D00-BBD8-2ADE42A2B86F%40notmyfault.dev.

Re: [Jenkins Development Support for IntelliJ IDEA] Release 3.0.3

[Alexander Brandes]

Thanks for implementing the deprecation marker :)

On Thursday 1 February 2024 at 01:01:07 UTC+1 due...@gmail.com wrote:

>
> https://plugins.jetbrains.com/plugin/1885-jenkins-development-support/versions/stable/478313
> A plumbing change and one new feature:
>
> 3.0.3
>
>-  Compatibility baseline is changed to 2022.3 which also changes 
>Java level to 17. No functional changes are expected.
>-  Report custom tag attributes that are marked deprecated.
>
>

-- 
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/d403fc8c-ea12-49b4-9fbc-6bd22ca9c774n%40googlegroups.com.

Backporting for 2.440.1 has started

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

Backporting for 2.440.1 has started, and the RC is scheduled for 21.02.2024.

Candidates: https://issues.jenkins.io/issues/?filter=12146
Fixed: 
https://issues.jenkins.io/browse/JENKINS-72603?jql=labels%20%3D%202.440.1-fixed 
Rejected: 
https://issues.jenkins.io/browse/JENKINS-72603?jql=labels%20%3D%202.440.1-rejected

Best regards,

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/DA5B0651-62A5-405B-8833-977DA14BFEB2%40notmyfault.dev.

Re: [Adoption] mail-watcher-plugin

['Alexander Brandes' via Jenkins Developers]

Added, thanks for adopting :)

> On 27. Jan 2024, at 10:47, Stefan Spieker  wrote:
> 
> Hi,
> I would like to adopt a plugin:
> Link: https://github.com/jenkinsci/mail-watcher-plugin
> Pull requests: 
> https://github.com/jenkinsci/mail-watcher-plugin/pull/92
> https://github.com/jenkinsci/mail-watcher-plugin/pull/93
> Status: for adoption
> GitHub Username: StefanSpieker
> Jenkins Infrastructure ID: stefan_spieker
> Repository Permission Updater PR: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3758
> I plan to update and modernize the plugin. I also see the possibility to use 
> this plugin for notifiying about failed backups from thin-backup plugin, 
> where I'm also the maintainer.
> 
> Best regards,
> Stefan Spieker
> 
> -- 
> 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/9a430f99-75b6-45bf-b422-aa2bdc211b45n%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/9593A882-6601-49FC-8CB5-CE422C45A8F0%40notmyfault.dev.

Re: 2.440.1 Release Lead

['Alexander Brandes' via Jenkins Developers]

Thanks for the approvals :)

> On 22. Jan 2024, at 18:42, Basil Crow  wrote:
> 
> +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/CAFwNDjrbgLJRfB5xbOm2ru_3WhN%2Bq8egA2k9BTu1qUpcWNP3mQ%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/82151726-5D5C-4CD7-9FC7-8B0197CDA389%40notmyfault.dev.

2.440.1 Release Lead

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

As discussed in https://groups.google.com/g/jenkinsci-dev/c/DXf7-uE7gII, I am 
volunteering to be the release lead for 2.440.1.

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/41C6FD90-0773-49FD-B29D-D908686EDE4D%40notmyfault.dev.

Re: fixing the access permissions for plugin maintained by unresponsive owner

['Alexander Brandes' via Jenkins Developers]

The maintainer responded with a reasonable explanation and objected to your 
adoption request: 
https://github.com/jenkinsci/tap-plugin/pull/36#issuecomment-1893725271

Thanks for understanding.

> On 16. Jan 2024, at 13:53, 'Alexander Brandes' via Jenkins Developers 
>  wrote:
> 
> I have reached out to the maintainer will keep you posted with their decision.
> 
>> On 16. Jan 2024, at 13:36, 'Alexander Brandes' via Jenkins Developers 
>>  wrote:
>> 
>> As seen evidently in https://github.com/jenkinsci/tap-plugin/pull/35, the 
>> maintainer is not inactive. I have forwarded the mail to the maintainer 
>> allowing some time for them to decide :)
>> 
>>> On 16. Jan 2024, at 13:17, Jiri Vanek  wrote:
>>> 
>>> hello!
>>> 
>>> It seems, that when there is unresponsive maintainer (about half year and 
>>> more of none, or weird replies to PRs or bugs),
>>> then it should be possible to rise a PR and become comaintainer of the 
>>> plugin.
>>> 
>>> eg: 
>>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3721/
>>> 
>>> However that is not enough - as it is allowing to push to artifactory, 
>>> however not to repo. So one can not do changes, nor approve PRs, nor to do 
>>> a release.
>>> 
>>> Is that expected? If so, From above scope, what is the point of granting a 
>>> permissions the jenkins-infra/repository-permissions-updater in such case? 
>>> (as release can not be done anyway)
>>> If not, what was expected? Or was something not working as expected?
>>> Is there some mechanism how to fix unresponsive maintainer completely?
>>> 
>>> I know that this may be fragile and sensitive topic, but I belive that 
>>> plugin belongs to wider community, and should not die jsut because single 
>>> maintainer pass away or say that will do, but never does.
>>> 
>>> Thank you in advance,
>>>  J.
>>> 
>>> 
>>> 
>>> -- 
>>> Jiri Vanek Mgr.
>>> Principal QA Software Engineer
>>> Red Hat Inc.
>>> +420 775 39 01 09
>>> 
>>> -- 
>>> 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/6fed3265-79d7-4e4d-989c-bdc02a3a332d%40redhat.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 
>> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/1F78030A-1613-405E-B439-BEDA543B20AF%40notmyfault.dev
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/1F78030A-1613-405E-B439-BEDA543B20AF%40notmyfault.dev?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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/785B4889-CA83-4DDB-AF9D-87C02176F3D0%40notmyfault.dev
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/785B4889-CA83-4DDB-AF9D-87C02176F3D0%40notmyfault.dev?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/9D0DB105-260E-4D9F-9A28-863B4A0DB18D%40notmyfault.dev.

Re: fixing the access permissions for plugin maintained by unresponsive owner

['Alexander Brandes' via Jenkins Developers]

I have reached out to the maintainer will keep you posted with their decision.

> On 16. Jan 2024, at 13:36, 'Alexander Brandes' via Jenkins Developers 
>  wrote:
> 
> As seen evidently in https://github.com/jenkinsci/tap-plugin/pull/35, the 
> maintainer is not inactive. I have forwarded the mail to the maintainer 
> allowing some time for them to decide :)
> 
>> On 16. Jan 2024, at 13:17, Jiri Vanek  wrote:
>> 
>> hello!
>> 
>> It seems, that when there is unresponsive maintainer (about half year and 
>> more of none, or weird replies to PRs or bugs),
>> then it should be possible to rise a PR and become comaintainer of the 
>> plugin.
>> 
>> eg: 
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3721/
>> 
>> However that is not enough - as it is allowing to push to artifactory, 
>> however not to repo. So one can not do changes, nor approve PRs, nor to do a 
>> release.
>> 
>> Is that expected? If so, From above scope, what is the point of granting a 
>> permissions the jenkins-infra/repository-permissions-updater in such case? 
>> (as release can not be done anyway)
>> If not, what was expected? Or was something not working as expected?
>> Is there some mechanism how to fix unresponsive maintainer completely?
>> 
>> I know that this may be fragile and sensitive topic, but I belive that 
>> plugin belongs to wider community, and should not die jsut because single 
>> maintainer pass away or say that will do, but never does.
>> 
>> Thank you in advance,
>>  J.
>> 
>> 
>> 
>> -- 
>> Jiri Vanek Mgr.
>> Principal QA Software Engineer
>> Red Hat Inc.
>> +420 775 39 01 09
>> 
>> -- 
>> 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/6fed3265-79d7-4e4d-989c-bdc02a3a332d%40redhat.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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1F78030A-1613-405E-B439-BEDA543B20AF%40notmyfault.dev
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/1F78030A-1613-405E-B439-BEDA543B20AF%40notmyfault.dev?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/785B4889-CA83-4DDB-AF9D-87C02176F3D0%40notmyfault.dev.

Re: fixing the access permissions for plugin maintained by unresponsive owner

['Alexander Brandes' via Jenkins Developers]

As seen evidently in https://github.com/jenkinsci/tap-plugin/pull/35, the 
maintainer is not inactive. I have forwarded the mail to the maintainer 
allowing some time for them to decide :)

> On 16. Jan 2024, at 13:17, Jiri Vanek  wrote:
> 
> hello!
> 
> It seems, that when there is unresponsive maintainer (about half year and 
> more of none, or weird replies to PRs or bugs),
> then it should be possible to rise a PR and become comaintainer of the plugin.
> 
> eg: https://github.com/jenkins-infra/repository-permissions-updater/pull/3721/
> 
> However that is not enough - as it is allowing to push to artifactory, 
> however not to repo. So one can not do changes, nor approve PRs, nor to do a 
> release.
> 
> Is that expected? If so, From above scope, what is the point of granting a 
> permissions the jenkins-infra/repository-permissions-updater in such case? 
> (as release can not be done anyway)
> If not, what was expected? Or was something not working as expected?
> Is there some mechanism how to fix unresponsive maintainer completely?
> 
> I know that this may be fragile and sensitive topic, but I belive that plugin 
> belongs to wider community, and should not die jsut because single maintainer 
> pass away or say that will do, but never does.
> 
> Thank you in advance,
>  J.
> 
> 
> 
> -- 
> Jiri Vanek Mgr.
> Principal QA Software Engineer
> Red Hat Inc.
> +420 775 39 01 09
> 
> -- 
> 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/6fed3265-79d7-4e4d-989c-bdc02a3a332d%40redhat.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/1F78030A-1613-405E-B439-BEDA543B20AF%40notmyfault.dev.

Re: 2.440 as Feb 21, 2024 LTS baseline?

['Alexander Brandes' via Jenkins Developers]

I’m +1 for 2.440 :)

> On 13. Jan 2024, at 02:32, Mark Waite  wrote:
> 
> Wednesday Jan 10, 2024 is the day that we should select the baseline for the 
> long term support release that will be delivered February 21, 2024.
> 
> I propose Jenkins 2.440  as the 
> next LTS baseline.  It was released Tuesday Jan 9, 2024.  It includes user 
> interface improvements, configuration as code improvements, and improvements 
> to the remoting library that communicates with agents.
> 
> Feedback is positive on the release.  It is running on weekly.jenkins.io and 
> I'm using on my weekly installation.
> 
> 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/bea3f5b4-bea7-41b4-8344-6bdcb56bc33en%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/A48D3272-E4E5-4203-86BD-BE106F0A1CAB%40notmyfault.dev.

Re: jenkins-2.426.3-rc has been released

['Alexander Brandes' via Jenkins Developers]

Here’s the working download URL for the RC: 
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.426.3-rc34287.96dc95a_55e9c/jenkins-war-2.426.3-rc34287.96dc95a_55e9c.war
 

> On 10. Jan 2024, at 23:01, Jenkins Release Bot  
> wrote:
> 
> Please report issues found to the release candidate announcement 
>  
> thread.
> 
> Final release is scheduled for 2024-01-24.
> 
> Download the release from: 
> https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.426.3-rc34287.96dc95a55e9c/jenkins-war-2.426.3-rc34287.96dc95a55e9c.war
> 
> After final release, the official changelog 
>  and official upgrade guide 
>  will be available on 
> www.jenkins.io/download .
> 
> 
> -- 
> 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/70f8fc02-0552-e22f-19bc-28588022956f%40jenkinsreleasebot
>  
> .

-- 
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/6AAB7554-7032-4103-9FF8-52348D9695BB%40notmyfault.dev.

Re: Adoption request for radargun-plugin

['Alexander Brandes' via Jenkins Developers]

Welcome aboard :)

> On 5. Jan 2024, at 13:24, Anna Manukyan  wrote:
> 
> Hi,
> 
> at the moment there is no active maintainer of the radargun-plugin. So I need 
> to take the responsibility to maintain/merge PRs to the plugin. Agreed with 
> current maintainer vjuranek.
> 
> Link to a plugin you want to adopt: https://plugins.jenkins.io/radargun/
> The status of the plugin ("for adoption" or "abandoned"): abandoned
> Link(s) to pull requests you want to deliver, if applicable:  -
> Your GitHub username/id (e.g. oleg-nenashev for 
> https://github.com/oleg-nenashev/): andyuk1986
> Your Jenkins infrastructure account id. Create your account 
>  if you don’t have one.: amanukya
> The link to the "Repository Permission Updater" PR described below: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3729 
> Thanks in advance.
> Best regards,
> Anna.
> 
> -- 
> 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/e25fc4dc-da44-47c1-a74f-e5efa8da210en%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/997CFB03-950E-4D0A-8781-2B177ACEFF13%40notmyfault.dev.

Re: Adoption request pipeline-as-yaml-plugin

['Alexander Brandes' via Jenkins Developers]

Approved, thanks for adopting :)

> On 3. Jan 2024, at 15:09, Verachten Bruno  wrote:
> 
> +1 from me.
> Thanks a lot, Valentin!
> 
> On Wed, Jan 3, 2024 at 11:56 AM Valentin Delaye (jonesbusy)
>  wrote:
>> 
>> Hi,
>> 
>> pipeline-as-yaml-plugin doesn't have any active maintainer. The plugin now 
>> doesn't work with recent Jenkins version (mainly due to SnakeYAML migration).
>> 
>> I'm not a user of the plugin but I volunteer to adopt it and keep it in 
>> minimal working state.
>> 
>> Link to a plugin you want to adopt: 
>> https://github.com/jenkinsci/pipeline-as-yaml-plugin
>> 
>> The status of the plugin ("for adoption" or "abandoned"): abandoned
>> 
>> Link(s) to pull requests you want to deliver, if applicable. 
>> https://github.com/jenkinsci/pipeline-as-yaml-plugin/pull/77
>> 
>> Your GitHub username/id: jonesbusy
>> 
>> Your Jenkins infrastructure account id: jonesbusy
>> 
>> The link to the "Repository Permission Updater" PR described below: 
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3723
>> 
>> Regards,
>> 
>> --
>> 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/f5a6c479-fd18-45a4-8feb-75ebdfe78601n%40googlegroups.com.
> 
> 
> 
> -- 
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CACtV%3DddfFq5Cir%3D%2BJD3BuevGpJJ_gfJxbqNYaXeR6n%3D%3DfOxHUA%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/E4A4E80F-298E-4D25-BFEE-A6D771DA26ED%40notmyfault.dev.

Re: UI/Website Feedback on top bar

['Alexander Brandes' via Jenkins Developers]

> Does anyone have some strong opinions? Changing this to always go to 
> jenkins.io  affects all sites (plugins, accounts, 
> stories, contributors, www, etc)

That’s an odd behaviour. I agree with you that these buttons should rather link 
to the subdomain’s homepage, instead of Jenkins.io.

> On 14. Dec 2023, at 23:51, 'Gavin Mogan' via Jenkins Developers 
>  wrote:
> 
> Does anyone have some strong opinions? Changing this to always go to 
> jenkins.io  affects all sites (plugins, accounts, 
> stories, contributors, www, etc)

-- 
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/6B4D2F4E-5886-4439-BA6F-2D7A4A638935%40notmyfault.dev.

Re: Adoption request sectioned-view-plugin

['Alexander Brandes' via Jenkins Developers]

Granted, welcome on board :)

> On 14. Dec 2023, at 13:55, Michał Smaga  wrote:
> 
> Link to a plugin you want to adopt: https://plugins.jenkins.io/sectioned-view/
> The status of the plugin ("for adoption" or "abandoned"): abandoned
> Link(s) to pull requests you want to deliver, if applicable: 
> https://github.com/jenkinsci/sectioned-view-plugin/pull/19
> Your GitHub username/id (e.g. oleg-nenashev for 
> https://github.com/oleg-nenashev/): mbSmaga
> Your Jenkins infrastructure account id. Create your account 
>  if you don’t have one.: mbSmaga
> The link to the "Repository Permission Updater" PR described below: 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3689
> 
> -- 
> 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/cf2947a8-3dc5-4c6e-9e5e-33ac7190310dn%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/23BA04C3-8A72-4BEE-BE18-56E99FC1C970%40notmyfault.dev.

Re: How to skip tests while generating build

['Alexander Brandes' via Jenkins Developers]

I would recommend against skipping unit tests. If your plugin has none yet, you will want to add at least one.On 13. Dec 2023, at 08:37, selvavi...@gmail.com  wrote:Hi Team,How to skip Jenkins to looking for Test reports while build. As I checked in this document , Add skip:true parameter in Jenkinsfile. Still no use. I am getting 12:07:46  ERROR: No test report files were found. Configuration error?I am looking to skip the JUnit test while building.Build consoleKindly assit.



-- 
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/76049930-b1c9-47cb-8a60-765ad53dfe65n%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/D3D86120-D28F-464F-872F-6BA241C78803%40notmyfault.dev.

Re: jenkins-2.426.2-rc-1 has been released

['Alexander Brandes' via Jenkins Developers]

For reference to the future release lead, make sure that the GitHub pre-release 
matches the template we use, because that’s the information posted on the 
community forums and mailing list ;)

> On 4. Dec 2023, at 02:20, Mark Waite  wrote:
> 
> I've installed it in my environment and have found no issues.  I'll continue 
> using it as my test configuration.
> 
> On Thursday, November 30, 2023 at 6:53:18 AM UTC-7 Kris Stern wrote:
> Other info relevant for the LTS 2.426.2 RC:
> 
> Please report issues found to this release candidate announcement thread.
> 
> Final release is scheduled for 2023-12-13.
> 
> -- 
> 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/9d5878bc-538b-4671-a42b-a484e03de83cn%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/16EE15BC-0454-4488-A1F5-CD84D87C4926%40notmyfault.dev.

Re: Adoption request flyway-runner-plugin

['Alexander Brandes' via Jenkins Developers]

Approved, thanks for adopting :)

> On 3. Dec 2023, at 09:35, Verachten Bruno  wrote:
> 
> +1 from me.
> Welcome!
> 
> On Sun, Dec 3, 2023, 08:54 Valentin Delaye (jonesbusy)  > wrote:
>> Link to a plugin you want to adopt: 
>> https://github.com/jenkinsci/flyway-runner-plugin
>> 
>> The status of the plugin ("for adoption" or "abandoned"): abandoned
>> 
>> Link(s) to pull requests you want to deliver, if applicable. Many PR not 
>> merged but I have grouped them in 
>> https://github.com/jenkinsci/flyway-runner-plugin/pull/23
>> 
>> Your GitHub username/id: jonesbusy
>> 
>> Your Jenkins infrastructure account id: jonesbusy
>> 
>> The link to the "Repository Permission Updater" PR described below: 
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3662
>> 
>> 
>> -- 
>> 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/e71b4aae-986b-432a-bfc8-a293829c2095n%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/CACtV%3Ddc5%2BeF30f%2B97u9zc4HLT_V3kZ4eST4RNROuJtF9EYqNNw%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/9F903183-EDDE-45D0-B8D1-1A3D4AD57D1D%40notmyfault.dev.

Re: [Information] 2FA will be enforced in jenkinsci organization

[Alexander Brandes]

Hey everyone,

GitHub reached out to us jenkinsci admins once again and shared, that they 
will roll out 2FA requirements for administrators of enterprises and 
organizations within the next wave.

Roughly 60% of users in scope have 2FA set up. 

We're on a good way to getting more and more people on board of 2FA :)

Cheers,
Alex
On Wednesday, 9 August 2023 at 10:27:06 UTC+2 Oleg Nenashev wrote:

> Thanks a lot for driving it! 
> +100 for going forward, though there are some GitHub bots to be affected. 
> Which is probably a good thing anyway
>
> On Friday, August 4, 2023 at 2:35:05 PM UTC+2 wfoll...@cloudbees.com 
> wrote:
>
>> Hello there,
>>
>> The jenkinsci administrators have recently received a message from 
>> GitHub, that will enforce 2FA setting for more people. It's not related to 
>> our settings but a process GitHub is pushing to enforce better security.
>>
>> The next wave will be for users who have published at least one release 
>> in the past. Also note that the scope will increase over time.
>>
>> For the jenkinsci organization, ~75% of users in scope have already the 
>> 2FA in place.
>>
>> You can read more about this in their blogpost from March 2023 
>> 
>> .
>>
>> Best regards,
>>
>> Wadeck Follonier
>> Jenkins Security 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/a1bf3e8e-5dca-47cf-aa8e-6cbe8d0bd02en%40googlegroups.com.

Re: Adoption request for postgresql-fingerprint-storage-plugin

['Alexander Brandes' via Jenkins Developers]

Granted.

> On 19. Nov 2023, at 19:12, Valentin Delaye (jonesbusy)  
> wrote:
> 
> Hi,
> 
> Sure thank you, there are few PR that need to be merged before doing a 
> release of the plugin.
> 
> I will take care of that when I get maintainer access.
> 
> Regards,
> 
> On Sunday, November 19, 2023 at 6:30:47 PM UTC+1 goun...@gmail.com 
>  wrote:
>> Hi Valentin,
>> 
>> Thank you so much for volunteering to become a maintainer for this plugin.
>> Once your official status is confirmed, could you please re-run PR
>> #260 
>> (https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin/pull/260)?
>> 
>> With the assistance of moderne.io/openrewrite 
>>  and the 'Improve a
>> Plugin' tutorial
>> (https://www.jenkins.io/doc/developer/tutorial-improve/), I've already
>> 'modernized' the plugin, so you won't need to do that.
>> 
>> Ooopsie, I've just seen that lots of the things I proposed in #260 are
>> already in #259. Oh well, I have a few more things. ;-)
>> 
>> Best regards,
>> Bruno
>> 
>> 
>> On Sun, Nov 19, 2023 at 1:23 PM Valentin Delaye (jonesbusy)
>> > wrote:
>> >
>> > Hi,
>> >
>> > I would like to adopt the postgresql-fingerprint-storage-plugin that was 
>> > implemented during one GSoC but never published to the release center (I 
>> > don't have the context).
>> >
>> > I started to use it with a real use case (like other database storage 
>> > plugin) and would like to adopt, refresh this plugin etc...
>> >
>> > Link to a plugin you want to adopt: 
>> > https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin
>> >
>> > The status of the plugin: abandonned
>> >
>> > Link(s) to pull requests you want to deliver, if applicable: 
>> > https://github.com/jenkinsci/postgresql-fingerprint-storage-plugin/pull/259
>> >  and some other
>> >
>> > Your GitHub username/id (jonesbusy)
>> >
>> > Your Jenkins infrastructure account id. jonesbusy
>> >
>> > The link to the "Repository Permission Updater" PR described below: 
>> > https://github.com/jenkins-infra/repository-permissions-updater/pull/3622
>> >
>> > Best regards,
>> >
>> > --
>> > 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/c5f21f77-47a7-477f-bd9a-b00e54ae18b4n%40googlegroups.com.
>> 
>> 
>> 
>> -- 
>> 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-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/21b2150b-4771-4fd0-ad01-821af262c144n%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/1DC7E6E9-8EC5-4CC5-9D11-13AEBFB6F1C9%40notmyfault.dev.

Re: Reporting documentation bug

['Alexander Brandes' via Jenkins Developers]

At the bottom of each page, there’s a “report page issue” button.

> On 11. Nov 2023, at 16:06, tzach solomon  wrote:
> 
> Hi,
> 
> I've noticed a documentation bug in the tutorial for creating a plugin 
> (https://www.jenkins.io/doc/developer/tutorial/create/)
> Where should I report it?
> 
> Thanks,
> Tzach
> 
> -- 
> 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/CAC19wgJZzopJBv17_rH34ujN27WpwY08w0VNEZpK-BUJt-AOwQ%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/1A6DF093-B428-449C-8E4D-F3D0B279E713%40notmyfault.dev.

Re: October 30, 2023 Governance Board Agenda

['Alexander Brandes' via Jenkins Developers]

A quick follow-up to the election: All roles have a nominee, and the nominee 
would serve in their nominated position.
All positions have a single nominee only, and therefore there's no need for a 
vote because the nominees are uncontested.

I'm unable to join the meeting today, unfortunately :/

~ Alex

> On 30. Oct 2023, at 18:04, Mark Waite  wrote:
> 
> News
> Jenkins elections 2023 nominations have closed - Alexander Brandes and Ulli 
> Hafner
>  <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
> Alexander Brandes and Ullrich Hafner run the officer and board elections for 
> 2023
> 57 registered voters
> Timeline
> Nominations are closed (September 18 - October 27)
> All roles have at least one nominee
> If role is uncontested, then no need to vote
> If candidates agree to accept the nomination and they are only nominee, then 
> they are elected
> Voter registration (September 18 - November 05)
> Voting (November 06 - December 1)
> Results announcement (December 11)
> Mark Waite submit jenkins.io <http://jenkins.io/> pull request to combine 
> subprojects and SIGs into a single concept - “working groups”
> More pull requests needed
> Retire the Chinese Jenkins site - deadline for 4 weeks to close (Kevin 
> Martens)
> Chinese site link removed from www.jenkins.io <http://www.jenkins.io/> header
> Kevin Martens (Docs Officer) tracking help desk ticket 
> <https://github.com/jenkins-infra/helpdesk/issues/3379> to replace the 
> Chinese pages with redirects to the English pages
> Need a redirect from https://www.jenkins.io/zh/ to https://www.jenkins.io/ 
> <https://www.jenkins.io/zh/>
> Kevin to work with the infrastructure team on the Helm charts implementing 
> the Chinese site
> Mark Waite draft a proposal to the board for license policy and phrasing 
> changes
> Discussed briefly at Linux Foundation Member Summit
> Linux Foundation legal team is willing to review proposal
> No further progress
> Allow other licenses like the JSON license
> Some other approach?
> What license should be used for a library plugin?
> License of the wrapped library (if wrapped library has no separate code, then 
> seems likely)
> MIT license as used by Jenkins plugins (if abstraction layer in the plugin, 
> then MIT for ours?)
> Review responses from other projects to license mixture (e.g. PyPI)
> Mostly focuses on OSI approved licenses but include a separate category for 
> other licenses
> Have categories for freeware, public domain, and more
> Reasonable precedent for allowing a wider range of licenses
> Needs more discussion, but being more permissive is working for PyPI
> Newer licenses may be more controversial
>  <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Community-activity>Community 
> activity
> Java 11, 17, and 21 in Jenkins - Mark Waite
> 2+2+2 Java support plan - Jenkins enhancement proposal 
> <https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11> 
> submitted
> Ready to assign a JEP number and mark as a Draft
> Mark Waite to assign the JEP and mark as a Draft
> Summary of discussions
> Jenkins developers mailing list 
> <https://groups.google.com/g/jenkinsci-dev/c/RaAloTTM9CQ/m/kag1KJSVAwAJ> - 
> quiet
> Jenkins users mailing list 
> <https://groups.google.com/g/jenkinsci-users/c/NGDRrNsaDYY/m/zj5RpSNSAQAJ> - 
> quiet
> Jenkins enhancement proposal 
> <https://github.com/MarkEWaite/jep/tree/java-adoption-plan/jep/#java-11> 
> - needs review
> Key dates
> Oct 3, 2023 - Java 11 end of life monitor visible in Jenkins weekly
> Nov 15, 2023 - Java 11 end of life monitor visible in Jenkins LTS
> 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
> Hacktoberfest nearing its end
> Jean-Marc Meessen message to developer list 
> <https://groups.google.com/g/jenkinsci-dev/c/wwtLLHNYAjo/m/ZcnRpsRUAAAJ>
> Friendly Jira issues list 
> <https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=19342>
> GitHub good first issues 
> <https://github.com/search?q=org%3Ajenkinsci+good-first-issues=issues>
> Infrastructure good first issues 
> <https://github.com/search?q=org%3Ajenkins-infra+good-first-issues=issues>
> Gitter requests that look for “where to start?”
>  <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Governance-Topics>Governance 
> Topics
> Board and officer elections - Alexander Brandes *
> 
> Processing the Azure credits donation - Mark Waite
> 
> Damien Duportal outlined alternatives in email message to the board
> Donation of Oracle Cloud costs by CloudBees - Mark Waite
> 

Re: Plug-in adoption

['Alexander Brandes' via Jenkins Developers]

Approved. Jenkinsfile modifications proposed without write permission to the 
repository aren’t considered by ci.jenkins.io  for 
security reasons :)

To access the Jira issue SECURITY-1025, please contact the security team: 
https://www.jenkins.io/security/cna/#contact

~ Alex

> On 30. Oct 2023, at 16:19, Jerome Lacoste  wrote:
> 
> Hello
> 
> I wish to adopt the batch-task plugin. 
> https://github.com/jenkinsci/batch-task-plugin/
> 
> Status is currently suspended due to a security issue.
> 
> https://plugins.jenkins.io/batch-task/
> 
> I made a few PRs. The build don't seem to pass as the changes are not pulled 
> on the CD environment. The build pass locally.
> 
> PRs I want to merge
> * https://github.com/jenkinsci/batch-task-plugin/pull/9
> * https://github.com/jenkinsci/batch-task-plugin/pull/10
> * https://github.com/jenkinsci/batch-task-plugin/pull/11
> 
> Github username: lacostej
> 
> Jenkins username: lacostej
> 
> link to the "Repository Permission Updater" PR  
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3594
> 
> 
> 
> 
> -- 
> 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/d69a85d5-b8b6-43e3-ad1f-a6013b9b7708n%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/C63CD2F8-9466-461B-9BA0-634B50172479%40notmyfault.dev.

Re: Request to adopt AccuRev plugin (up for adoption)

['Alexander Brandes' via Jenkins Developers]

Approved. Welcome aboard :)

> On 26. Oct 2023, at 17:49, Basil Crow  wrote:
> 
> +1, thank you for stepping up to maintain this plugin.
> 
> This plugin's build has not been updated in a long time, so you should
> expect to modernize some portions of the build before being able to do
> a release. See the tutorial here:
> 
> https://www.jenkins.io/doc/developer/tutorial-improve/
> 
> -- 
> 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/CAFwNDjq_qi1yb-JvcZwZK8tYV5T%2BcptJT3QVjv5k_7xgiwd8xw%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/B7CE7F76-D462-46FD-B086-C0B65911A3DC%40notmyfault.dev.

Re: Request to adopt groovy-events-listener-plugin (Up for adoption)

[Alexander Brandes]

Added.

On Tuesday, 17 October 2023 at 22:47:15 UTC+2 ray...@gmail.com wrote:

>
>- Link to a plugin you want to adopt: 
>https://github.com/jenkinsci/groovy-events-listener-plugin
>- The status of the plugin: up for adoption 
>- Link(s) to pull requests you want to deliver: 
>- https://github.com/jenkinsci/groovy-events-listener-plugin/pull/70
>- Your GitHub username/id: raymondwu1
>- Your Jenkins infrastructure account id: raymondwu
>- The link to the "Repository Permission Updater" PR: 
>https://github.com/jenkins-infra/repository-permissions-updater/pull/3572
>
> Requesting permissions for this repository since it is up for adoption and 
> incompatible with newer Jenkins LTS releases (> 2.249.3)
>
> Thanks!
>

-- 
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/5967779b-295c-4267-9896-0147c6e583ffn%40googlegroups.com.

Re: Adoption request extra-tool-installers-plugin

['Alexander Brandes' via Jenkins Developers]

Added.

> On 21. Oct 2023, at 12:42, Mark Waite  wrote:
> 
> +1 from me.  Thanks for being willing to adopt the plugin.
> 
> On Friday, October 20, 2023 at 11:33:45 PM UTC-6 jone...@gmail.com 
>  wrote:
>> Hi,
>> 
>> This is an adoption request for extra-tool-installers-plugin that is for 
>> adoption 
>> 
>> I would like to it refreshed, add test for JCasC and more test coverage
>> 
>> Planning to use it in real life specially for the retry installer
>> 
>> Link to a plugin you want to adopt 
>> https://github.com/jenkinsci/extra-tool-installers-plugin
>> The status of the plugin: abandoned
>> Link(s) to pull requests you want to deliver, if applicable: Not yet
>> Your GitHub username/id : jonesbusy
>> Your Jenkins infrastructure account id: jonesbusy
>> The link to the "Repository Permission Updater" PR described below: 
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3577
>> Regards,
> 
> 
> -- 
> 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/84a7bc0d-3bba-4688-bf7f-597fdf60ebe1n%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/1C907B3D-7110-4A52-8C48-AC83C670EE38%40notmyfault.dev.

Re: Mark Waite as release lead for 2.426.1?

[Alexander Brandes]

Don't hesitate to request me for a review :)

On Saturday, 21 October 2023 at 13:53:18 UTC+2 imon...@cloudbees.com wrote:

> +1
>
>
>
> El sáb, 21 oct 2023, 13:10, 'Bruno Verachten' via Jenkins Developers <
> jenkin...@googlegroups.com> escribió:
>
>> +1 of course!
>>
>> On Sat, Oct 21, 2023, 13:09 Kris Stern  wrote:
>>
>>> +1
>>> --
>>> *From:* jenkin...@googlegroups.com  on 
>>> behalf of Mark Waite 
>>> *Sent:* 21 October 2023 18:49
>>> *To:* Jenkins Developers 
>>> *Subject:* Mark Waite as release lead for 2.426.1? 
>>>  
>>> It has been quite a while since I last acted as a release lead for a 
>>> Jenkins LTS release.  I'd like to be the release lead for Jenkins 2.426.1.  
>>> Jenkins 2.426.1 is scheduled to release Nov 15, 2023. 
>>>
>>> I've been testing 2.426 in my development environment and am interested 
>>> in several of its changes.  Some of those changes include:
>>>
>>>- Removal of Prototype.js JavaScript library
>>>    - Addition of the Java 11 end of life Administrative Monitor
>>>- End of life for Red Hat Enterprise Linux 7 and its derivatives
>>>
>>>
>>> I'll need coaching and reviews from Kris Stern, Alexander Brandes, and 
>>> Tim Jacomb.
>>>
>>> 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-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/e739cb3f-dffc-4661-a498-7d85d791ec22n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/e739cb3f-dffc-4661-a498-7d85d791ec22n%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-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/OS3P286MB335379B78EED60C8E3438952A1DAA%40OS3P286MB3353.JPNP286.PROD.OUTLOOK.COM
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/OS3P286MB335379B78EED60C8E3438952A1DAA%40OS3P286MB3353.JPNP286.PROD.OUTLOOK.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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFbR2rqAw1jA%3DVjW1nxWvQWm2nHY0QtVdKE%3DC4%2Bw8Q0wJcSOsA%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFbR2rqAw1jA%3DVjW1nxWvQWm2nHY0QtVdKE%3DC4%2Bw8Q0wJcSOsA%40mail.gmail.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/cd48c36a-e726-49a4-8a1e-eb96cfdfdae4n%40googlegroups.com.

Re: Jenkins Board and Officer Elections 2023 started: Nomination of candidates & Voter registration is now open

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

Nomination for the two governance board and five officer positions (Security, 
Events, Release, Infrastructure, and Documentation), closes soon, on October 27.

If you want to nominate someone and haven't done that yet, please finish that 
by October 27, by sending a message to the election-committee 
<https://community.jenkins.io/g/election-committee> group on the Jenkins 
community forums <https://community.jenkins.io/>. Self nomination is allowed.
Take a look at the guide 
<https://www.jenkins.io/project/election-walkthrough/#joining-the-community-forums>
 on how to send a nomination to the election committee.

The candidates are announced on November 06, the same day the voting starts.

Best regards,
Alex

> On 18. Sep 2023, at 12:19, Alexander Brandes  wrote:
> 
> Hey everyone,
> 
> The annual Jenkins governance board and officer elections have started.
> Up for election are two governance board positions, and all five officer 
> positions (Security, Events, Release, Infrastructure, and Documentation).
> 
> For more information about the annual Jenkins election, visit this year's 
> announcement blogpost 
> <https://www.jenkins.io/blog/2023/09/18/board-officer-election-announcement/> 
> and the nomination, voter sign-up and ranking walkthrough 
> <https://www.jenkins.io/project/election-walkthrough/>.
> 
> We invite community members to nominate candidates by sending a message to 
> the election-committee <https://community.jenkins.io/g/election-committee> 
> group on the Jenkins community forums <https://community.jenkins.io/>, to 
> shape the future of the project.
> 
> Nomination is open, and will end on October 27. Anyone can nominate anyone.
> 
> This is a tremendous opportunity for community members to influence the 
> direction of the project.
> 
> We ask all community members who are interested in voting, to join the 
> election-voter-2023 <https://community.jenkins.io/g/election-voter-2023> 
> group on the Jenkins community forums during the registration period.
> Take a look at the guide 
> <https://www.jenkins.io/project/election-walkthrough/#voting> on how to do 
> that.
> Previous elections utilized their groups, so joining the election-voter-2023 
> group is required for participation.
> If you've contributed at least 1 time to Jenkins before September 1, 2023, 
> 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.
> 
> Voter registration is open, and will end on November 05.
> 
> If you encounter issues or technical difficulties with any step of the 
> election process, don’t hesitate to message the election committee 
> <https://community.jenkins.io/g/election-committee>.
> 
> Best regards,
> Alexander Brandes, for the Jenkins Governance Board
> 

-- 
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/55F82370-C1E5-42D4-B65F-67356893F8B7%40notmyfault.dev.

Re: Backporting for LTS 2.414.3 has started

['Alexander Brandes' via Jenkins Developers]

Packaging happens from the versioned stable-2.414 branch.There's a stable- branch for every recent LTS release.On 17. Oct 2023, at 21:59, Mark Waite  wrote:On Monday, October 16, 2023 at 7:05:03 PM UTC-6 Mark Waite wrote:On Friday, October 13, 2023 at 9:42:27 AM UTC-6 Alexander Brandes wrote:I would like to propose backporting a documentation change [0], ensuring the installation pages match the instructions on jenkins.io.I am "+1" for the documentation backport.Kevin and I investigated and as far as we can tell, a backport is not needed because the master branch is used for packaging.  There are no recent stable-xxx branches in the packaging repository.When the build runs tomorrow, the LTS documentation for Debian on https://pkg.jenkins.io/debian-stable/ will be updated to match the weekly documentation.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/d396-6c64-4e96-904c-c7656f580a01n%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/686B2E31-9960-4ACD-B885-65494DEF1854%40notmyfault.dev.

Re: Two week break in LTS schedule at end of 2023

[Alexander Brandes]

Within the corrections, I'm +1 still :)

On Monday, 16 October 2023 at 17:33:48 UTC+2 Mark Waite wrote:

> Sad that I made so many date related mistakes in a mail message focused on 
> dates.  Corrections below:
>
> On Monday, October 16, 2023 at 8:12:50 AM UTC-6 Mark Waite wrote:
>
> I've been assuming a two week break in the LTS schedule at the end of 2023 
> as we've done in the past.  That assumption is embedded in the Jenkins 
> enhancement proposal for the 2+2+2 Java Support Plan 
> 
> .
>
> The dates with a two week break would be:
>
>
>- 
>
>Nov 15, 2023 - Jenkins 2.426.1 release
>- 
>
>Dec 13, 2024 - Jenkins 2.426.2 release
>
>
> * Dec 13, *2023* - Jenkins 2.426.2 release
>  
>
>
>- 
>
>Jan 24, 2024 - Jenkins 2.426.3 release (assuming two week skip for 
>holidays
>
>
> With that two week break, Oct 2, 2023 would be the last LTS version to 
> support Java 11, with the first LTS version to require Java 17 on Oct 30, 
> 2024.
>
>
> With that two week break, *Oct 2, 2024* would be the last LTS version to 
> support Java 11, with the first LTS version to require Java 17 on Oct 30, 
> 2024.
>  
>
> The two week break also makes it easier for those who are taking time off 
> at the end of the year.
>
> Are there strong objections to the Jenkins project taking the customary 
> two week break at the end of the 2023 calendar year? Weekly releases will 
> continue during that time, but the time between 2.426.2 and 2.426.3 will 
> increase from 4 weeks to 6 weeks.
>
>
>  
>

-- 
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/c6fba38e-23ee-476a-a299-782be1cc6ca7n%40googlegroups.com.

Re: Backporting for LTS 2.414.3 has started

['Alexander Brandes' via Jenkins Developers]

I would like to propose backporting a documentation change [0], ensuring the 
installation pages match the instructions on jenkins.io .

Additionally, a remoting PR has been labeled as “backporting-candidate”.

[0] https://github.com/jenkinsci/packaging/pull/435
[1] https://github.com/jenkinsci/remoting/pull/675

> On 2. Oct 2023, at 14:36, Kris Stern  wrote:
> 
> Yes, my apologies, should be something like 
> https://issues.jenkins.io/issues/?jql=labels%20%3D%202.414.3-fixed instead, 
> otherwise the first issue looks like they don't belong. 
> 
> Best,
> Kris
> From: 'Jesse Glick' via Jenkins Developers 
> Sent: 02 October 2023 19:50
> To: jenkinsci-dev@googlegroups.com 
> Subject: Re: Backporting for LTS 2.414.3 has started
>  
> On Mon, Oct 2, 2023 at 1:49 AM Kris Stern  > wrote:
> Fixed: 
> https://issues.jenkins.io/browse/JENKINS-71479?jql=labels%20%3D%202.414.3-fixed
> 
> I think you meant to link to 
> https://issues.jenkins.io/issues/?jql=labels%20%3D%202.414.3-fixed ? 
> -- 
> 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/CANfRfr1Jdikfn8nTNjYaVu-zih0m9Nzv3JTLiuei-WFy_AcssA%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/OS3P286MB14314EC918E02F8A6779B887A1C5A%40OS3P286MB1431.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/34CD8CDC-C3FE-4581-97EE-2E40544FF027%40notmyfault.dev.

Re: Proposal: Kris Stern to join the release team

[Alexander Brandes]

With the approval of the release officer, I've added you to the release 
team in the jenkinsci organization.

To join the release team in the infra org, please file a helpdesk issue, I 
can't add you there.

Welcome aboard :)

On Monday, 9 October 2023 at 12:06:28 UTC+2 timja...@gmail.com wrote:

> Approved
>
> On Mon, 9 Oct 2023 at 10:21, Oleg Nenashev  wrote:
>
>> +1
>>
>> On Wednesday, October 4, 2023 at 1:30:04 PM UTC+2 stephan...@gmail.com 
>> wrote:
>>
>>> +1 from me, good work Kris
>>>
>>> Le lun. 2 oct. 2023 à 19:57, 'Kevin Martens' via Jenkins Developers <
>>> jenkin...@googlegroups.com> a écrit :
>>>
 +1 from me too!

 On Mon, Oct 2, 2023 at 1:40 PM Basil Crow  wrote:

> +1
>
> On Mon, Oct 2, 2023 at 5:06 AM Hervé  wrote:
>
>> FWIW, +1 from me too!
>>
>> -- 
>> 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/CAE1M8%2B9yQf3YzbEPkv%3DnAEQyPFoihRJL5cWGi6myVzwqM9EzZQ%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/CAFwNDjr3h1gnWGTSP0hfwVHd0-VWWA%3DYW_fnvQLr5VAume03Nw%40mail.gmail.com
>  
> 
> .
>


 -- 
 Kevin Martens
 Technical Content Developer
 CloudBees, Inc.


 E: kmar...@cloudbees.com

 Pronouns: He/Him/His

 -- 
 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/CAP92yNdo8EE7KMWRrXMiTbZO3QMEHhcMc_v%3DD3%2BdQ_Ss2VU70g%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/8a9b4429-8517-4ddf-befd-e1c94698c73fn%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/a2ab3480-5647-40b0-8b6d-e0ab0dbf099dn%40googlegroups.com.

Re: 2.426 as Nov 15, 2023 LTS baseline?

['Alexander Brandes' via Jenkins Developers]

+1 from me

> On 4. Oct 2023, at 06:14, Mark Waite  wrote:
> 
> Wednesday, 4 Oct 2023 is listed as the day when we select the baseline for 
> the long term support release that will be delivered November 15, 2023.
> 
> I propose Jenkins 2.426  as the 
> next LTS baseline.  It removes Prototype.js from Jenkins core and adds the 
> Java 11 end of life administrative monitor to warn users that Jenkins will no 
> longer support Java 11 after September 30, 2024.
> 
> I've updated my development environment to run Jenkins 2.426 with JDK 21.  
> I've found no issues in the testing that I've performed.
> 
> 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/b32ddc69-d333-4b04-aedb-ac491b6a49ebn%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/E49E1048-D58E-4A67-956B-DCF7C7690E63%40notmyfault.dev.

Re: October 2, 2023 Governance Board Agenda

[Alexander Brandes]

Unfortunately, I can't make it today :(

On Monday, 2 October 2023 at 19:19:03 UTC+2 Mark Waite wrote:

> Agenda
>
>  Comment
> <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#News>News
>
>- Jenkins elections 2023 nominations in progress - Alexander Brandes 
>and Ulli Hafner
>   - Announced by blog post 
>   
> <https://www.jenkins.io/blog/2023/09/18/board-officer-election-announcement/>
>   , community post 
>   
> <https://community.jenkins.io/t/jenkins-board-and-officer-election-2023/9644>
>   , tweet <https://twitter.com/jenkinsci/status/1703772922593132972>, 
>   LinkedIn 
>   
> <https://www.linkedin.com/feed/update/urn:li:activity:7109540080251244546>, 
>   and jenkins-infra <https://github.com/jenkins-infra>
>- Cloudflare sponsors Jenkins project
>   - Project to host update center content on Cloudflare R2 buckets 
>   worldwide
>  - Reduce AWS costs for the Jenkins project
>   - Java 21 released <https://openjdk.org/projects/jdk/21/> September 
>19, 2023
>   - Summary blog post with Java 11 end of life, Java 21 support, Java 
>   17 …
>  - Basil willing to create that blog post when ready
>   - Prototype.js will be removed from Jenkins 2.426 
><https://www.jenkins.io/blog/2023/05/12/removing-prototype-from-jenkins/> 
> 3 
>Oct 2023
>   - 6 months of work <https://issues.jenkins.io/browse/JENKINS-70906> 
> from 
>   Tim Jacomb, Basil Crow, and many others
>   - Google sheet 
>   
> <https://docs.google.com/spreadsheets/d/1dpaKALZaK0_HIGy6ony3wnegr1frTg3u1lngG4KdoC8/edit#gid=0>
>  shows 
>   good status
>   - Exceptions mostly from plugins that integrate to company services 
>   and are maintained by the company providing the service
>  - JFrog Artifactory plugin 
>  <https://issues.jenkins.io/browse/JENKINS-71671> not yet 
>  released - 23k installs
>  - CyberRes Fortify plugin 
>  <https://issues.jenkins.io/browse/JENKINS-71303> not yet 
>  released - 4k installs
>  - XRay test management plugin 
>  <https://github.com/jenkinsci/xray-connector-plugin/issues/75> not 
>  yet released - 2k installs
>  - Synopsys Coverity plugin 
>  <https://issues.jenkins.io/browse/JENKINS-71308> not yet 
>  released - 1.5k installs
>  - Tricentis qTest plugin 
>  <https://issues.jenkins.io/browse/JENKINS-71309> not yet 
>  released - 1.3k installs
>  - OpenStack Cloud 
>  <https://issues.jenkins.io/browse/JENKINS-71310> fixed but 
>  unreleased - 900 installs
>   - Next LTS baseline selected Wednesday 4 Oct 2023
>   - Jenkins 2.426 expected to be a good choice for 15 Nov 2023 LTS
>- Google Summer of Code projects 
><https://www.jenkins.io/projects/gsoc/#gsoc-2023> for 2023
>   - 4 completed successfully
>  - GitLab plugin modernization 
>  
> <https://www.jenkins.io/projects/gsoc/2023/projects/gitlab-plugin-modernization>
>  - Docker compose for tutorials 
>  
> <https://www.jenkins.io/projects/gsoc/2023/projects/docker-compose-build>
>  - Adding probes to plugin health score 
>  
> <https://www.jenkins.io/projects/gsoc/2023/projects/add-probes-to-plugin-health-score>
>  - Building jenkins.io with alternate tools 
>      
> <https://www.jenkins.io/projects/gsoc/2023/projects/alternative-jenkinsio-build-tool>
>   - Prototype.js removed from Jenkins core Oct 3, 2023
>- Java 11 end of life monitor enabled Oct 3, 2023 - end of life Oct 
>31, 2024
>
> <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items
>
>- Alexander Brandes and Ullrich Hafner run the officer and board 
>elections for 2023
>   - Timeline
>  - Nomination of candidates (September 18 - October 27)
>  - Voter registration (September 18 - November 05)
>  - Voting (November 06 - December 1)
>  - Results announcement (December 11)
>   - Alexander Brandes documented how to nominate someone 
>   <https://www.jenkins.io/project/election-walkthrough/>, and how 
>   CIVS works 
>   <https://www.jenkins.io/project/election-walkthrough/#voting>; both 
>   for voters and the election committee
>- Mark Waite retrospective on signing certificate renewal process 
>
> <https://docs.google.com/document/d/1BB2TueNTLhK3TcJ5senSSSMdzy9D95DxPXuWNzL3k2s/edit#>
>  and 
>its

Proposal: Kris Stern to join the release team

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

I would like to propose Kris Stern (@krisstern ) 
to join the release team.

I have assisted them during their past releases 

 as lead and would welcome an addition to the release team on GitHub.

They have signed an ICLA too.

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/572E9F9E-4A7A-47CC-8317-886F38702C04%40notmyfault.dev.

Re: Add a co-maintainer for the Startup Trigger Plugin

[Alexander Brandes]

Approved.

On Friday, 22 September 2023 at 15:06:58 UTC+2 goun...@gmail.com wrote:

> Hi,
>
> This is a request to add me (@gounthar on GitHub, @poddingue on
> Jenkins) as a co-maintainer to the Startup Trigger Plugin.
>
> Link to a plugin you want to co-maintain:
> https://github.com/jenkinsci/startup-trigger-plugin
>
> The status of the plugin ("for adoption" or "abandoned"): no such status
>
> Link(s) to pull requests you want to deliver, if applicable:
> https://github.com/jenkinsci/startup-trigger-plugin/pull/8
>
> Your GitHub username/id: gounthar
>
> Your Jenkins infrastructure account id: poddingue
>
> The link to the "Repository Permission Updater" PR:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3542
>
> Thanks!
>
> -- 
> 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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9c54fa0d-ff74-4ff4-a720-69503a62f55bn%40googlegroups.com.

Re: Request to adopt github-scm-trait-notification-context-plugin (abandoned)

[Alexander Brandes]

Approved.

On Saturday, 23 September 2023 at 00:14:46 UTC+2 Ross Bender wrote:

>
>- Link to a plugin I want to adopt: 
>https://github.com/jenkinsci/github-scm-trait-notification-context-plugin
>- The status of the plugin: abandoned
>- Link(s) to pull requests I want to deliver:
>   - 
>   
> https://github.com/jenkinsci/github-scm-trait-notification-context-plugin/pull/3
>   - 
>   
> https://github.com/jenkinsci/github-scm-trait-notification-context-plugin/pull/5
>   - 
>   
> https://github.com/jenkinsci/github-scm-trait-notification-context-plugin/pull/7
>- GitHub username/id: l3ender
>- Jenkins infrastructure account id: l3ender
>- The link to the "Repository Permission Updater" PR: 
>https://github.com/jenkins-infra/repository-permissions-updater/pull/3543
>
> I am requesting permission for this repository because the plugin is 
> abandoned. The maintainer has not responded to comments/pull requests, some 
> of which are over 3 years old. There are multiple features submitted as PRs 
> from various users which I would like to deliver to enhance this plugin's 
> functionality.
>
> Thank you!
>
>

-- 
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/6051e216-f876-4148-bc97-39937af0447dn%40googlegroups.com.

Re: Release lead for LTS 2.414.3

[Alexander Brandes]

+1

On Monday, 25 September 2023 at 21:09:49 UTC+2 kris...@outlook.com wrote:

> Hi everyone,
>
> I would like to volunteer to be the Release Lead for LTS 2.414.3.
>
> Planned dates can be seen on the event calendar: 
> https://www.jenkins.io/events/#event-calendar 
>
>
>- Release candidate by October 4th
>- Release on October 18th
>
>
> The documentation is at:
>
> https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
>
> We will chat in https://app.gitter.im/#/room/#jenkins-release:matrix.org 
> or on the bridged matrix channel.
>
> Thanks,
> Kris
>

-- 
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/c68d09fd-fd06-4c3f-a6ed-2927ef5ae440n%40googlegroups.com.

Re: CD release failed: Could not transfer artifact...from repo.jenkins-ci.org...Connection reset

['Alexander Brandes' via Jenkins Developers]

Hey,

I’ve triggered the action again with a successful result. I would blame this 
one time issue on GitHub actions, given the step is successful on ci.jenkins.io 
 and locally on my machine.

Best,
Alex (NotMyFault)

> On 24. Sep 2023, at 20:53, Ross Bender  wrote:
> 
> I am doing my first CD release for a plugin and saw the following error when 
> the maven-cd / release action ran:
> 
> [INFO] --- maven-hpi-plugin:3.48:resolve-test-dependencies 
> (default-resolve-test-dependencies) @ github-scm-trait-notification-context 
> ---
> 
> [INFO] 
> 
> 
> [INFO] BUILD FAILURE
> 
> [INFO] 
> 
> 
> [INFO] Total time: 04:07 min
> [INFO] Finished at: 2023-09-24T18:42:48Z
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.jenkins-ci.tools:maven-hpi-plugin:3.48:resolve-test-dependencies 
> (default-resolve-test-dependencies) on project 
> github-scm-trait-notification-context: Failed to resolve artifacts: 
> com.coravy.hudson.plugins.github:github:hpi:1.37.3, 
> io.jenkins.plugins.mina-sshd-api:mina-sshd-api-common:hpi:2.10.0-69.v28e3e36d18eb_,
>  
> io.jenkins.plugins.mina-sshd-api:mina-sshd-api-core:hpi:2.10.0-69.v28e3e36d18eb_,
>  io.jenkins.plugins:caffeine-api:hpi:3.1.8-133.v17b_1ff2e0599, 
> io.jenkins.plugins:commons-lang3-api:hpi:3.13.0-62.v7d18e55f51e2, 
> io.jenkins.plugins:jakarta-activation-api:hpi:2.0.1-3, 
> io.jenkins.plugins:jakarta-mail-api:hpi:2.0.1-3, 
> io.jenkins.plugins:javax-activation-api:hpi:1.2.0-6, 
> io.jenkins.plugins:jaxb:hpi:2.3.8-1, 
> io.jenkins.plugins:jjwt-api:hpi:0.11.5-77.v646c772fddb_0, 
> io.jenkins.plugins:okhttp-api:hpi:4.11.0-157.v6852a_a_fa_ec11, 
> io.jenkins.plugins:snakeyaml-api:hpi:1.33-95.va_b_a_e3e47b_fa_4, 
> org.jenkins-ci.modules:instance-identity:hpi:173.va_37c494ec4e5, 
> org.jenkins-ci.plugins.workflow:workflow-api:hpi:1281.vca_5fddb_3fceb_, 
> org.jenkins-ci.plugins.workflow:workflow-scm-step:hpi:415.v434365564324, 
> org.jenkins-ci.plugins.workflow:workflow-step-api:hpi:639.v6eca_cd8c04a_a_, 
> org.jenkins-ci.plugins.workflow:workflow-support:hpi:865.v43e78cc44e0d, 
> org.jenkins-ci.plugins:apache-httpcomponents-client-4-api:hpi:4.5.14-208.v438351942757,
>  org.jenkins-ci.plugins:bouncycastle-api:hpi:2.29, 
> org.jenkins-ci.plugins:credentials-binding:hpi:636.v55f1275c7b_27, 
> org.jenkins-ci.plugins:credentials:hpi:1271.v54b_1c2c6388a_, 
> org.jenkins-ci.plugins:display-url-api:hpi:2.3.9, 
> org.jenkins-ci.plugins:git-client:hpi:4.5.0, 
> org.jenkins-ci.plugins:git:hpi:5.2.0, 
> org.jenkins-ci.plugins:github-api:hpi:1.314-431.v78d72a_3fe4c3, 
> org.jenkins-ci.plugins:github-branch-source:hpi:1741.va_3028eb_9fd21, 
> org.jenkins-ci.plugins:jackson2-api:hpi:2.15.2-350.v0c2f3f8fc595, 
> org.jenkins-ci.plugins:mailer:hpi:463.vedf8358e006b_, 
> org.jenkins-ci.plugins:plain-credentials:hpi:143.v1b_df8b_d3b_e48, 
> org.jenkins-ci.plugins:scm-api:hpi:676.v886669a_199a_a_, 
> org.jenkins-ci.plugins:script-security:hpi:1275.v23895f409fb_d, 
> org.jenkins-ci.plugins:ssh-credentials:hpi:308.ve4497b_ccd8f4, 
> org.jenkins-ci.plugins:structs:hpi:325.vcb_307d2a_2782, 
> org.jenkins-ci.plugins:token-macro:hpi:384.vf35b_f26814ec, 
> org.jenkins-ci.plugins:trilead-api:hpi:2.84.v72119de229b_7: Could not 
> transfer artifact 
> io.jenkins.plugins.mina-sshd-api:mina-sshd-api-common:hpi:2.10.0-69.v28e3e36d18eb_
>  from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): GET 
> request of: 
> io/jenkins/plugins/mina-sshd-api/mina-sshd-api-common/2.10.0-69.v28e3e36d18eb_/mina-sshd-api-common-2.10.0-69.v28e3e36d18eb_.hpi
>  from repo.jenkins-ci.org failed: Connection reset -> [Help 1]
> 
> The link to the action is here: 
> https://github.com/jenkinsci/github-scm-trait-notification-context-plugin/actions/runs/6291771195/job/17080473281.
> 
> Can someone take a look into this issue?
> 
> Once resolved, how do I proceed to retrigger the release?
> 
> Thanks!
> 
> -- 
> 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/91243e16-c414-4dcc-b0fe-8488435c3e04n%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 

Jenkins Board and Officer Elections 2023 started: Nomination of candidates & Voter registration is now open

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

The annual Jenkins governance board and officer elections have started.
Up for election are two governance board positions, and all five officer 
positions (Security, Events, Release, Infrastructure, and Documentation).

For more information about the annual Jenkins election, visit this year's 
announcement blogpost 
<https://www.jenkins.io/blog/2023/09/18/board-officer-election-announcement/> 
and the nomination, voter sign-up and ranking walkthrough 
<https://www.jenkins.io/project/election-walkthrough/>.

We invite community members to nominate candidates by sending a message to the 
election-committee <https://community.jenkins.io/g/election-committee> group on 
the Jenkins community forums <https://community.jenkins.io/>, to shape the 
future of the project.

Nomination is open, and will end on October 27. Anyone can nominate anyone.

This is a tremendous opportunity for community members to influence the 
direction of the project.

We ask all community members who are interested in voting, to join the 
election-voter-2023 <https://community.jenkins.io/g/election-voter-2023> group 
on the Jenkins community forums during the registration period.
Take a look at the guide 
<https://www.jenkins.io/project/election-walkthrough/#voting> on how to do that.
Previous elections utilized their groups, so joining the election-voter-2023 
group is required for participation.
If you've contributed at least 1 time to Jenkins before September 1, 2023, 
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.

Voter registration is open, and will end on November 05.

If you encounter issues or technical difficulties with any step of the election 
process, don’t hesitate to message the election committee 
<https://community.jenkins.io/g/election-committee>.

Best regards,
Alexander Brandes, for the Jenkins Governance Board

-- 
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/FFB403FA-E495-4AF5-8E5C-16D3F471659A%40notmyfault.dev.

Re: SECURITY-3153 / CVE-2023-40347 - Request Access

['Alexander Brandes' via Jenkins Developers]

Hey Stephan,

In case you cannot access SECURITY-3153 [1], I recommend to contact [2] the 
Jenkins security team and ask for an assignment of “phreakadelle” to 
SECURITY-3153.

Given your username is listed as maintainer in the repository permission 
updater [3], you are an eligible to be added to the issue.

Best regards,
Alex

[1] https://issues.jenkins.io/projects/SECURITY/issues/SECURITY-3153 
[2] https://www.jenkins.io/security/cna/#contact 
[3] 
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-maven-artifact-choicelistprovider.yml
 

> On 2. Sep 2023, at 13:04, Stephan Watermeyer  wrote:
> 
> Hey, need some support to fix the security issue: SECURITY-3153 / 
> CVE-2023-40347
> 
> I am the developer of the plugin "maven-artifact-choicelistprovider" and need 
> some details on that bug. I can login to JIRA with my user "phreakadelle" but 
> i dont see any assigned issue to me in the SECURITY project. I've checked the 
> permissions and emails between GitHub and JIRA, but its all set up correctly.
> 
> Would be great if someone could help me to SEE the issue in JIRA and i hope 
> that one contains the information i need to fix the issue.
> 
> Thanks for your support
> 
> -- 
> 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/bc4a7a51-bfa3-4eaa-bee3-84e28247897an%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/42761480-094A-451B-90DB-9A01C48DA4A2%40notmyfault.dev.

Re: Renaming the plugin and repo

['Alexander Brandes' via Jenkins Developers]

You can change the name of the GitHub repository and friendly name ( in 
the pom.xml) for sure. GitHub handles redirects. You may change them in 
documentation sources, such as the README.md too, if applicable.
Renaming the GitHub repository is achieved by opening a pull request, modifying 
your permission file at the repository permission updater 
(https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-redhat-codeready-dependency-analysis.yml).

Changing the plugin ID is not possible at this state anymore.

Best regards,
Alex

> On 23. Aug 2023, at 18:51, Vladimir Belousov  wrote:
> 
> Hi,
> We are working on plugin 
> https://plugins.jenkins.io/redhat-codeready-dependency-analysis/
> 
> For some reason, we want to rename the plugin and change the repository name 
> where it is hosted
> 
> Will it work?
> What are the possible side effects?
> 
> Thanks!
> 
> -- 
> 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/0ccc74b5-d410-4ce3-a76a-e684f1193f13n%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/2597D663-338D-4DAD-A996-42325E315D30%40notmyfault.dev.

Opportunity to be the release lead for 2.414.2

['Alexander Brandes' via Jenkins Developers]

Hello

Is anyone interested in being the release lead for the upcoming 2.414.2 LTS 
release?

Planned dates can be seen on the event calendar: 
https://www.jenkins.io/events/#event-calendar
The release candidate is scheduled for the 6th of September
The final release is scheduled for the 20th of September

The documentation is at:
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

Past release leads will be available to answer any questions and provide 
guidance.

We chat in jenkins-release:matrix.org  
(https://app.gitter.im/#/room/%23jenkins-release:matrix.org)

If anyone is interested, don’t hesitate to respond. That’s your shot, newbies 
are welcome too :)

BR
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/0B4148BE-38D3-4901-8711-2BE351CE8A58%40notmyfault.dev.

Re: [ci.jenkins.io] JDK21 availability

['Alexander Brandes' via Jenkins Developers]

Thanks for providing this opportunity. Starting with 
https://github.com/jenkinsci/jenkins/pull/8361, Jenkins core is now built on 
Java 11, 17 and 21 (with a successful initial build on 21 \o/)


> On 11. Aug 2023, at 22:11, Basil Crow  wrote:
> 
> Thanks! This was already very helpful as it enabled me to file JENKINS-71805 
> .
> 
> -- 
> 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/CAFwNDjrM_aLAG3GSVzo_Z90ig7dWE7DvTLpJ9oPPt09ZhdmkoQ%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/E0FC65E0-2A0C-44DD-B973-46DF2D7D2CE1%40notmyfault.dev.

[Information] Change of infrastructure and release team chat channels from IRC to Matrix

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

The location of the Jenkins infrastructure and release team chat channels have 
changed.

In case you have used the IRC channels #jenkins-infra and #jenkins-release on 
Libera.chat before, please ensure you join the Matrix rooms 
#jenkins-infra:matrix.org  and #jenkins-release:matrix.org 
 to keep the communication up.

If you like, you can use the Element web client hosted by Gitter to access the 
infrastructure (https://app.gitter.im/#/room/%23jenkins-infra:matrix.org) and 
release (https://app.gitter.im/#/room/%23jenkins-release:matrix.org) chat the 
same way you can access all other channels in the Jenkins space 
(https://app.gitter.im/#/room/%23jenkins-ci:matrix.org).
But you can use any client or service supporting Matrix if you like.

Best regards,
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/7D6E1C61-8B20-4F37-AA61-891A1D196D5B%40notmyfault.dev.

Backporting for LTS 2.414.1 started

['Alexander Brandes' via Jenkins Developers]

Hey everyone,

Backporting for 2.414.1 has started, and the release candidate (RC) is 
scheduled for 2023-08-09.

Candidates: https://issues.jenkins.io/issues/?filter=12146
Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.414.1-fixed
Rejected: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.414.1-rejected

Best regards,

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/38FFFE34-B8A3-494F-B8A1-7B195D1AD4DA%40notmyfault.dev.

2.414.1 Release Lead

[Alexander Brandes]

Hey everyone,

I am volunteering to be the release lead for the upcoming LTS release, 
2.414.1.

The RC is scheduled for the 9th of August, final release for the 23rd of 
August.

BR,
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/d370edd0-b0e9-4dc0-8f95-52ed84b0b9e4n%40googlegroups.com.

Re: Jenkins 2.413 as next LTS baseline?

[Alexander Brandes]

Alternatively, 2.417 could be a viable candidate, as it includes the 
security fix, and could include both regression fixes for JENKINS-71698 
 and JENKINS-71699 
, if reviewed within the 
next week.
Thanks to Tim and Markus for filing the couple of PRs so quick!

On Monday, 24 July 2023 at 16:43:05 UTC+2 timja...@gmail.com wrote:

> Ah I see I missed that 2.415 was out.
>
> Let’s continue with 2.414 and backport security fixes
>
> On Mon, 24 Jul 2023 at 15:41, 'jn...@cloudbees.com' via Jenkins 
> Developers  wrote:
>
>> >  2.415 appears to have a regression in the dialog handling that I just 
>> found with a minimal amount of testing, so possibly too new to have had 
>> exposure  :-(
>> https://issues.jenkins.io/browse/JENKINS-71699
>>
>> On Monday, July 24, 2023 at 3:31:21 PM UTC+1 jn...@cloudbees.com wrote:
>>
>>> Thanks Tim & Basil for continuing this.
>>>
>>> I filed https://issues.jenkins.io/browse/JENKINS-71698 for LTS tracking 
>>> and tagged the jenkins PR 
>>>  
>>>
>>> >  Shall we go with 2.415 instead as it will have security fixes 
>>>
>>> not sure I follow 2.415 is not a security release?  are you meaning 
>>> 2.416 which will be the security release which will naturally contain the 
>>> 2.415 bits?
>>>
>>> 2.415 *appears* to have a regression in the dialog handling that I just 
>>> found with a minimal amount of testing, so possibly too new to have had 
>>> exposure  :-(
>>> On Monday, July 24, 2023 at 2:29:46 PM UTC+1 timja...@gmail.com wrote:
>>>
 Shall we go with 2.415 instead as it will have security fixes (given 
 they would be backported anyway, it's less confusing if we start with the 
 version they were introduced in I think)?

 The plugin manager bug in 2.414 has been fixed.

 On Sat, 22 Jul 2023 at 00:21, Basil Crow  wrote:

> On Fri, Jul 21, 2023 at 10:42 AM 'jn...@cloudbees.com' via Jenkins
> Developers  wrote:
> > 2.414 has a regression in the plugin manager.
> > I would be -1 on this unless that is fixed (currently missing a 
> Jenkins bug but has been the cause of a lot of ATH failures)
> > https://github.com/jenkinsci/acceptance-test-harness/issues/1284 
> for the current status/investigation, I will file a Jenkins bug on Monday 
> to track.
>
> Thanks for starting to investigate this. As I wrote in the discussion
> at jenkinsci/acceptance-test-harness#1284, I was able to definitively
> implicate jenkinsci/jenkins#8025 as the cause of the ATH test failure
> by widening the race window with some sleeps, and I may have been able
> to chase away the ATH test failure and/or fix the bug by removing the
> asynchrony from the original change.
>
> Since jenkinsci/jenkins#8025 was the last commit in 2.414 and since
> 2.414 contains some other changes that we want, I would like to
> propose that we keep 2.414 as the next LTS baseline but simply revert
> jenkinsci/jenkins#8025 from the stable branch before shipping. (An
> equally plausible alternative would be to choose 2.413 and backport
> the other changes that we want.)
>
> As far as the main branch is concerned, now that I have come up with a
> way to reproduce the original problem, I would like to propose that we
> give folks a limited amount of time (say, a week) to come up with a
> solution and otherwise revert jenkinsci/jenkins#8025 on the main
> branch as well to restore stability to the ATH test suite.
>
> -- 
> 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/CAFwNDjpCWAkp6nfB07z3wc9bMqaFs091tbGWyW3CVMQZm8dFmw%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/7d39f095-36c4-4164-a4b9-34f920b5d3dcn%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 

Re: Jenkins 2.401.3 RC testing has started

[Alexander Brandes]

Hey everyone,

I published a new RC removing a plugin with an unresolved vulnerability 
from the setup wizard. The new RC can be obtained from 
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.401.3-rc33579.0058db_2b_4a_21/jenkins-war-2.401.3-rc33579.0058db_2b_4a_21.war
.

BR,
Alex

On Wednesday, 12 July 2023 at 17:04:31 UTC+2 kris...@outlook.com wrote:

> Alternatively, the release can be downloaded from: 
>
> https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.401.3-rc33578.5f3947a_c72fc/jenkins-war-2.401.3-rc33578.5f3947a_c72fc.war
> .
>
> K.S.
>
> --
> *From:* jenkin...@googlegroups.com  on behalf 
> of Kris Stern 
> *Sent:* 12 July 2023 22:03
> *To:* jenkin...@googlegroups.com 
> *Subject:* Jenkins 2.401.3 RC testing has started 
>  
> Hi everyone, 
>
> The latest LTS RC has been made public, and it is ready to be tested. 
> Final release is scheduled for Wednesday, July 26th, 2023. Please report 
> your findings in this thread.
>
> Download the release from: 
> https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.401.3-rc.
>
> Best,
> Kris 
>
> -- 
> 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/TYYP286MB14385E9AB15255203AF7280CA136A%40TYYP286MB1438.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/d06e5ba4-1e35-428c-b241-078d70fbeb03n%40googlegroups.com.

Re: Jenkins 2.413 as next LTS baseline?

[Alexander Brandes]

No objections against 2.414 from my side either.

On Wednesday, 12 July 2023 at 16:03:12 UTC+2 Mark Waite wrote:

> On Wednesday, July 12, 2023 at 7:45:07 AM UTC-6 Alexander Brandes wrote:
>
> Hey everyone,
>
> I would recommend choosing 2.413 as baseline for the next LTS, as it 
> finalizes fixing a major regression from 2.409.
>
>
> I think that 2.413 is a very safe choice as the next LTS baseline.  It has 
> good ratings and the preceding releases also have good ratings.
>
> I think that we should consider 2.414 even a little bit above 2.413 
> because it includes the improvements for the safe restart process and has 
> all the benefits of 2.413.  My personal preference is for 2.414 with the 
> assurance that if there are surprises in the safe restart improvements, 
> we'll backport the fixes.
>  
>
> An alternative would be 2.412, and backport the fixes for JENKINS-71553 
> <https://issues.jenkins.io/browse/JENKINS-71553>.
>
>
> I don't see anything in Jira reports, mailing lists, or on 
> community.jenkins.io that makes me think that 2.412 would be a better 
> choice than 2.413 or 2.414.  I prefer 2.414 as my first choice and 2.413 as 
> my second choice, with 2.414 being only a very little bit ahead of 2.413 in 
> my prioritization.  I'd be happy with either of them.
>  
> 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/6b7d25cb-3087-44d2-99ec-bcc0c84331c7n%40googlegroups.com.

Jenkins 2.413 as next LTS baseline?

[Alexander Brandes]

Hey everyone,

I would recommend choosing 2.413 as baseline for the next LTS, as it 
finalizes fixing a major regression from 2.409.

An alternative would be 2.412, and backport the fixes for JENKINS-71553 
.

Despite the obvious hijacked voting results for 2.413 on the changelog, I 
would favor it nonetheless, given the lack of reports outside voting.

Thoughts? Comments?

Br,
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/cf3aeac4-c9ca-45d5-98ab-012a431c852bn%40googlegroups.com.

Re: About my addition to the jenkinsci/docker-packaging group

[Alexander Brandes]

Subsequent +1 from me

On Monday, 10 July 2023 at 17:40:48 UTC+2 Mark Waite wrote:

> +1 from me for Herve to be added to team-docker-packaging
>
> On Monday, July 10, 2023 at 9:32:13 AM UTC-6 lemeurher...@gmail.com wrote:
>
>> Hello!
>>
>> I've recently asked to be added to the docker-agent repository in 
>> https://github.com/jenkins-infra/repository-permissions-updater/issues/3423, 
>> and instead of just this repo, I've been added to the github team 
>> docker-packaging (
>> https://github.com/orgs/jenkinsci/teams/team-docker-packaging)
>>
>> While this is great for me as I intended to work on other docker 
>> packaging repositories in jenkinsci org, it doesn't seem to follow the 
>> normal process of addition to critical teams like this one, hence this mail 
>> to formally ask if there is any objection about my addition to this team.
>>
>> Kind regards,
>>
>> Hervé
>>
>>

-- 
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/0b0c796d-14d0-4df4-b94a-12542c502bc5n%40googlegroups.com.

Re: JENKINS-66171

[Alexander Brandes]

Hey,

Sometimes, maintainers move on or lose interest in maintaining plugins, 
which is totally fine. The Jenkins project has an adoption policy 
 
allowing 
contributors to step up as maintainers if you are interested in that.
The person you mentioned is the only maintainer.

Best regards,
Alex

On Friday, 30 June 2023 at 11:33:06 UTC+2 realc...@gmail.com wrote:

> Hi,
>
> I'm struggling to get an important fix in for the Docker Custom Build 
> Environment plugin.
>
> It is about https://issues.jenkins.io/browse/JENKINS-66171. I believe I 
> have a legit fix at 
> https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/82 
> which I'm also using in my environment as a temporary solution but I think 
> this should be merged into the plugin and a new release should happen with 
> high priority.
>
> Some weeks ago there was contact with the maintainer, Jon Hermansen, but 
> now there's no reaction for a several weeks. What can I do to make progress 
> here? E.g is there someone else who could help reviewing and getting it 
> integrated/released?
>
> I believe this issue has very high priority now as more people are 
> updating docker and using the new builder.
>
> Thanks a lot in advance
> Christoph
>
>

-- 
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/1a0442cd-b27b-4ffd-946a-fc6d54fe71fen%40googlegroups.com.

Re: Drop 2.375.x support from plugin bom

[Alexander Brandes]

+1

On Tuesday, 27 June 2023 at 08:08:16 UTC+2 timja...@gmail.com wrote:

> +1 from me.
>
> On Mon, 26 Jun 2023 at 23:44, Basil Crow  wrote:
>
>> No strong feeling one way or another from me. When we began requiring
>> 2.361.x or newer, there was a strong technical reason; namely, it was
>> prohibitively difficult to support Java 11 as a first-class citizen in
>> the toolchain alongside Java 8. There is no similar technical
>> justification in this case, since the relevant changes to bring the
>> 2.375.x BOM line up to feature parity with the 2.387.x BOM line with
>> regard to the plugin parent POM and test harness (i.e., the HtmlUnit
>> migration) could be backported if desired. So the question comes down
>> to whether we feel the benefit justifies the cost. If I were doing
>> this work myself, I would try to retain support for 2.375.x since
>> there is some minor inconvenience in dropping support for 2.375.x and
>> since I think the cost of backporting is relatively low. But since I
>> believe the people doing the work should make the decisions, it is not
>> up to me.
>>
>> -- 
>> 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/CAFwNDjoCH9orjtO1NaA94gFzF5gz7AuEKa-Kn4RNP50yBqyJYw%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/b0c8e36c-44bf-48ec-860f-7c4d8e3b5b5an%40googlegroups.com.

Re: Backporting for LTS 2.401.2 has started

[Alexander Brandes]

+1 for the monitor, works well on my CentOS 7 instance.

On Friday, 9 June 2023 at 19:11:26 UTC+2 timja...@gmail.com wrote:

> +1 for EOL Monitor
>
> On Fri, 9 Jun 2023 at 18:01, Basil Crow  wrote:
>
>> That makes sense to me, and I think an exception is justified for
>> time-sensitive areas, such as EOL notifications. The feature has been
>> in weeklies without any reports of regression.
>>
>> On Fri, Jun 9, 2023 at 8:34 AM Mark Waite  wrote:
>> > I would like to inform users earlier about end of life operating 
>> systems, if that difference from the standard LTS backporting rules would 
>> be allowed.
>> >
>> > Specifically, we would backport:
>> >
>> > Warn when operating system end of life is approaching - 
>> https://github.com/jenkinsci/jenkins/pull/7913 (Jenkins 2.407)
>> > Fix Fedora 38 date in operating system end of life warning - 
>> https://github.com/jenkinsci/jenkins/pull/8082 (Jenkins 2.409)
>> >
>> > That would make the operating system end of life warning visible to LTS 
>> users 8 weeks before it would naturally become visible.
>> >
>> > This is backporting a feature, so I am also just fine if this is 
>> rejected, since it is not according to the standard backporting rules where 
>> we rarely backport features to an LTS line.
>> >
>> > I would revise the blog post that announces the end of life operating 
>> system warning to state that the warning is available to LTS users in 
>> 2.401.2
>> >
>> > 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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjoEguYDuOAuw2yxJ82HnT1WOvtvDaN8-0O5XdTvwyUKuw%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/06503203-56eb-4466-8534-5c7d5324181bn%40googlegroups.com.

Re: Requesting admin access to the jenkinsci GitHub organization

[Alexander Brandes]

+1 for Basil

On Mon 5. Jun 2023 at 19:30, Mark Waite  wrote:

>
>
> On Monday, June 5, 2023 at 11:29:18 AM UTC-6 m Basil Crow wrote:
>
> I would like to become an organization administrator of the jenkinsci
> GitHub organization. This would facilitate various efforts I am
> involved with, such as repository transfers.
>
>
> +1 from me.
>
> --
> 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/78809aba-d9ca-4d43-98bf-858811577121n%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/CAP9joaGh28MKR0jSRptwGGhnAKNn_7C8W2aTQVgzpqmsyjtgeQ%40mail.gmail.com.

Requesting Admin access to the jenkinsci organization

[Alexander Brandes]

Hey everyone,

I would like to increase my involvement within the Jenkins project beyond a
maintainer scope, and would like to request admin access to the jenkinsci
GitHub organization.

Besides my seat on the Jenkins governance board, I am one of the core
maintainers within the jenkinsci GitHub organization.
The recent sponsorship of the project coming from GitHub and the adoption
of enterprise features, like autolink references you can find in core
repositories already, are one of the examples of my work, which wouldn't be
possible without me bothering Tim Jacomb constantly to click the right
buttons for me.
I have admin access to various core component and plugin repositories
within the jenkinsci organization, plus the jenkins-infra organization,
including jenkins.io or the plugin site. Having admin permissions in the
jenkinsci organization would allow me to help to facilitate contributions
of these kinds to the Jenkins project.

My GitHub account is configured securely, and I have an ICLA signed.

Would the project be fine with such a request?

Thanks in advance,

Alexander Brandes

-- 
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/CAP9joaHYsQEvPKLQpxdWPW_OR92O98F8Xt1AWMyDsO-03tYiQg%40mail.gmail.com.

Re: Backporting for LTS 2.401.2 has started

[Alexander Brandes]

It appears you forgot to select issues you want to backport. The query is 
empty.

On Saturday, 3 June 2023 at 05:20:02 UTC+2 kris...@outlook.com wrote:

> Hi everyone,
>
> Backporting for 2.401.2 has started, and the RC is scheduled for 
> Wednesday, June 14th, 2023.
>
>
> Candidates: https://issues.jenkins.io/issues/?filter=12146
> Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.2-fixed
> Rejected: 
> https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.2-rejected
>
> Best,
>
> Kris
>
>
>

-- 
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/b69ac7b9-ca5c-4f3d-ba0e-5cc3496aabd1n%40googlegroups.com.

Re: Permission to upload new Sonargraph Jenkins plugin release 5.0.2 to plugin repository

[Alexander Brandes]

Alternatively, you can adopt 

 the 
plugin.

On Thursday, 1 June 2023 at 12:16:22 UTC+2 ullrich...@gmail.com wrote:

> > The colleague who was working on our plugin before no longer maintains 
> that plugin. He left the company (hello2morrow).
> > 
> > I submitted a PR (pull request) to obtain authorization. I got feedback, 
> that I would need the authorization of 3 developers, which all no longer 
> work for our company, They no longer maintain any Sonargraph related open 
> source component. 
> > 
> > So I am kind of stuck here - help is appreciated.
>
> Did you try to reach out to these developers? 

-- 
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/ec6d0625-9974-42a9-9201-16a7ef587452n%40googlegroups.com.

Re: Jenkins 2.401.1 RC testing has started

[Alexander Brandes]

Hey,

Thanks for spotting! I created a draft including both changes mentioned: 
https://github.com/jenkinsci/jenkins/pull/8051

~ Alex

On Thursday, 25 May 2023 at 23:35:31 UTC+2 cc...@cloudbees.com wrote:

> Created https://issues.jenkins.io/browse/JENKINS-71345 for tracking.
>
> On Thursday, May 25, 2023 at 5:32:12 PM UTC-4 Cathy Chan wrote:
>
>> We just observed that the entries in the dropdown of `Manage Jenkins` -> 
>> `Configure System` all have trailing "undefined".
>>
>> This has been fixed on 2.403, apparently as a side effect of 
>> https://github.com/jenkinsci/jenkins/pull/7474 and 
>> https://github.com/jenkinsci/jenkins/pull/7887. Should we consider a 
>> backport?
>>
>> - Cathy.
>>
>>
>> On Wednesday, May 17, 2023 at 5:13:25 AM UTC-4 mc.ca...@gmail.com wrote:
>>
>> Hello everyone,
>>
>> Latest LTS RC was made public, and it is ready to be tested. Final 
>> release is scheduled for 2023-05-31.
>>
>> Please report your findings in this thread.
>>
>> Download the release from: 
>> https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.401.1-rc33562.17c1c4c32750/jenkins-war-2.401.1-rc33562.17c1c4c32750.war
>>
>> Best regards,
>> 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/84bffcbb-7510-4c60-a018-c2685dd86faan%40googlegroups.com.

Re: Maven 3.9.2: ready to roll?

[Alexander Brandes]

I'm already using it locally with Java 20.0.1 and 17 for Jenkins core, 
libraries, and a few plugins without issues 

On Tuesday, 23 May 2023 at 09:57:48 UTC+2 damien@gmail.com wrote:

> Hello dear maintainers,
>
> Is there any objection against the deployment of Maven 3.9.2 in the 
> Jenkins infrastructure?
>
>
> For the Jenkins 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/ce67ff65-b697-431f-9ee3-772197971755n%40googlegroups.com.

Jenkins 2.401.1 RC testing has started

[Alexander Brandes]

Hello everyone,

Latest LTS RC was made public, and it is ready to be tested. Final release 
is scheduled for 2023-05-31.

Please report your findings in this thread.

Download the release from: 
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.401.1-rc33562.17c1c4c32750/jenkins-war-2.401.1-rc33562.17c1c4c32750.war

Best regards,
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/935d0944-596f-4d08-8625-dece5acf1761n%40googlegroups.com.

Backporting for LTS 2.401.1 started

[Alexander Brandes]

Hey everyone,

Backporting for 2.401.1 has started, and the RC is scheduled for 2023-05-17.

Candidates: https://issues.jenkins.io/issues/?filter=12146
Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.1-fixed
Rejected: 
https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.1-rejected

Best regards,

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/3194b666-9e5e-40c1-ad15-0e5be650fd5en%40googlegroups.com.

Re: Release lead for 2.401.1

[Alexander Brandes]

I can take care of that.

Best regards,
Alex

On Monday, 15 May 2023 at 18:02:25 UTC+2 timja...@gmail.com wrote:

> Hello
>
> Is anyone interested in being the release lead for 2.401.1?
>
> Planned dates can be seen on the event calendar: 
> https://www.jenkins.io/events/#event-calendar
> Release candidate by 17th May (apologies for short notice can be a little 
> late if needed)
> Release on 31st May
>
> The documentation is at:
>
> https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
>
> I'll be available to answer any questions and provide guidance (along with 
> hopefully other past release leads)
>
> We chat in #jenkins-release on libera IRC, 
> https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix 
> channel.
>
> Anyone interested?
>
> 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/49ebbd5e-1a4d-45f5-88bc-a5d6e246fcaen%40googlegroups.com.

Re: Jenkinsci Cloudevents plugin

[Alexander Brandes]

> Do you know what the next steps are to get the plug-in formally pulled 
into the jenkins project on GitHub and being available on the 
plugin.jenkins.io page? I don’t know if that is a process or something more 
simple?

It's as simple as cutting a release of the plugin. Take a look at the guide 
<https://www.jenkins.io/doc/developer/publishing/releasing-manually/#prerequisites>
 on 
how to set up your machine to cut a successful release. plugins.jenkins.io 
refreshes every 2 hours, if I recall correctly, so you'll see your plugin 
there timely.

> Also we will be in Vancouver for cdCon if others are. We would love to 
meet up.

Awesome, I'll be there too \o/

~ Alex

On Saturday, 22 April 2023 at 11:59:08 UTC+2 gerard@fmr.com wrote:

> Thank you Alexander and it is great to be onboard and we look forward to 
> further contributions and participation.
>
> Do you know what the next steps are to get the plug-in formally pulled 
> into the jenkins project on GitHub and being available on the 
> plugin.jenkins.io page? I don’t know if that is a process or something 
> more simple?
>
> Also we will be in Vancouver for cdCon if others are. We would love to 
> meet up.
>
> Thanks
>
> Ger
>
> Sent from Outlook for iOS <https://aka.ms/o0ukef>
> --
> *From:* jenkin...@googlegroups.com  on behalf 
> of Alexander Brandes 
> *Sent:* Saturday, April 22, 2023 10:23:22 AM
> *To:* Jenkins Developers 
> *Subject:* Re: Jenkinsci Cloudevents plugin 
>  
> NOTICE: This email is from an external sender - do not click on links or 
> attachments unless you recognize the sender and know the content is safe. 
>
> Hey Gerard, 
>
> I've finished my investigation and didn't find new blockers. Thanks for 
> addressing my outstanding concerns and welcome aboard!
>
> I'm excited to see the CDEvents plugin being included in the printings.
>
> BR,
> Alexander Brandes
>
> On Friday, 21 April 2023 at 16:12:56 UTC+2 gerard@fmr.com wrote:
>
> Hi
>
>
> I first wanted to thanks you all for the help and support on this, our 
> teams first major contribution. I think we have made great progress on the 
> feedback received to date and we are hoping the lastest push closes out all 
> the findings. 
>
>
> I wanted to share that there is somewhat of a time consideration to having 
> the plugin publicly available and accessible. The CDF are planning to 
> announce the plugin within some upcoming press releases and at CDCon on May 
> 8th alongside other contribution projects related to CDEvents. All the 
> marketing materials for the press releases and CDCon have to be submitted 
> next week for print etc. We are looking to include the Jenkins CDEvents 
> Plugin within the press release and at CDCon and wanted to include all the 
> Jenkins URL's for gihub and plugin.jenkins.io.
>
>  
>
> Do you think this is possible and if their was a possibility, could  the 
> reviews be accelerated for the plugin to be available within the Jenkins 
> project by the middle of next week. If you don’t think this is an option we 
> can temporarily host within the CDevents project itself and for the 
> purposes of the above and once within Jenkins we can communicate out again.
>
>  
>
> Thought and appreciate anything that can be done from an acceleration 
> perspective.
>
>  
>
> Thanks
>
>  
>
> Ger
>
>  
>
>
> On Friday, April 21, 2023 at 1:51:00 PM UTC+1 mc.ca...@gmail.com wrote:
>
> I'll continue reviewing the request by next week.
>
> Thanks for addressing the issues named so far!
>
> BR,
> Alexander Brandes
>
> On Fri 21. Apr 2023 at 14:46, 'Jamie Plower' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
> Hi all,
>
> All updates are done in https://github.com/fidelity/cdevents-plugin and 
> address all spotbugs items and required pom updates. 
>
> Please let know if you need anything else to proceed with the hosting 
> process. 
>
> Thanks in advance
>
> Jamie 
>
> On Thursday, April 20, 2023 at 5:30:16 PM UTC+1 Mark Waite wrote:
>
> On Thu, Apr 20, 2023 at 5:32 AM 'Jamie Plower' wrote:
>
> HI all,
>
> Just to update the hosting request has been completed for the CDEvents 
> plugin with the details below and is with the Jenkins team for internal 
> checks. Very keen to see this published and please let me know if you 
> require anything else from my side. Many thanks to all regarding support 
> during the hosting process 
>
>
> Thanks very much.  I cloned the repository and built it.  Nice result.  It 
> reports some open spotbugs warnings.  There is a tutorial that will help 
> you resolve the spotbugs warnings 
> <https://w

Re: Jenkinsci Cloudevents plugin

[Alexander Brandes]

Hey Gerard,

I've finished my investigation and didn't find new blockers. Thanks for 
addressing my outstanding concerns and welcome aboard!

I'm excited to see the CDEvents plugin being included in the printings.

BR,
Alexander Brandes

On Friday, 21 April 2023 at 16:12:56 UTC+2 gerard@fmr.com wrote:

> Hi
>
>
> I first wanted to thanks you all for the help and support on this, our 
> teams first major contribution. I think we have made great progress on the 
> feedback received to date and we are hoping the lastest push closes out all 
> the findings. 
>
>
> I wanted to share that there is somewhat of a time consideration to having 
> the plugin publicly available and accessible. The CDF are planning to 
> announce the plugin within some upcoming press releases and at CDCon on May 
> 8th alongside other contribution projects related to CDEvents. All the 
> marketing materials for the press releases and CDCon have to be submitted 
> next week for print etc. We are looking to include the Jenkins CDEvents 
> Plugin within the press release and at CDCon and wanted to include all the 
> Jenkins URL's for gihub and plugin.jenkins.io.
>
>  
>
> Do you think this is possible and if their was a possibility, could  the 
> reviews be accelerated for the plugin to be available within the Jenkins 
> project by the middle of next week. If you don’t think this is an option we 
> can temporarily host within the CDevents project itself and for the 
> purposes of the above and once within Jenkins we can communicate out again.
>
>  
>
> Thought and appreciate anything that can be done from an acceleration 
> perspective.
>
>  
>
> Thanks
>
>  
>
> Ger
>
>  
>
>
> On Friday, April 21, 2023 at 1:51:00 PM UTC+1 mc.ca...@gmail.com wrote:
>
>> I'll continue reviewing the request by next week.
>>
>> Thanks for addressing the issues named so far!
>>
>> BR,
>> Alexander Brandes
>>
>> On Fri 21. Apr 2023 at 14:46, 'Jamie Plower' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> Hi all,
>>>
>>> All updates are done in https://github.com/fidelity/cdevents-plugin and 
>>> address all spotbugs items and required pom updates. 
>>>
>>> Please let know if you need anything else to proceed with the hosting 
>>> process. 
>>>
>>> Thanks in advance
>>>
>>> Jamie 
>>>
>>> On Thursday, April 20, 2023 at 5:30:16 PM UTC+1 Mark Waite wrote:
>>>
>>>> On Thu, Apr 20, 2023 at 5:32 AM 'Jamie Plower' wrote:
>>>>
>>>>> HI all,
>>>>>
>>>>> Just to update the hosting request has been completed for the CDEvents 
>>>>> plugin with the details below and is with the Jenkins team for internal 
>>>>> checks. Very keen to see this published and please let me know if you 
>>>>> require anything else from my side. Many thanks to all regarding support 
>>>>> during the hosting process 
>>>>>
>>>>>
>>>> Thanks very much.  I cloned the repository and built it.  Nice result.  
>>>> It reports some open spotbugs warnings.  There is a tutorial that will 
>>>> help 
>>>> you resolve the spotbugs warnings 
>>>> <https://www.jenkins.io/doc/developer/tutorial-improve/add-more-spotbugs-checks/>
>>>>  
>>>> either by excluding them or by code changes.
>>>>  
>>>> 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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/01de9849-0bff-4220-a7a3-c999e2f53b5cn%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/01de9849-0bff-4220-a7a3-c999e2f53b5cn%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/e3588840-73d0-4587-840a-b41f52f89acfn%40googlegroups.com.

Re: Jenkinsci Cloudevents plugin

[Alexander Brandes]

I'll continue reviewing the request by next week.

Thanks for addressing the issues named so far!

BR,
Alexander Brandes

On Fri 21. Apr 2023 at 14:46, 'Jamie Plower' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi all,
>
> All updates are done in https://github.com/fidelity/cdevents-plugin and
> address all spotbugs items and required pom updates.
>
> Please let know if you need anything else to proceed with the hosting
> process.
>
> Thanks in advance
>
> Jamie
>
> On Thursday, April 20, 2023 at 5:30:16 PM UTC+1 Mark Waite wrote:
>
>> On Thu, Apr 20, 2023 at 5:32 AM 'Jamie Plower' wrote:
>>
>>> HI all,
>>>
>>> Just to update the hosting request has been completed for the CDEvents
>>> plugin with the details below and is with the Jenkins team for internal
>>> checks. Very keen to see this published and please let me know if you
>>> require anything else from my side. Many thanks to all regarding support
>>> during the hosting process
>>>
>>>
>> Thanks very much.  I cloned the repository and built it.  Nice result.
>> It reports some open spotbugs warnings.  There is a tutorial that will help
>> you resolve the spotbugs warnings
>> <https://www.jenkins.io/doc/developer/tutorial-improve/add-more-spotbugs-checks/>
>> either by excluding them or by code changes.
>>
>> 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/01de9849-0bff-4220-a7a3-c999e2f53b5cn%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/01de9849-0bff-4220-a7a3-c999e2f53b5cn%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/CAP9joaEV0uqYsECeP_-tF8%3DJsBabyHOUXmrejoBa-gTkna6BVw%40mail.gmail.com.

Re: Jenkins 2.401 as next LTS baseline?

[Alexander Brandes]

+1 for 2.401

On Fri 21. Apr 2023 at 14:45, Mark Waite  wrote:

> As a third option, the 2.399 release has very good ratings but would need
> a backport of at least https://issues.jenkins.io/browse/JENKINS-70988
> TypeError: inputs[i].nextElementSibling is null
>
> On Friday, April 21, 2023 at 6:23:23 AM UTC-6 Mark Waite wrote:
>
>> We're a few days behind the scheduled date to choose a Jenkins version as
>> the baseline for the next long term support release.
>>
>> I recommend that we choose 2.401 as the baseline because it includes the
>> fix for https://issues.jenkins.io/browse/JENKINS-70988 - TypeError:
>> inputs[i].nextElementSibling is null and also includes
>> https://github.com/jenkinsci/jenkins/pull/7845 Copy multiple class names
>> in hetero-list.js .  Further benefit that it includes a Spring Framework
>> update to reduce the risk of security scanner complaints.
>>
>> An alternative choice would be to  choose 2.400 and backport
>> https://github.com/jenkinsci/jenkins/pull/7845 Copy multiple class names
>> in hetero-list.js and optionally backport the Spring Framework update
>>
>> 2.400 has more than the typical number of "rollback" ratings on
>> https://www.jenkins.io/changelog/ though it is not clear to me why it
>> received that many reports of rollback.
>>
>> Comments from others on which version to choose as the next LTS baseline?
>>
>> 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/9a02dd0f-ad52-43ae-b549-bc4f75aed8a7n%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/CAP9joaGxNbcb5yJp0rPYt_R9K%2BQ-Rs8FDwLme%2BdBYiUnTX4J%2BA%40mail.gmail.com.

Re: Reimbursement for code signing certificate

[Alexander Brandes]

+1, of course.

On Tuesday, 18 April 2023 at 21:29:22 UTC+2 ga...@gavinmogan.com wrote:

> I would argue this discussion should happen before the spending not after.
>
> But +1 from me
>
> On Tue, Apr 18, 2023 at 12:04 PM Tim Jacomb  wrote:
>
>> +1
>>
>> On Tue, 18 Apr 2023 at 19:32, Basil Crow  wrote:
>>
>>> On Tue, Apr 18, 2023 at 11:23 AM 'Gavin Mogan' via Jenkins Developers
>>>  wrote:
>>> > Shouldn't this be submitted via expensify and approved in the board
>>> > mailing list?
>>>
>>> From JEP-15 (at revision b8bfe17), § 3.3.2 ("Use of donations"), lines
>>> 177-178:
>>>
>>> > Budget requests should be submitted to the developer mailing list and
>>> > discussed there, the Governance meeting will be doing a formal
>>> > approval/rejection based on the community feedback.
>>>
>>> -- 
>>> 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/CAFwNDjpHawAfD7141y-_TxgOThzrMH_g7Z9x8To2p9vQHPM5Bw%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/CAH-3Bif%2Bm%2BaUJYNW1F5xQTz6DCm1jj5qWj%2B%3D_go1vq4Z0hVOyA%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/cb2577be-d4f2-43d2-9fbb-e43198899001n%40googlegroups.com.

Revise "Bug" template fields on Jira

[Alexander Brandes]

Hey everyone,

Commonly, when I'm triaging (core) issues, I almost always face submissions 
like JENKINS-71064  and 
JENKINS-70732 .
These two figures are prime examples of how issue submissions are not 
supposed to look like. The list is long, and based on my observation, 
getting longer by day.

I don't believe it's healthy to continuously bug submitters to provide 
details on their setup, when they could - and are supposed to - do that 
during the submission form.
That's part of the issue reporting documentation, we link on the issue 
form, but is commonly ignored.

I would like to propose making the "Environment" and "Description" fields 
mandatory for "Bug" type issues on Jira, to go a bit against issue 
submissions without any useful information at all and stop us playing 
guessing games.

Best regards,

Alex

*This mail is a copy 
of https://github.com/jenkins-infra/helpdesk/issues/3515 
*

-- 
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/7b613078-29dd-4f22-84d3-44fbe9dcfa91n%40googlegroups.com.

Re: Looking for assistants on jenkins.io ui decisions

[Alexander Brandes]

> As for groups, I kinda gave access to plugin-site group, but it can 
probably be given to a better group. I've been trying to tag @copy-editors 
for copy changes, like navigation

I see, I asked to join the team 
<https://github.com/orgs/jenkins-infra/teams/plugin-site/members> through 
GitHub to keep myself posted if that works for you. Maybe we can look into 
a more suitable model in the future.

~ Alex

On Friday, 14 April 2023 at 19:17:40 UTC+2 ga...@gavinmogan.com wrote:

> Thanks so much for helping out.
>
> All my github notifications get marked as spam, so now i can only review 
> them really at the end of the day, so i'm way behind on things.
>
> As for groups, I kinda gave access to plugin-site group, but it can 
> probably be given to a better group. I've been trying to tag @copy-editors 
> for copy changes, like navigation
>
> On Fri, Apr 14, 2023 at 9:36 AM Alexander Brandes  
> wrote:
>
>> Hey Gavin,
>>
>> I'm already reviewing PRs and contributing to several component-like 
>> repositories. I plan to keep up on that. Don't hesitate to mention me in a 
>> PR if you're looking for an additional pair of eyes.
>> If we have a team for that, you can add me to one for sure, to keep your 
>> workload surveyable. Whatever works the best for you!
>>
>> ~ Alex
>>
>> On Monday, 27 February 2023 at 01:28:32 UTC+1 kris...@outlook.com wrote:
>>
>>> Hi Gavin,
>>>
>>> I would like to help out on such tasks if possible. 
>>>
>>> Best,
>>> Kris
>>> --
>>> *From:* ga...@gavinmogan.com  on behalf of 'Gavin 
>>> Mogan' via Jenkins Developers 
>>> *Sent:* 27 February 2023 08:18
>>> *To:* Jenkins Developers 
>>> *Subject:* Looking for assistants on jenkins.io ui decisions 
>>>  
>>> So I am the "official maintainer" of plugins, i guess stories, and the 
>>> web components for header and footer.
>>>
>>> I have no problem with reviewing PRs for technical items and bugs, but 
>>> for behavior, I have low motivation. I don't use jenkins at work, and since 
>>> getting covid in january, i've been trying to be off my personal computer 
>>> more, and it looks like the ramp up for gsoc is getting more and more small 
>>> behavior PRs coming though (fixes to support mobile viewing).
>>>
>>> I know kevin and mark "own" the content of jenkins.io 
>>> <https://jpn01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjenkins.io%2F=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=xF5ToNRE%2BfEhNyKpfa5PTLQRMes26ukKF817fKid2B0%3D=0>,
>>>  
>>> but is there anyone interested in owning/being primary for behavior of the 
>>> sites?
>>>
>>> https://github.com/jenkins-infra/jenkins-io-components/pull/71 
>>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins-io-components%2Fpull%2F71=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=2BwROLXhSYXvQbsLg260hBhdPrTKvZ5L6749%2BcgNsKs%3D=0>
>>>  
>>> - Show links to books in the footer.
>>> https://github.com/jenkins-infra/jenkins-io-components/pull/63 
>>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins-io-components%2Fpull%2F63=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=TOxE7TbO1mcKR2TalRGT9xV8a5PqiIQ4CW3sjhsiK8I%3D=0>
>>>  
>>> - overflow of menu links on mobile
>>> https://github.com/jenkins-infra/plugin-site/pull/1277 
>>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fplugin-site%2Fpull%2F1277=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=y%2BmXJCzc10sl5h6Ku9tSWWJuJ7a0J43mCt%2Fv6e1yRgo%3D=0>
>>>  
>>> - Changing of alignment on search on plugins site
>>> https://github.com/jenkins-infra/plugin-site/pull/1276 
>>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenk

Re: Looking for assistants on jenkins.io ui decisions

[Alexander Brandes]

Hey Gavin,

I'm already reviewing PRs and contributing to several component-like 
repositories. I plan to keep up on that. Don't hesitate to mention me in a 
PR if you're looking for an additional pair of eyes.
If we have a team for that, you can add me to one for sure, to keep your 
workload surveyable. Whatever works the best for you!

~ Alex

On Monday, 27 February 2023 at 01:28:32 UTC+1 kris...@outlook.com wrote:

> Hi Gavin,
>
> I would like to help out on such tasks if possible. 
>
> Best,
> Kris
> --
> *From:* ga...@gavinmogan.com  on behalf of 'Gavin 
> Mogan' via Jenkins Developers 
> *Sent:* 27 February 2023 08:18
> *To:* Jenkins Developers 
> *Subject:* Looking for assistants on jenkins.io ui decisions 
>  
> So I am the "official maintainer" of plugins, i guess stories, and the web 
> components for header and footer.
>
> I have no problem with reviewing PRs for technical items and bugs, but for 
> behavior, I have low motivation. I don't use jenkins at work, and since 
> getting covid in january, i've been trying to be off my personal computer 
> more, and it looks like the ramp up for gsoc is getting more and more small 
> behavior PRs coming though (fixes to support mobile viewing).
>
> I know kevin and mark "own" the content of jenkins.io 
> ,
>  
> but is there anyone interested in owning/being primary for behavior of the 
> sites?
>
> https://github.com/jenkins-infra/jenkins-io-components/pull/71 
> 
>  
> - Show links to books in the footer.
> https://github.com/jenkins-infra/jenkins-io-components/pull/63 
> 
>  
> - overflow of menu links on mobile
> https://github.com/jenkins-infra/plugin-site/pull/1277 
> 
>  
> - Changing of alignment on search on plugins site
> https://github.com/jenkins-infra/plugin-site/pull/1276 
> 
>  
> - Show more page numbers on larger screen
>
> All seem fine from a technical point of view, and the two plugin ones 
> sound good are probably wins, i just know myself and my ADHD, its hard to 
> motivate myself to deal with them.
>
> So looking for assistance, mostly on the why/if we should, not the code, i 
> can handle the code.
>
>
> Gavin
>
> -- 
> 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_Dus1UmUJrkOvrV_YLEe59mae1mahhuLmGOWRQ%3DBtO9sY2w%40mail.gmail.com
>  
> 

Re: Adopting inodes-monitor-plugin

[Alexander Brandes]

Hey,

Here's the correct RPU URL: 
https://github.com/jenkins-infra/repository-permissions-updater/pull/3245 for 
the adoption request.

BR,
Alex

On Thursday, 13 April 2023 at 14:25:21 UTC+2 srikant...@gmail.com wrote:

> Hi,
>
> I would like to adopt inodes-monitor-plugin
>
>- 
>
>Link to a plugin you want to adopt: 
>https://github.com/jenkinsci/inodes-monitor-plugin
>- 
>
>The status of the plugin: "For adoption"
>- 
>
>Link(s) to pull requests you want to deliver, if applicable: 
>https://github.com/jenkinsci/inodes-monitor-plugin/pull/6
>- My GitHub username/id: janasrikanth
>- My Jenkins infrastructure account id: janasrikanth
>- link to the "Repository Permission Updater" PR: 
>https://github.com/jenkins-infra/repository-permissions-updater/pull/3245 
>
>
> Thanks,
> Jana Srikanth
>

-- 
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/7ad75683-cccf-4e1b-948e-4b1f6429baa3n%40googlegroups.com.

Re: Zoom account access for Kris Stern

[Alexander Brandes]

Approved, but if we're at it, I lack access to our 1password too.

~ Alex

On Thursday, 13 April 2023 at 14:55:35 UTC+2 Mark Waite wrote:

> Kris Stern is one of the Jenkins organization administrators in Google 
> Summer of Code.  He needs access to the Jenkins Zoom account so that he can 
> host office hours and run mentoring sessions.
>
> Once approved, we'll share the Zoom account password with him through 
> 1password and will ask that he be added to the Zoom account email list.
>
> 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/815dc75e-c375-49ba-85f1-f30a6f61d46dn%40googlegroups.com.

Re: Updating Plugin Maintainer

[Alexander Brandes]

Hey Randall,

the information is based on the developers specified in the permission file 

 of 
your repository. You can fork the repository, modify the file and propose a 
PR to update the maintainers of your plugin.

Best regards,
Alex

On Thursday, 30 March 2023 at 16:04:08 UTC+2 rpet...@nowsecure.com wrote:

> Hi All,
>
> We would like to update the maintainer listed for our plugin at 
> https://plugins.jenkins.io/nowsecure-auto-security-test/ , it looks like 
> it is currently the last version generated from the now-defunct wiki. If we 
> were to update our information in Jira, would that update the name on the 
> page? Or will we need to update to using the Github documentation to make 
> changes?
>
> Thanks,
> Randall
>

-- 
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/24e18d78-4620-4b68-83a8-4ae6fd90ba77n%40googlegroups.com.

Re: one-shot-executor-plugin

[Alexander Brandes]

> That experiment was indeed abandoned

If it's abandoned, we should archive the repository then.

On Thursday, 16 March 2023 at 02:25:50 UTC+1 slide wrote:

> Awesome, thanks for pointing that out! Much appreciated!
>
> On Wed, Mar 15, 2023, 18:24 'Jesse Glick' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> That experiment was indeed abandoned. Use 
>> https://javadoc.jenkins.io/plugin/durable-task/org/jenkinsci/plugins/durabletask/executors/OnceRetentionStrategy.html
>>
>> -- 
>> 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/CANfRfr3_c7pc6FNLyZ0xzRDObCQsn%2BULSemmZMJtWeKsOV77zg%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/428291f7-8434-4406-b236-4258c2b9a085n%40googlegroups.com.

Re: Jenkins 2.387.1 RC testing has started

[Alexander Brandes]

Thanks, the pull request has been merged, and the commit has been 
backported to the stable branch.

A new RC is available at 
https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.387.1-rc33315.3b_778b_3e1c8d/jenkins-war-2.387.1-rc33315.3b_778b_3e1c8d.war

On Wednesday, 22 February 2023 at 19:11:31 UTC+1 ane...@cloudbees.com wrote:

> Hey again,
>
> Here is a Pull Request providing a fix for the regression discussed above: 
> https://github.com/jenkinsci/jenkins/pull/7668
>
> Let me know if anything else is needed :)
>
> On Wednesday, February 22, 2023 at 5:51:18 PM UTC+1 Antoine Neveux wrote:
>
>> Hello Alex, hello everyone,
>>
>> There is a regression introduced with that LTS version: [JENKINS-70662 
>> ] Built-in validations 
>> are broken when inside an `optionalBlock`.
>>
>> The commit that led to this regression is 
>> 5870838f690eaa06762630eceb21c40d3df0ceb8 
>> ,
>>  
>> coming from Pull Request: #7203 
>> . The regression was 
>> first delivered with Jenkins 2.376.
>>
>> The particular change that led to this regression is the submit button in 
>> form/submit.jelly which was changed from >
>> The error which is faced (An invalid form control with name='' is not 
>> focusable) is likely a browser validation error (reference 
>> 
>> ).
>>
>> Different solutions could be imagined, among some tested:
>>
>>- Adding novalidate="true" to the form tag in form.jelly works, with 
>>a concern about f:form being sufficiently commonly used to be a valid 
>>approach?
>>- Adding formNoValidate="true" to the submit button works as well
>>
>> Other solutions could be considered, but might be more difficult to put 
>> in place?
>>
>> I'm not familiar with how OSS LTS releases are managed, so could you 
>> please let me know how we could move forward with that concern? Would you 
>> like me to submit a Pull Request to core with one of these fixes?
>>
>> Thanks a lot for your help and attention, have a great day!
>>
>> Antoine
>>
>> On Wednesday, February 22, 2023 at 10:06:51 AM UTC+1 mc.ca...@gmail.com 
>> wrote:
>>
>>> Hello everyone,
>>>
>>> Latest LTS RC was made public, and it is ready to be tested. Final 
>>> release is scheduled for 2023-03-08.
>>>
>>> Please report your findings in this thread.
>>>
>>> Download the release from: 
>>> https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.387.1-rc33314.b_f418c7c9f79/jenkins-war-2.387.1-rc33314.b_f418c7c9f79.war
>>> Best regards,
>>> 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/d8a2d903-262b-4c03-bd36-c18bb9f8e7a5n%40googlegroups.com.