Re: Modernize core dependency json-lib library

I did a risk assessment of the various Apache Commons libraries we are shipping in core. --- commons-beanutils-1.11.0.jar Used extensively by Stapler/Jelly and cannot be removed. We're on version 1.11.0, which doesn't use Commons Lang 3; version 2.0.0-M2 uses Commons Lang 3. If Commons BeanUtils

Re: The reverse-proxy-auth-plugin is being put up for adoption

Hi Steve, Thank you for the heads-up about the reverse-proxy-auth-plugin. We appreciate your transparency in putting it up for adoption and understand the need for proper care and attention to maintain its quality. Please remember to follow the next steps in the abandonment procedure listed here:

Re: Modernize core dependency json-lib library

: jenkinsci-dev@googlegroups.com Subject: Re: Modernize core dependency json-lib library On Wed, Jul 30, 2025 at 10:30 AM 'Winter, Markus' via Jenkins Developers wrote: > > And given the almost 300 plugins that use commons-lang I think once json-lib > is fixed we can remove it

Re: Modernize core dependency json-lib library

On Wed, Jul 30, 2025 at 10:30 AM 'Winter, Markus' via Jenkins Developers wrote: > > And given the almost 300 plugins that use commons-lang I think once json-lib > is fixed we can remove it from core and have the commons-lang-api plugin as > an implied dependency. An implied dependency could wo

Re: Modernize core dependency json-lib library

Security Scan look for usages of commons.lang and report them? From: jenkinsci-dev@googlegroups.com on behalf of Verachten Bruno Sent: Wednesday, July 30, 2025 6:20 PM To: jenkinsci-dev@googlegroups.com Subject: Re: Modernize core dependency json-lib library

Re: Modernize core dependency json-lib library

Basil, Thank you for creating the spreadsheet to track the dependencies related to removing Commons Lang 2 from Jenkins core. That will prove helpful! Best wishes, Bruno On Wed, Jul 30, 2025 at 6:16 PM Basil Crow wrote: > CVE-2025-48924 increases the motivation to remove Commons Lang 2 from >

Re: Modernize core dependency json-lib library

CVE-2025-48924 increases the motivation to remove Commons Lang 2 from Jenkins core. That cannot be done until core stops depending on it (including via Json-Lib), as discussed in this thread, and until plugins stop depending on core's copy. To track the latter I created this spreadsheet: https://d

Re: EC2 Fleet Plugin Adoption

Hi Brady, Looks like you've accepted the GitHub invitation. Welcome aboard! Now that https://github.com/jenkinsci/ec2-fleet-plugin/pull/405 has been merged, this plugin can be released manually as documented in https://www.jenkins.io/doc/developer/publishing/releasing-manually/ — or alternatively

Re: Plugin Adoption for kryptowire-plugin

tps://github.com/jenkinsci/kryptowire-plugin >>> Plugin on Plugins site: https://plugins.jenkins.io/kryptowire/ >>> My ci.jenkins.io Username: crdkw >>> My Github Username: cdowney-kryptowire >>> Original Contributor Github Username: odra >>> >

Re: Plugin Adoption for kryptowire-plugin

yptowire >> Original Contributor Github Username: odra >> >> Regards, >> >> Chris Downey >> Senior Product Manager, Kryptowire >> >> -- Forwarded message - >> From: Chris Downey >> Date: Wednesday, August 31, 2022 at 9:5

Re: Plugin Adoption for kryptowire-plugin

gins site: https://plugins.jenkins.io/kryptowire/ > My ci.jenkins.io Username: crdkw > My Github Username: cdowney-kryptowire > Original Contributor Github Username: odra > > Regards, > > Chris Downey > Senior Product Manager, Kryptowire > > ------ Forwarded mess

Re: Plugin-releasenotes not rendering

See also https://github.com/jenkins-infra/plugin-site/issues/2319 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.co

Re: Plugin-releasenotes not rendering

Björn Pedersen schrieb am Dienstag, 29. Juli 2025 um 11:41:11 UTC+2: michael...@visualon.de schrieb am Dienstag, 29. Juli 2025 um 09:58:13 UTC+2: Seeing this too. when using curl to fetch ` https://cdn.jsdelivr.net/npm/@jenkinsci/jenkins-io-components/`

Re: Plugin-releasenotes not rendering

michael...@visualon.de schrieb am Dienstag, 29. Juli 2025 um 09:58:13 UTC+2: Seeing this too. when using curl to fetch ` https://cdn.jsdelivr.net/npm/@jenkinsci/jenkins-io-components/` i get html code instead of a js file, that's

Re: Plugin-releasenotes not rendering

Seeing this too. when using curl to fetch `https://cdn.jsdelivr.net/npm/@jenkinsci/jenkins-io-components/` i get html code instead of a js file, that's why the browser is blocking it. content type is `text/html; charset=utf-8` instead of `application/javascript; charset=utf-8` -- You receive

Re: Plugin-releasenotes not rendering

damien@gmail.com schrieb am Montag, 28. Juli 2025 um 14:19:15 UTC+2: That is unexpected. Do you have the same result with culr/wget ? And with a private browsing session? Yes, also on different machines. Le lundi 28 juillet 2025 à 08:56:34 UTC+2, ice...@googlemail.com a écrit : Björn

Re: EC2 Fleet Plugin Adoption

Thanks. I approved the repository permissions PR. Once it is merged by a member of the hosting team, I can invite you to become a member of the jenkinsci GitHub organization. On Mon, Jul 28, 2025 at 4:45 PM Brady Shober wrote: > > Hello, just wanted to give a ping here since it has been a bit ove

Re: EC2 Fleet Plugin Adoption

Hello, just wanted to give a ping here since it has been a bit over two weeks without a response from any of the other maintainers of the plugin. Thanks, Brady On Wednesday, July 9, 2025 at 12:13:12 PM UTC-5 Brady Shober wrote: Hi Basil, I've CCd 2 of the other maintainers on this reply. Our A

Re: Plugin-releasenotes not rendering

Sent: Monday, July 28, 2025 2:19 PM To: Jenkins Developers Subject: Re: Plugin-releasenotes not rendering That is unexpected. Do you have the same result with culr/wget ? And with a private browsing session? Le lundi 28 juillet 2025 à 08:56:34 UTC+2, ice...@googlemail.com a écrit : Björn

Re: Plugin-releasenotes not rendering

That is unexpected. Do you have the same result with culr/wget ? And with a private browsing session? Le lundi 28 juillet 2025 à 08:56:34 UTC+2, ice...@googlemail.com a écrit : > Björn Pedersen schrieb am Montag, 28. Juli 2025 um 08:52:06 UTC+2: > > Hi, > > if you try to look up the release note

Re: Plugin-releasenotes not rendering

Björn Pedersen schrieb am Montag, 28. Juli 2025 um 08:52:06 UTC+2: Hi, if you try to look up the release notes of a plugin on the releases page, then they are not rendered. In the js-console I get `webpack-runtime-77f3…bf9413a6cafce1.js:1 Uncaught SyntaxError: Invalid or unexpected token`

Re: 2.516.1 BOM not produced?

Thanks again! On Fri, Jul 25, 2025 at 6:58 AM Adrien Lecharpentier < adrien.lecharpent...@gmail.com> wrote: > There, you have the first BOM release for 2.516.x branch: > https://github.com/jenkinsci/bom/releases/tag/5085.v05cc65a_936d3. > > Le jeu. 24 juil. 2025 à 21:43, Adrien Lecharpentier < >

Re: 2.516.1 BOM not produced?

There, you have the first BOM release for 2.516.x branch: https://github.com/jenkinsci/bom/releases/tag/5085.v05cc65a_936d3. Le jeu. 24 juil. 2025 à 21:43, Adrien Lecharpentier < adrien.lecharpent...@gmail.com> a écrit : > I'm bom release lead this week. > I scheduled the release to start at 7am

Re: 2.516.1 BOM not produced?

I'm bom release lead this week. I scheduled the release to start at 7am GMT. Hopefully, by Friday evening CEST, you should have the BOM for 2.516.1. Le jeu. 24 juil. 2025, 21:19, 'rsomas...@netflix.com' via Jenkins Developers a écrit : > Thanks! Sorry for the noise. > > On Thursday, July 24, 20

Re: 2.516.1 BOM not produced?

Thanks! Sorry for the noise. On Thursday, July 24, 2025 at 10:21:54 AM UTC-7 timja...@gmail.com wrote: > Bom is released weekly, normally on Fridays, see > https://github.com/jenkinsci/bom/issues/5352 > > On Thu, 24 Jul 2025 at 17:36, 'rsomas...@netflix.com' via Jenkins > Developers wrote: > >

Re: 2.516.1 BOM not produced?

Bom is released weekly, normally on Fridays, see https://github.com/jenkinsci/bom/issues/5352 On Thu, 24 Jul 2025 at 17:36, 'rsomas...@netflix.com' via Jenkins Developers wrote: > Hi! > > I'm looking at https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/ > Typically, the bom gets produced

Re: Debian sudo apt-get update does not work with pkg.jenkins.io anymore

Hi Stéphane! Thanks for your answer. I will ask our IT. I will get back to you asap. Stéphane Le mardi 22 juillet 2025 à 16:33:53 UTC+2, stephan...@gmail.com a écrit : > Hi Stéphane, > > can you provide us your outbounds ips ? > the blocking ip `199.232.58.133` is part of fastly ips: > https:/

Re: Release Lead for LTS 2.516.2

Hi, I am interested From: jenkinsci-dev@googlegroups.com on behalf of Mark Waite Sent: 23 July 2025 23:34 To: Jenkins Developers Subject: Release Lead for LTS 2.516.2 Hello The Jenkins 2.516.1 release has been delivered. We need a release lead for 2.516.2.

Re: Debian sudo apt-get update does not work with pkg.jenkins.io anymore

Hi Stéphane, can you provide us your outbounds ips ? the blocking ip `199.232.58.133` is part of fastly ips: https://www.fastly.com/documentation/reference/api/utils/public-ip-list/ Stéphane Merle For the infra team Le mar. 22 juil. 2025 à 11:23, Stéphane BOBIN a écrit : > Hi! > > I am trying

Re: [ci.jenkins.io] JDK25 early availability

Hello there, Thanks a lot, Stéphane, for making this possible! I truly appreciate the efforts of the infra team, along with Mark Waite, in bringing the JDK25 prerelease to ci.jenkins.io. I’ve already created a branch in one of the plugins I help co-maintain to test the waters, and I’m happy to re

Re: What's i18n message key string case style is recommend?

I fully agree with your preference for using the camel case style for i18n message keys, and I also support not migrating existing keys to avoid unnecessary risks and disruptions. At the same time, I wonder if we could go one step further and formally recommend this approach for future developm

Re: JetBrains and YourKit sponsor Jenkins maintainers with free licenses

I've assigned you a license on your account. On Friday, 11 July 2025 at 01:37:13 UTC+2 Mark Waite wrote: > I'd like a license for the JetBrains All Products Pack if it is available. > > I am a core maintainer and I maintain many plugins > https://plugins.jenkins.io/ui/search/?query=markewaite >

Re: JetBrains and YourKit sponsor Jenkins maintainers with free licenses

I'd like a license for the JetBrains All Products Pack if it is available. I am a core maintainer and I maintain many plugins https://plugins.jenkins.io/ui/search/?query=markewaite Mark Waite On Thursday, July 10, 2025 at 9:37:15 AM UTC-6 mc.ca...@gmail.com wrote: > Hi Valentin, > > I've sent

Re: Backporting for 2.516.1 LTS has started

A second backport was created and merged to stable-2.516 as part of 2.516.1. It include cherry picked commits from the pull request: - [JENKINS-75834] limit the functionality to a specific reference

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

On Mon, Jul 7, 2025 at 9:54 AM Alexander Brandes wrote: > > I'd be +1 for creating a dedicated namespace, like io.jenkins.lib, given the > efforts to reach out to past maintainers of the existing namespaces weren't > successful. > That way we could move on with the other open publishing requests

Re: JetBrains and YourKit sponsor Jenkins maintainers with free licenses

Hi Valentin, I've sent you an invitation to your email address. Please let me know if something doesn't work out. ~ Alex On Thursday, 10 July 2025 at 17:33:01 UTC+2 jone...@gmail.com wrote: > Hi, > > I'm interested by an IntelliJ IDEA Ultimate license. > > My GH handle is "jonesbusy". > > I ma

Re: JetBrains and YourKit sponsor Jenkins maintainers with free licenses

Hi, I'm interested by an IntelliJ IDEA Ultimate license. My GH handle is "jonesbusy". I maintains more than 45 plugins: https://plugins.jenkins.io/ui/search/?query=jonesbusy Thanks! On Wednesday, July 9, 2025 at 1:18:47 PM UTC+2 Alexander Brandes wrote: > Hi all, > > I'm excited to share tha

Re: EC2 Fleet Plugin Adoption

Hi Basil, I've CCd 2 of the other maintainers on this reply. Our AWS TAM was going to try reaching out to one of the other maintainers internally but we haven't heard back if that was successful or not. Thanks, Brady On Wed, Jul 9, 2025 at 11:24 AM Basil Crow wrote: > Hi Brady, > > Thanks for

Re: EC2 Fleet Plugin Adoption

Hi Brady, Thanks for stepping up to maintain this plugin. Can you please make a best-effort attempt to reach out to someone at AWS about this? CC'ing them on this thread should be fine. In the absence of explicit approval from an existing maintainer, we typically wait for about two weeks during no

Re: Request maintainer permission to the Jenkins Organization

Thank you all, team, I have been added to the JenkinsCI Org Best regards. On Wednesday, July 9, 2025 at 4:42:57 PM UTC+2 mc.ca...@gmail.com wrote: > I've sent you an invitation > > On Wednesday, 9 July 2025 at 16:24:04 UTC+2 jga...@cloudbees.com wrote: > >> Thanks Mark, >> >> Yes, you are right,

Re: Request maintainer permission to the Jenkins Organization

I've sent you an invitation On Wednesday, 9 July 2025 at 16:24:04 UTC+2 jga...@cloudbees.com wrote: > Thanks Mark, > > Yes, you are right, please add me as a member of the Jenkinsci > organisation on GitHub. > > Thanks in advance. > > On Wednesday, July 9, 2025 at 2:48:54 PM UTC+2 Mark Waite wr

Re: Request maintainer permission to the Jenkins Organization

Thanks Mark, Yes, you are right, please add me as a member of the Jenkinsci organisation on GitHub. Thanks in advance. On Wednesday, July 9, 2025 at 2:48:54 PM UTC+2 Mark Waite wrote: > On Wednesday, July 9, 2025 at 6:47:35 AM UTC-6 Javier Garcia wrote: > > Hi team, > > I hope you're doing we

Re: Request maintainer permission to the Jenkins Organization

On Wednesday, July 9, 2025 at 6:47:35 AM UTC-6 Javier Garcia wrote: Hi team, I hope you're doing well. Could you please grant maintainer permission to the Jenkins GitHub organization? - *GitHub username:* jgarciacloudbees - *Jenkins LDAP user:* jgarciacloudbees Thank

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Hi, I'd be +1 for creating a dedicated namespace, like io.jenkins.lib, given the efforts to reach out to past maintainers of the existing namespaces weren't successful. That way we could move on with the other open publishing requests as well. ~ Alex On Friday, 4 July 2025 at 01:22:54 UTC+2 m.

Re: p4sa plugin release 403 error

Hi, resolved. I was using a PAT that only had permissions to my repo's and not the jenkins owned plugin repo. Cheers, Michael On Wednesday, July 2, 2025 at 11:53:36 AM UTC+1 adrien.lec...@gmail.com wrote: > Hi, > > RPU is managing the permissions on artifactory, not GitHub. The path you >

Re: [Jenkins Infrastructure] maintenance on ci.jenkins.io

The operation finished successfully at 08:30am UTC. We don't see immediate failures, feel free to report in https://github.com/jenkins-infra/helpdesk/ if you see anything weird. Le lundi 7 juillet 2025 à 09:03:15 UTC+2, Damien Duportal a écrit : > Hi dear developers, > > The Jenkins infra. team

Re: Backporting for 2.516.1 LTS has started

I prepared a tentative second backport branch based on two pull requests that I expect to merge before the release of 2.518. Those two pull requests are: * https://github.com/jenkinsci/jenkins/pull/10791 * https://github.

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

On Thu, Jul 3, 2025 at 3:55 PM Basil Crow wrote: > > I propose we create a new namespace: io.jenkins.syslog Alternatively, should we create an io.jenkins.lib namespace and put both Syslog Java Client and Mock JavaMail there? -- You received this message because you are subscribed to the Google

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

> Hi Cyrille, On Tue, Mar 29, 2022 at 11:02 PM Basil Crow wrote: > Based on my reading of the Sonatype documentation, I think your > understanding is correct, but I would not necessarily assume that the > use of the "com.cloudbees" namespace by the Jenkins project for such > legacy libraries is f

Re: Adoption Request for Google Kubernetes Engine plugin

By the comment in https://github.com/jenkins-infra/repository-permissions-updater/pull/4501#issuecomment-2987831547 I retract my request. On Thursday, 19 June 2025 at 14:50:20 UTC+3 kris...@outlook.com wrote: > +1 from me > > Get Outlook for iOS > -

Re: p4sa plugin release 403 error

Hi, RPU is managing the permissions on artifactory, not GitHub. The path you see is the group id of sort of the plugin. Have you try to push commit in the repository without maven? On GitHub, please make sure you are part of the developer team (can be found on Jenkins on organisation). If not, o

Re: [DISCUSS] Current Status of Gatsby and Future Direction for Jenkins Websites

Hi, Thanks a lot for your message . Just to clarify, we’re not moving away from versioned documentation at all. The main idea behind the GSoC project is to modernize the Jenkins website setup ; not to change the contribution model or how docs are managed. We’re using Vite.js for the non-vers

Re: [DISCUSS] Current Status of Gatsby and Future Direction for Jenkins Websites

On Tue, Jul 1, 2025 at 5:10 PM Baptiste Mathus wrote: > I think this is extremely powerful to use drive-by-PR changes for > jenkins.io, and I have a hard time picturing us going back to using some > CMS or so? > I'm sure this means "No Jenkins version dropdown on the rendered site" instead of go

Re: [DISCUSS] Current Status of Gatsby and Future Direction for Jenkins Websites

Hey, > our Google Summer of Code 2025 project focused on building a *non-versioned documentation site* Is there a place to read more about this? I'm personally extremely surprised by this statement, and it would seem backward to me that we'd go away from using this concept. I think this is extrem

Re: Picking up new Kubernetes-client releases (6.14)

The coordinated release picking up Kubernetes-client 6.14 is done, and jackson2-api 2.19.0 has been unblocked from UC. I'll be running another set of releases some time next week to pick up Kubernetes-client 7.x, but as far as I can see there should only be impacts on test code, not on users. Vin

Re: 2.514 as 23 Jul 2025 LTS baseline

Sounds good On Fri, 27 Jun 2025 at 01:52, Mark Waite wrote: > > > On Tuesday, June 17, 2025 at 1:39:25 PM UTC-6 Mark Waite wrote: > > On Thursday, June 12, 2025 at 5:14:04 AM UTC-6 Mark Waite wrote: > > t is time to choose the next LTS baseline. The first release of that LTS > baseline is sched

Re: 2.514 as 23 Jul 2025 LTS baseline

On Tuesday, June 17, 2025 at 1:39:25 PM UTC-6 Mark Waite wrote: On Thursday, June 12, 2025 at 5:14:04 AM UTC-6 Mark Waite wrote: t is time to choose the next LTS baseline. The first release of that LTS baseline is scheduled for 23 Jul 2025. I recommend Jenkins 2.514, released Tuesday. There

Re: Mark Waite as 2.516.1 release lead

+1 from me too. Thanks, Mark! Get Outlook for iOS<https://aka.ms/o0ukef> From: 'Kevin Martens' via Jenkins Developers Sent: Thursday, June 26, 2025 9:31:10 PM To: jenkinsci-dev@googlegroups.com Subject: Re: Mark Waite as 2.516.1 release lead +1

Re: Mark Waite as 2.516.1 release lead

+1 from me, thanks Mark! On Thu, Jun 26, 2025 at 9:27 AM Mark Waite wrote: > I'd like to be the release lead for the next Jenkins LTS release, > scheduled for July 23, 2025. > > https://groups.google.com/g/jenkinsci-dev/c/HsNnU6rE-GA/m/dTOb7UxgAAAJ is > where I first mentioned it. > > Mark Waite

Re: Reflection API - a weird test failure while bumping pom to next LTS

On Sat, Jun 21, 2025 at 10:04 AM Radek Antoniuk wrote: > this was intentional but I couldn’t find it in the release notes > Because this was an internal change. If you are using Mockito in tests, you are in general going to need to be constantly adjusting your tests according to implementation c

Re: Reflection API - a weird test failure while bumping pom to next LTS

Thanks Vincent, that was exactly the confirmation I wanted that this was intentional but I couldn’t find it in the release notes. Appreciate it! On 20 Jun 2025 at 10:36 +0200, Vincent Latombe , wrote: > > and suddenly it's needed after bumping the LTS. > > The implementation changed and now it r

Re: Reflection API - a weird test failure while bumping pom to next LTS

> and suddenly it's needed after bumping the LTS. The implementation changed and now it relies on having a valid Jenkins context as it relies on resolving implementation of an extension point (wasn't the case before). Vincent Le mar. 17 juin 2025 à 19:29, 'Jesse Glick' via Jenkins Developers <

Re: Listener when an branch is deleted

On Thu, Jun 19, 2025 at 10:51 AM Valentin Delaye (jonesbusy) < jonesb...@gmail.com> wrote: > …when a branch is deleted (for example via UI when it's disabled). > > By checking logs the onDeleted() is just not called. > > Is it expected behavior? > No, I do not think so. I'm not sure about other

Re: Proposal: Move Firefox ESR to Level two browser support

We're not testing Firefox ESR in ATH, and I don't think there is enough benefit for us to start testing Firefox ESR in ATH. On a side note, we're not testing Chrome in ATH either, even though that is the most commonly used browser. https://github.com/jenkinsci/acceptance-test-harness/issues/2025 tr

Re: 2.514 as 23 Jul 2025 LTS baseline

--- >> *From:* jenkin...@googlegroups.com on >> behalf of Verachten Bruno >> *Sent:* 18 June 2025 04:51 >> *To:* jenkin...@googlegroups.com >> *Subject:* Re: 2.514 as 23 Jul 2025 LTS baseline >> >> That's fine with me. >> Tha

Re: 2.514 as 23 Jul 2025 LTS baseline

:* 18 June 2025 04:51 > *To:* jenkin...@googlegroups.com > *Subject:* Re: 2.514 as 23 Jul 2025 LTS baseline > > That's fine with me. > Thanks, Mark! > > Bruno Verachten > > On Tue, Jun 17, 2025, 21:39 Mark Waite wrote: > > > > On Thursday, June 12,

Re: Adoption Request for Google Kubernetes Engine plugin

+1 from me Get Outlook for iOS From: jenkinsci-dev@googlegroups.com on behalf of Vilius Šumskas Sent: Thursday, June 19, 2025 7:26:59 PM To: Jenkins Developers Subject: Adoption Request for Google Kubernetes Engine plugin Hello, I would

Re: 2.514 as 23 Jul 2025 LTS baseline

Great to have you as the release lead of the next .1 release, Mark! From: jenkinsci-dev@googlegroups.com on behalf of Verachten Bruno Sent: 18 June 2025 04:51 To: jenkinsci-dev@googlegroups.com Subject: Re: 2.514 as 23 Jul 2025 LTS baseline That's fine wi

Re: 2.514 as 23 Jul 2025 LTS baseline

That's fine with me. Thanks, Mark! Bruno Verachten On Tue, Jun 17, 2025, 21:39 Mark Waite wrote: > > > On Thursday, June 12, 2025 at 5:14:04 AM UTC-6 Mark Waite wrote: > > t is time to choose the next LTS baseline. The first release of that LTS > baseline is scheduled for 23 Jul 2025. > > I re

Re: 2.514 as 23 Jul 2025 LTS baseline

On Thursday, June 12, 2025 at 5:14:04 AM UTC-6 Mark Waite wrote: t is time to choose the next LTS baseline. The first release of that LTS baseline is scheduled for 23 Jul 2025. I recommend Jenkins 2.514, released Tuesday. There are some pending pull requests that will likely need to be back

Re: Reflection API - a weird test failure while bumping pom to next LTS

On Tue, Jun 17, 2025 at 10:57 AM Radek Antoniuk wrote: > proper integration tests with `JenkinsRule` or one of its variants. > > > By the variants you mean @WithJenkins @WithoutJenkins, right? > I actually meant `JenkinsSessionRule` and `RealJenkinsRule`. `@WithJenkins` is I guess the JUnit 5 ve

Re: Request to Archive crossbrowsertesting-plugin (SmartBear)

Thank you, Mark! On Tuesday, June 17, 2025 at 12:08:30 PM UTC-4 Mark Waite wrote: > On Tuesday, June 17, 2025 at 7:58:06 AM UTC-6 Jonathan Parrilla wrote: > > Thank you, Mark. I appreciate the fast turnaround on this. > > Please let me know once the repo itself has been archived - > https://gith

Re: Request to Archive crossbrowsertesting-plugin (SmartBear)

On Tuesday, June 17, 2025 at 7:58:06 AM UTC-6 Jonathan Parrilla wrote: Thank you, Mark. I appreciate the fast turnaround on this. Please let me know once the repo itself has been archived - https://github.com/jenkinsci/crossbrowsertesting-plugin https://github.com/jenkinsci/crossbrowsertesti

Re: Adoption Request for Categorized View Plugin

Hi Lukas, Thank you for your interest in adopting the Categorized View Plugin for Jenkins. We appreciate your willingness to contribute to the project and maintain this plugin. Best regards, On Tue, Jun 17, 2025 at 5:15 PM Kris Stern wrote: > +1 from me > -- > *From

Re: Adoption Request for Categorized View Plugin

+1 from me From: jenkinsci-dev@googlegroups.com on behalf of Lukas Mundt Sent: 17 June 2025 22:06 To: Jenkins Developers Subject: Adoption Request for Categorized View Plugin Hi everyone, based on Marks suggestion on https://github.com/jenkinsci/categorized-vi

Re: Reflection API - a weird test failure while bumping pom to next LTS

> In general, if you use Mockito in Jenkins tests, you should expect to be > forced to edit existing test suites after even compatible changes to core or > plugin dependencies. That's fine, I was just making sure in this specific case this isn't something that slipped through the core tests. >

Re: Request to Archive crossbrowsertesting-plugin (SmartBear)

Thank you, Mark. I appreciate the fast turnaround on this. Please let me know once the repo itself has been archived - https://github.com/jenkinsci/crossbrowsertesting-plugin On Tuesday, June 17, 2025 at 8:49:47 AM UTC-4 Mark Waite wrote: > On Monday, June 16, 2025 at 3:57:15 PM UTC-6 Mark Wait

Re: Request to Archive crossbrowsertesting-plugin (SmartBear)

On Monday, June 16, 2025 at 3:57:15 PM UTC-6 Mark Waite wrote: On Monday, June 16, 2025 at 3:21:38 PM UTC-6 Jonathan Parrilla wrote: Hi, I’m writing on behalf of SmartBear, the original maintainer of the CrossBrowserTesting plugin. The CrossBrowserTesting (CBT) service has officially b

Re: Request to Archive crossbrowsertesting-plugin (SmartBear)

On Monday, June 16, 2025 at 3:21:38 PM UTC-6 Jonathan Parrilla wrote: Hi, I’m writing on behalf of SmartBear, the original maintainer of the CrossBrowserTesting plugin. The CrossBrowserTesting (CBT) service has officially been discontinued, and the plugin is no longer in use or functio

Re: Reflection API - a weird test failure while bumping pom to next LTS

In general, if you use Mockito in Jenkins tests, you should expect to be forced to edit existing test suites after even compatible changes to core or plugin dependencies. It is safer to divide test code into true unit tests (no mocking framework) plus proper integration tests with `JenkinsRule` or

Re: Any plan to move from guice 6 to guice 7?

On Fri, May 30, 2025 at 4:15 PM Basil Crow wrote: > Even if […] someone were to extract Guice from core into a Jenkins library > plugin […] I think we would still be unable to upgrade the Guice library plugin from 6 > to 7 unless we were to > > > fix MNG-8027, officially drop support for the Jen

Re: Switch Jenkins Core release build from jdk17 to jdk21

Noting this possibly caused https://github.com/jenkins-infra/helpdesk/issues/4705 I doubt there is anything that can be done about it now, but maybe something to think about for the next Java bump. On Tuesday, June 3, 2025 at 2:21:13 PM UTC+1 damien@gmail.com wrote: > Hello folks, quick r

Re: Proposal: Move Firefox ESR to Level two browser support

Agreed, with the same reason as in https://github.com/jenkins-infra/jenkins.io/pull/8191#pullrequestreview-2932149819 > On 16. Jun 2025, at 15:30, Tim Jacomb wrote: > > Hi all, > > Based on feedback on https://github.com/jenkinsci/jenkins/pull/10078 > > I've raised this proposal >

Re: Proposal: Move Firefox ESR to Level two browser support

+1 from me too From: 'Kevin Martens' via Jenkins Developers Sent: 16 June 2025 21:39 To: jenkinsci-dev@googlegroups.com Subject: Re: Proposal: Move Firefox ESR to Level two browser support Definitely agree, +1 from me On Mon, Jun 16, 2025 at 9:36 AM

Re: Proposal: Move Firefox ESR to Level two browser support

Definitely agree, +1 from me On Mon, Jun 16, 2025 at 9:36 AM 'Alexander Brandes' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Agreed, with the same reason as in > https://github.com/jenkins-infra/jenkins.io/pull/8191#pullrequestreview-2932149819 > > > On 16. Jun 2025, at 15:3

Re: Adoptt a plugin - job-config-history-plugin

" - that was sent at the end of last > month and still does not show. I just checked and found these headers: Subject: Re: Any plan to move from guice 6 to guice 7? From: Fritz Elfert To: Basil Crow So you sent the reply to me directly but not to the list. I suggest using the "Repl

Re: Reflection API - a weird test failure while bumping pom to next LTS

You need a valid Jenkins context to use this class. Simply removing @WithoutJenkins annotation from the test method should fix it. Vincent Le ven. 13 juin 2025 à 12:19, Radek Antoniuk a écrit : > I'm updating the jira-plugin to the next LTS and one test suddenly started > failing with: > > Fou

Re: Adoptt a plugin - job-config-history-plugin

Well, it was when I sent this mail a few days ago. He just forgot to remove the label. For some unknown reason, my mails to this list always get delayed for several days or even filtered completely. Like my answer to Basil on the topic "Any plan to move from guice 6 to guice 7?" - that was sent

Re: Adopt Image Tag Parameter plugin

Granted, welcome aboard On Saturday, 7 June 2025 at 14:56:51 UTC+2 dodo9...@gmail.com wrote: > Hi, > I would like to adopt a plugin: > > Link: https://github.com/jenkinsci/image-tag-parameter-plugin > Pull requests (optional): > https://github.com/jenkinsci/image-tag-parameter-plugin/pu

Re: Adoptt a plugin - job-config-history-plugin

Hi Fritz, The plugin is not up for adoption. It has just been adopted recently by Stefan Spieker. ~ Alex > On 7. Jun 2025, at 15:19, 'Fritz Elfert' via Jenkins Developers > wrote: > > Hi, > > I would like to adopt a plugin: > >Link: https://github.com/jenkinsci/job-config-history-plug

Re: Adopt a plugin - Gatling

On Monday, June 2, 2025 at 10:16:33 AM UTC-6 Mark Waite wrote: On Monday, June 2, 2025 at 10:15:20 AM UTC-6 Vedanth wrote: Hello, I would like to be the owner of the gatling plugin as it isn't maintained anymore. Link: https://plugins.jenkins.io/gatling/ ( https://github.com/jenkinsci/gatlin

Re: Switch Jenkins Core release build from jdk17 to jdk21

Hello folks, quick reminder that we want to have the weekly release 2.514 to be built with JDK21 (instead of JDK17) so that we have the same behavior between ci and CD (and infra can move forward on the LTS support). Without any objections, we'll move forward to this planning (e.g. Tuesday 10 J

Re: Incrementals builds are not published for bitbucket-source-plugin

The same happens for other plugins i managed like nodejs-plugin, dependecy-check, xunit-plugin Thanks I'm try the patch Il giorno martedì 3 giugno 2025 alle 01:58:20 UTC+2 m...@basilcrow.com ha scritto: > This ought to do the trick: > > diff --git a/pom.xml b/pom.xml > index 529c0e2..4d2cce0 10

Re: Incrementals builds are not published for bitbucket-source-plugin

This ought to do the trick: diff --git a/pom.xml b/pom.xml index 529c0e2..4d2cce0 100644 --- a/pom.xml +++ b/pom.xml @@ -64,7 +64,7 @@ scm:git:https://github.com/${gitHubRepo}.git scm:git:g...@github.com:${gitHubRepo}.git https://github.com/${gitHubRepo} -936.3.1 +

Re: Adopt a plugin - Gatling

On Monday, June 2, 2025 at 10:15:20 AM UTC-6 Vedanth wrote: Hello, I would like to be the owner of the gatling plugin as it isn't maintained anymore. Link: https://plugins.jenkins.io/gatling/ ( https://github.com/jenkinsci/gatling-plugin) Status: Up for adoption Link to pull request: https://

Re: Adopt a plugin android-signin-plugin

Hi On Mon, Jun 2, 2025 at 9:38 AM Verachten Bruno wrote: > > Michael, > > Thank you for expressing interest in adopting the Android Signing Plugin for > Jenkins. We appreciate your willingness to help and contribute to the > maintenance of the plugin. > Have you had a chance to contact the curr

Re: Adopt a plugin android-signin-plugin

Michael, Thank you for expressing interest in adopting the Android Signing Plugin for Jenkins. We appreciate your willingness to help and contribute to the maintenance of the plugin. Have you had a chance to contact the current maintainer, @restjohn? Best regards, On Mon, Jun 2, 2025 at 9:13 AM

Re: Any plan to move from guice 6 to guice 7?

On Fri, May 30, 2025 at 11:27 AM 'Jesse Glick' via Jenkins Developers wrote: > Better still (IMHO) would be to remove the Guice dep from core This problem is orthogonal to the one being discussed in this thread, I think. Even if, by some great effort, someone were to extract Guice from core into

Re: [jira-plugin] move bug reporting to github issues

Thanks Tim, I used your write-up and migrated all unresolved issues in a flash! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...

Re: Any plan to move from guice 6 to guice 7?

On Fri, May 30, 2025 at 1:55 PM Basil Crow wrote: > in the long term Jenkins core should upgrade to Guice 7 > Better still (IMHO) would be to remove the Guice dep from core, letting it just be loaded as a regular library wrapper plugin for the handful of plugins needing it (for example via jclou

  1   2   3   4   5   6   7   8   9   10   >