Re: Adopt unity3d plugin

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

Backporting for Jenkins 2.452.1 has started

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:

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

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

2.452.1 release lead

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

Re: Modernize device-watcher-plugin

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

Re: Adopt msbuild plugiin

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

Re: 2.452 as May 15, 2024 LTS baseline?

+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

Building Jenkins core and plugins with Java 22

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

Re: Adoption request for scmskip plugin

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

Re: Adopt email-ext plugin

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

Re: Retire some of my old plugins

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

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

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

Re: Remove Suggestimate from issues.jenkins.io?

+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 >

Re: Adoption of delivery-pipeline-plugin

uilds-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

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

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

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

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

Re: nomad-plugin merge maxconcurrentjobs

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 >

Re: Adoption request for jenkins-multijob-plugin

ing 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. >> >> >>>

Re: Adopt plugin openid-plugin

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 >

Proposal: Stefan Spieker to join the core PR reviewers team

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

Re: Jenkins 2.440.1-rc has been released

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

Re: Adoption request for jenkins-multijob-plugin

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

Re: Build p4-plugin using gradle.

> 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.

Jenkins 2.440.1-rc has been released

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:

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

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

Backporting for 2.440.1 has started

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:

Re: [Adoption] mail-watcher-plugin

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 >

Re: 2.440.1 Release Lead

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

2.440.1 Release Lead

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

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

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

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

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 for

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

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

Re: 2.440 as Feb 21, 2024 LTS baseline?

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

Re: jenkins-2.426.3-rc has been released

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

Re: Adoption request for radargun-plugin

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

Re: Adoption request pipeline-as-yaml-plugin

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

Re: UI/Website Feedback on top bar

> 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

Re: Adoption request sectioned-view-plugin

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:

Re: How to skip tests while generating build

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

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

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

Re: Adoption request flyway-runner-plugin

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

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

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

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

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

Re: Reporting documentation bug

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? > >

Re: October 30, 2023 Governance Board Agenda

:/ ~ 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 Hafne

Re: Plug-in adoption

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 ~

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

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.

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

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

Re: Adoption request extra-tool-installers-plugin

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

Re: Mark Waite as release lead for 2.426.1?

eduled 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 >>> - Addi

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

t; 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 off

Re: Backporting for LTS 2.414.3 has started

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

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

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

Re: Backporting for LTS 2.414.3 has started

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]

Re: Proposal: Kris Stern to join the release team

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:

Re: 2.426 as Nov 15, 2023 LTS baseline?

+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 >

Re: October 2, 2023 Governance Board Agenda

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 Brand

Proposal: Kris Stern to join the release team

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

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

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

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

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

Re: Release lead for LTS 2.414.3

+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

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

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

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

ovember 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 messag

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

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

Re: Renaming the plugin and repo

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

Opportunity to be the release lead for 2.414.2

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

Re: [ci.jenkins.io] JDK21 availability

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

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

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

Backporting for LTS 2.414.1 started

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:

2.414.1 Release Lead

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.

Re: Jenkins 2.413 as next LTS baseline?

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.

Re: Jenkins 2.401.3 RC testing has started

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 .

Re: Jenkins 2.413 as next LTS baseline?

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

Jenkins 2.413 as next LTS baseline?

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

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

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

Re: JENKINS-66171

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

Re: Drop 2.375.x support from plugin bom

+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 >>

Re: Backporting for LTS 2.401.2 has started

+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

Re: Requesting admin access to the jenkinsci GitHub organization

+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

Requesting Admin access to the jenkinsci organization

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 "Je

Re: Backporting for LTS 2.401.2 has started

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:

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

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.

Re: Jenkins 2.401.1 RC testing has started

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

Re: Maven 3.9.2: ready to roll?

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

Jenkins 2.401.1 RC testing has started

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:

Backporting for LTS 2.401.1 started

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:

Re: Release lead for 2.401.1

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

Re: Jenkinsci Cloudevents plugin

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

Re: Jenkinsci Cloudevents plugin

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

Re: Jenkinsci Cloudevents plugin

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://gith

Re: Jenkins 2.401 as next LTS baseline?

+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

Re: Reimbursement for code signing certificate

+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

Revise "Bug" template fields on Jira

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

Re: Looking for assistants on jenkins.io ui decisions

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

Re: Looking for assistants on jenkins.io ui decisions

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

Re: Adopting inodes-monitor-plugin

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

Re: Zoom account access for Kris Stern

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

Re: Updating Plugin Maintainer

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

Re: one-shot-executor-plugin

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

Re: Jenkins 2.387.1 RC testing has started

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

  1   2   >