Re: Proposal: newsletter mailing list for contributor announcements

I added a rss bot to jenkinsci/jenkins gitter channel, but since I don't have admin in the gitter i can't add subscriptions in theory, ` !rss subscribe https://feeds.feedburner.com/ContinuousBlog/` should be enough to make it work. If that does, we can have rss from discourse too On Fri, Jun 11,

Re: Proposal: newsletter mailing list for contributor announcements

After the introduction of community.jenkins.io, maybe creating a mailing list does not make sense anymore. There is already a category for announcements created by Olivier: https://community.jenkins.io/t/about-the-announcement-category/40 Instead of the original idea, I suggest the following:

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

I'm sorry to be so late on this... I am going to write here for visibility, and I'll also add or see to add it correctly the sheet initiated by Oleg. 1. I would like to help facilitate a conversation on Guava upgrade in Jenkins Core. As you know, this work is already somehow started. I'd like us

Re: ASM in core

On Fri, Jun 11, 2021 at 2:19 AM Robert Sandell wrote: > > Some historical context to know where we "old timers" are coming from :) > https://kohsuke.org/2012/03/03/potd-package-renamed-asm/ Thanks for providing this context, Robert! I have a tremendous amount of respect for all the old-timers in

Re: ASM in core

On Fri, Jun 11, 2021 at 3:45 AM Ullrich Hafner wrote: > > Wouldn’t it be helpful if we would also suggest which option we prefer? > Otherwise every plugin author needs to rethink the same options again and > again. > > E.g., option 1 did break all my integration tests with the token macro

Re: ASM in core

On June 11, 2021 10:18:30 AM UTC, kuisathaverat wrote: >Robert, Which plugin are you talking about? Which version of the core >is >that plugin required as minimum? there is another topic opened a few >weeks >ago about deprecated plugins, a plugin should bump it core minimum >required >version and

Re: How to create a pre-release testing environment ?

Thanks for your input. That's what I thought. -- [image: Martin Goyot] [image: Logo Tuleap] Martin Goyot +33.7.66.39.17.39 Consultant and Tuleap trainer Enalean SAS - Tuleap [image: Linkedin Tuleap] [image: Tuleap website]

Re: How to create a pre-release testing environment ?

You get either all or nothing. There is no way to use filters for the experimental update center (as far as I know). I’m testing my plugins by simply copying the HPI (or JPI) files to a docker based Jenkins installation. All other plugins are the latest stable ones, just my plugins are the

How to create a pre-release testing environment ?

Hi there, I've seen https://www.jenkins.io/doc/developer/publishing/releasing-experimental-updates/ but I'm not sure it answers completely my need. I would like to be able to test my plugins before releasing them. In order to do so, and relying on the experimental updates system, I'd like to

Re: ASM in core

> > In general, when a plugin depends on a library already provided by > core, I have seen three approaches in the short term: > > 1. Exclude the library on the plugin side (e.g. how Token Macro excludes ASM) > 2. Mask the library's classes (e.g. how JaCoCo masks ASM classes) > 3. Shade the

Re: ASM in core

Robert, Which plugin are you talking about? Which version of the core is that plugin required as minimum? there is another topic opened a few weeks ago about deprecated plugins, a plugin should bump it core minimum required version and update its dependencies often, if not it is not possible to

Re: ASM in core

Some historical context to know where we "old timers" are coming from :) https://kohsuke.org/2012/03/03/potd-package-renamed-asm/ There are several times where I've needed to shade asm in plugins because of some transitive dependency. Las time I think it was a dependency on ASM7 that blew up

Re: ASM in core

Hi, I would like to add an issue related to not bump the ASM library, I recently hit an issue with stapler (see https://groups.google.com/g/jenkinsci-dev/c/JppfFwqIrCU) and it is related to compile the plugin for JDK 11 only, new plugins use new libraries and more and more libraries use JDK 11