Re: Spring Security upgrade from 5.x to 6.x

Sounds good to me On Sat, 11 May 2024 at 04:08, Mark Waite wrote: > > > On Friday, May 10, 2024 at 12:51:46 PM UTC-6 Basil wrote: > > Based on my prototyping in JENKINS-73120, there is quite a bit of work > to support Jetty 12 (even just EE 8 with javax imports), blocked on > the requirement of

Re: SCM plugin with Multi-Branch Pipeline throwing InaccessibleObjectException

I find in my IDE (IntelliJ) sometimes I need to add the `--add-opens` to command line arguments for hpi:run On Mon, 22 Apr 2024 at 13:15, 'Jesse Glick' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > How are you running Jenkins when you see this? Should not occur when > either

Re: Windows-arm64 native support

>From my point of view GitHub actions is fine. I don’t think we want to add something that takes so long to install to our image builds. This isn’t something we really want to maintain but it needed updating for something and it has no one actively maintaining it. I’m not sure if any of our

Re: Remove Suggestimate from issues.jenkins.io?

According to their website it's free for open source projects: https://enhancera.com/jira/suggestimate/buy.html I think it's just in a bit of a state of confusion due to Atlassian's retirement of server and our moving to data center. Is it worth trying to get the plugin relicensed, e.g. does it

Re: 2.440 as Feb 21, 2024 LTS baseline?

+1 On Sat, 13 Jan 2024 at 08:51, 'Alexander Brandes' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > 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

Re: Github webhook push events delays in SCM API plugin

You aren’t getting rate limited by GitHub are you? We use the open telemetry plugin to show a dashboard with the remaining rate limit of all the credentials. If you give a bit more info about your setup or thread dumps it may be possible to see where the delays are coming from On Tue, 19 Dec

Re: Github webhook push events delays in SCM API plugin

The thread pool is initialised when the first event is received. There's not much point making it editable at runtime I think. If you are hitting delays run "jenkins.scm.api.SCMEvent.executorService" In the script console and see if you have any queued. We run with 40 threads using that system

Re: 2.426 as Nov 15, 2023 LTS baseline?

Confirmed On Fri, 13 Oct 2023 at 23:23, Mark Waite wrote: > Tim Jacomb, can you confirm that 2.426 is approved as the next LTS > baseline? > > Thanks, > Mark Waite > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Dev

Re: Proposal: Kris Stern to join the release team

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

Re: [Information] Release block "Beta" program

h any bots that can auto merge when CI checks >> pass, e.g. renovate and dependabot, whereas a locked branch will work. >> >> On Tue, 5 Sep 2023 at 17:48, Tim Jacomb wrote: >> >>> Why not lock the branch instead? >>> That means it won’t break review appro

Re: [Information] Release block "Beta" program

Also this won’t work with any bots that can auto merge when CI checks pass, e.g. renovate and dependabot, whereas a locked branch will work. On Tue, 5 Sep 2023 at 17:48, Tim Jacomb wrote: > Why not lock the branch instead? > That means it won’t break review approvals in the meantime and

Re: [Information] Release block "Beta" program

Why not lock the branch instead? That means it won’t break review approvals in the meantime and things like enabling auto merge for when the release block is over On Tue, 5 Sep 2023 at 17:13, 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > Dear plugin maintainers, > > *Context* > In

Re: Jenkins 2.413 as next LTS baseline?

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 < jenkinsci-dev@googlegroups.com> wrote: > > 2.415 appears to have a regression in the dialog handling that I just > found with

Re: Jenkins 2.413 as next LTS baseline?

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

Re: Jenkins 2.413 as next LTS baseline?

in the release notes. > > > Thanks for noting those needed additions to the upgrade guide. Since > those changes are in Jenkins 2.413 and in Jenkins 2.414, it makes sense to > me that we choose Jenkins 2.414. > > Tim Jacomb, do you agree that Jenkins 2.414 should be the baseline

Re: Drop 2.375.x support from plugin bom

+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

Re: Requesting admin access to the jenkinsci GitHub organization

I've added Basil as an organisation owner On Tue, 13 Jun 2023 at 07:50, 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > +1 > > On Tuesday, June 6, 2023 at 10:36:39 AM UTC+2 Adrien Lecharpentier wrote: > >> +1 as well from me. >> >> Le mar. 6 juin 2023, 10:15, Baptiste Mathus a écrit :

Re: Backporting for LTS 2.401.2 has started

+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

Re: Requesting Admin access to the jenkinsci organization

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

2.401.2 release lead

Hello Is anyone interested in being the release lead for 2.401.2? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 14th June Release on 28th June The documentation is at:

Release lead for 2.401.1

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:

Re: Prototype.js replacing JSON.stringify

I think pull requests are now open for all of the core usage of prototype. and a PR for bom and ATH which removes prototype in https://github.com/jenkinsci/jenkins/pull/7781 Basil has opened a PR with a feature flag that you can use to disable prototype and do some more testing / developing of

Re: Jenkins 2.401 as next LTS baseline?

Yes On Thu, 27 Apr 2023 at 17:34, Mark Waite wrote: > Based on the feedback, Tim Jacomb are you OK with the selection of 2.401 > as the next LTS baseline? > > Mark Waite > > -- > You received this message because you are subscribed to the Google Groups > &q

Re: Reimbursement for code signing certificate

+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"),

Release lead for 2.387.3

Hello Is anyone interested in being the release lead for 2.387.3? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 19th April (apologies for short notice can be a little late if needed) Release on 3rd May The documentation is

Re: script to configure repository labels

It can be setup at the org level as a repository default, Gavin also had an app where you could click a button and it would set it all up for your repository On Fri, 31 Mar 2023 at 13:23, Ullrich Hafner wrote: > I am using the action > > >

Re: Prototype.js replacing JSON.stringify

++NOT+repo%3Ajenkinsci%2Fjenkins+=code=1 If anyone wants to help they could either test the above pull request or submit some pull requests to other plugins. Thanks Tim On Tue, 14 Mar 2023 at 08:06, Tim Jacomb wrote: > I've made a start: > https://github.com/jenkinsci/jenkins/pull/7727 >

Re: New maintainer for Jenkins Operator

+ jenkinsci-dev On Fri, 24 Mar 2023 at 15:12, 'Piotr Ryba' via Jenkins Cloud Native SIG < jenkins-cloud-native-...@googlegroups.com> wrote: > Hello, > > My name is Peter, I work at VirtusLab and am part of the team maintaining > the Jenkins Operator

Re: 2.387.2 RC?

Nope I just forgot to send the release lead email. Is there anyone able to do it? Thanks Tim On Mon, 20 Mar 2023 at 16:42, Baptiste Mathus wrote: > Hi all, > > @Tim in the calendar, the 2.387.2 RC is supposed to go out this Wednesday > the 22nd . > Is the

Re: Prototype.js replacing JSON.stringify

I've made a start: https://github.com/jenkinsci/jenkins/pull/7727 This PR is also removing some prototype as well: https://github.com/jenkinsci/jenkins/pull/7718 On Mon, 13 Mar 2023 at 22:27, 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > My knowledge of core is

Re: Jenkinsci Cloudevents plugin

Given the plugins implement different specifications without being too close to the details I would suggest a new plugin even if it’s based on the existing one. There’s no need to confuse users with having a different spec in the artefact id On Tue, 7 Mar 2023 at 19:47, Mark Waite wrote: > > >

Re: Managing clouds UI in Jenkins

ud config > when i click test connection was failing, but that required page navigation > and the to expand the options. So all the nodes where via one cloud > provider. > John > > > On Thu, 19 Jan 2023 at 11:32, Tim Jacomb wrote: > >> Seems reasonable to me although a

Re: Next LTS baseline

I've added the RC dates and the start of the line after next to take us out to May On Mon, 6 Feb 2023 at 18:29, Mark Waite wrote: > On Monday, February 6, 2023 at 11:07:12 AM UTC-7 Alex Brandes wrote: > Does someone mind adding new release dates to the calendar with the new > baseline, please?

2.387. 1 release lead

Hello Is anyone interested in being the release lead for 2.387.1? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 22nd February Release on 8th March The documentation is at:

Re: Next LTS baseline

2.387 has been selected as the next baseline Cheers Tim On Sun, 29 Jan 2023 at 15:21, Oleg Nenashev wrote: > Belated +1 > > On Wednesday, January 25, 2023 at 3:36:25 AM UTC+1 Mark Waite wrote: > >> +1 from me for 2.387. >> >> On Tuesday, January 24, 2023 at 2:30:47 AM UTC-7 mc.ca...@gmail.com

Re: Removing inactive Core maintainers to reduce risk

While I’m very much +1 for the change I think it should’ve been discussed on the mailing list publicly On Sun, 29 Jan 2023 at 13:52, 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > Thanks for the positive feedback! > > > we decided > Decision was made between Damien and me. > It was

Next LTS baseline

Hi all, It's time to select the next LTS baseline. The best candidate right now appears to be 2.387 See recent changelogs: https://www.jenkins.io/changelog/ Thanks Tim -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: Managing clouds UI in Jenkins

Seems reasonable to me although a prototype would allow giving better feedback :) On Thu, 19 Jan 2023 at 09:55, Vincent Latombe wrote: > Hello, > > I've been looking at cloud configuration recently, and these are my naive > thoughts about it. Let me know what you think of it. > > Clouds

2.375.3 release lead

Hello Is anyone interested in being the release lead for 2.375.3? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 25th January Release on 8th February The documentation is at:

Re: Migration to Java11 and modules

I'm not aware of hitting any modules issues, this is the normal pull request that has been applied: https://github.com/jenkinsci/support-core-plugin/pull/421 at a guess 30+ plugins with no issues, likely more. On Tue, 3 Jan 2023 at 13:08, Ullrich Hafner wrote: > I’m currently starting the Java

2.375.2 release lead

Hello Is anyone interested in being the release lead for 2.375.2? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 14th December Release on 11th January The documentation is at: https://github.com/jenkins-infra/release

Re: Revert of breadcrumb bar accessibility change

Jan has offered a partial reversion instead of a full one https://github.com/jenkinsci/jenkins/pull/6912#issuecomment-1331319966 I think that would be more appropriate here given the issue is only with one particular part of it On Fri, 9 Dec 2022 at 16:05, 'wfoll...@cloudbees.com' via Jenkins

Re: JDK19 is now available on ci.jenkins.io

I would prefer not to have that, UI will be weird and confusing I think. Interested maintainers can opt-in On Fri, 9 Dec 2022 at 07:57, 'Stephane Merle' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > We were thinking of renaming jdk19 to jdk-edge and have this version >

Re: JDK19 is now available on ci.jenkins.io

Personally I'm not the biggest fan of edge I'd rather get a clear error that the Java version has been removed or a deprecation error in my build than the Java versions has been randomly changed to another major version. I think that we would want a deprecation period after 20 is out (and maybe

Re: Next baseline shift

+1 to any time after 2.375.1 On 28 Nov 2022 at 22:38:58, Basil Crow wrote: > On Mon, Nov 28, 2022 at 1:30 PM 'Jesse Glick' via Jenkins Developers > wrote: > > Not really any of those […] I was soliciting opinions on whether it > sounded desirable and safe enough to try > > > And I was

Re: End of year holidays and Jenkins 2.375.2 release schedule

Is there an issue with what’s already in the calendar? On Tue, 22 Nov 2022 at 16:32, 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > For the delay of the LTS realease, with pleasure! :-) > > For the RC, no opinion. > > On Tuesday, November 22, 2022 at 3:53:47 PM UTC+1 Mark Waite wrote:

2.375.1 release lead

Hello Is anyone interested in being the release lead for 2.375.1? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 16th November Release on 30th November The documentation is at:

Re: Next LTS baseline selection

Hi all 2.375 is selected as the next baseline. Thanks Tim On Mon, 31 Oct 2022 at 21:18, Tim Jacomb wrote: > https://issues.jenkins.io/browse/JENKINS-69966 is very much a real issue, > but it has a fix on the plugin so I wouldn't worry too much about it. > > 2.375 looks to be a g

Re: Next LTS baseline selection

https://issues.jenkins.io/browse/JENKINS-69966 is very much a real issue, but it has a fix on the plugin so I wouldn't worry too much about it. 2.375 looks to be a good baseline to me. On Fri, 28 Oct 2022 at 14:21, Alexander Brandes wrote: > As an alternative to 2.375, I'd like to bring up

Re: Hosting

;> >>>>>>> The job entails monitoring PRs on >>>>>>> https://github.com/jenkins-infra/repository-permissions-updater >>>>>>> Making sure the request is either approved from an existing >>>>>>> maintainer, the p

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

gt;>>> wrote: >>>>>>>> >>>>>>>>> +1 >>>>>>>>> >>>>>>>>> On Thu, Oct 13, 2022 at 10:12 AM 'Kevin Martens' via Jenkins >>>>>>>>> Developers wrote: >>&

Re: ATH broswer supprt

I highly doubt it works, fine to remove I think On Fri, 14 Oct 2022 at 15:43, 'jn...@cloudbees.com' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi all, > > Does anyone use the HTMLUnit browser in the jenkins > acceptance-test-harness suite? > > I am doing some cleaning and

Proposal: Alexander Brandes (@NotMyFault) to join the Core team

Hi I would like to propose Alexander Brandes (@NotMyFault ) to join the Jenkins Core team. Contributions: - Pull requests (108) (in jenkinsci/jenkins) -

2.361.3 release lead

Hello Is anyone interested in being the release lead for 2.361.3? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 19th October Release on 2nd November The documentation is at: https://github.com/jenkins-infra/release

Re: [Adoption] thin-backup-plugin

He approved it via GiHub On Mon, 26 Sep 2022 at 12:31, Oleg Nenashev wrote: > +1. Note that there were recent updates by Thomas Fuerer 16 days ago: > https://github.com/jenkinsci/thin-backup-plugin/pull/30 > It would be nice to have explicit confirmation from him just in case > > On Sunday,

Re: pipeline-graph-view-plugin on infra.ci.jenkins.io

+1 On Fri, 16 Sep 2022 at 18:01, 'Herve Le Meur' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hello, > > https://github.com/jenkinsci/pipeline-graph-view-plugin/ has received a > lot of updates lately, and we would like to install it on > infra.ci.jenkins.io in order to test

2.361.2 release lead

Hello Is anyone interested in being the release lead for 2.361.2? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 21st September Release on 5th October The documentation is at: https://github.com/jenkins-infra/release

Re: ASM in core

If core no longer uses it the. Yes absolutely +1 On Thu, 18 Aug 2022 at 05:40, Basil Crow wrote: > Recent weeklies no longer consume ASM. So shall we detach it to a > library plugin? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group.

Re: Forked repositories in GitHub

es/2272#issuecomment-1216867119 >>> >>> >>> Any objections or +1s? >>> >>> Thanks >>> Tim >>> >>> On Wed, 4 Aug 2021 at 16:52, Tim Jacomb wrote: >>> >>>> I replied with Daniel's support ticket number (569994

Re: Forked repositories in GitHub

GitHub support have offered to make the jenkinsci organisation the root of all of the fork networks See https://github.com/jenkins-infra/helpdesk/issues/2272#issuecomment-1216867119 Any objections or +1s? Thanks Tim On Wed, 4 Aug 2021 at 16:52, Tim Jacomb wrote: > I replied with Danie

Re: Merging multiple build steps into one (with nested Describables)

What version are you building against? I think recent weekly (and the upcoming LTS) has that help issue fixed RE: design library and warnings, mind filing an issue for that? On Sun, 14 Aug 2022 at 17:14, Tim Van Holder wrote: > Hi, > > I'm in the process of adjusting a plugin that has a dozen

Re: Prettier for formatting supported languages in Jenkins core

We have eslint as well to do things like what you said My preference is for opinionated formatters so we don’t have to worry about debating options and it does a really good job by just automatically formatting it, you don’t get red lines in your IDE as you type distracting you like you do with

Re: Updating Azure Artifact Manager plugin to use Azure CDN

I think you want to change either: https://github.com/jenkinsci/azure-artifact-manager-plugin/blob/master/src/main/java/com/microsoft/jenkins/artifactmanager/AzureBlobVirtualFile.java#L178-L185 or

Re: How to align a checkbox with an optionalBlock vertically?

If you share a branch with the code you have that is not working how you want someone is more likely to be able to help On Fri, 12 Aug 2022 at 08:05, Nikhil Bhoski wrote: > Any input on this would be appreciated. Is it a Bug in Jenkins Jelly > format that optional block and simple checkbox are

Prettier for formatting supported languages in Jenkins core

Hi all Looking for any feedback on the proposal of using prettier for formatting Jenkins core with the supported languages: - JavaScript - CSS - HTML - Markdown - Yaml See: https://github.com/jenkinsci/jenkins/pull/6863 Thanks Tim -- You received this message because you are

Re: 2.361.1 release lead

ted, even though I have never done it before. But I might need > extra help in getting started though. > > Best, > Kris > -- > *From:* jenkinsci-dev@googlegroups.com > on behalf of Tim Jacomb > *Sent:* 05 August 2022 17:25 > *To:* Jenkins Developer

2.361.1 release lead

Hello Is anyone interested in being the release lead for 2.361.1? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 24th August Release on 7th September The documentation is at: https://github.com/jenkins-infra/release

Re: Next LTS baseline

Hello 2.361 has been selected as the next baseline Thanks Tim On Tue, 2 Aug 2022 at 23:43, Olivier Lamy wrote: > As explained in the PR there are no real security issues but some > companies using scanners may have to live a long time with alarms etc... > And they don't have any "safe" (by

Re: Next LTS baseline

(as mentioned on the PR) My concern with backporting the Jetty changes is that this PR will never go to weekly as weekly is now on Jetty 10. But if we don't backport it, that would mean security scanners complaining about a new LTS line which isn't ideal... On Tue, 2 Aug 2022 at 22:06, Olivier

Re: maven-jellydoc-plugin and maven-stapler-plugin

+1 On Thu, 28 Jul 2022 at 23:50, Basil Crow wrote: > I would like to request a transfer of > https://github.com/kohsuke/maven-jellydoc-plugin from the kohsuke > GitHub organization to the jenkinsci GitHub organization and > permissions for both that repository and >

Re: comment-ops-bot available in jenkinsci and jenkins-infra

dev@googlegroups.com> wrote: > > > On Mon, Jul 25, 2022 at 12:20 PM Tim Jacomb wrote: > >> > Can we have review requests enabled by default while label changes are >> opt in? >> >> I'm not sure if that would scale across the number of infrequently >> tou

Re: comment-ops-bot available in jenkinsci and jenkins-infra

> Can we have review requests enabled by default while label changes are opt in? I'm not sure if that would scale across the number of infrequently touched repositories that we have. There's some good discussion happening in: https://github.com/timja/github-comment-ops/pull/56 On Mon, 25 Jul

Re: comment-ops-bot available in jenkinsci and jenkins-infra

we can enable globally. Thanks Tim On Mon, 25 Jul 2022 at 10:46, 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > On Mon, Jul 25, 2022 at 10:22 AM Tim Jacomb wrote: > >> It requires no organization permissions, which means anyone can req

comment-ops-bot available in jenkinsci and jenkins-infra

Hi all I've created a comment-ops bot that can be used to help manage issues and pull requests on GitHub. The features it has currently are: - /close - Issues only - /label - /remove-label - /reopen - Issues only - /reviewer(s) - /transfer It can be found at:

Re: Grant timja immediate permissions to commons-lang3-api plugin

b.com/jenkinsci/commons-lang3-api-plugin/>. The current >> maintainer has not responded to previous requests nor to the current >> request >> <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659> >> that asks to grant Tim Jacomb permission to m

Re: Let renovate handle dependency updates in jenkinsci/jenkins

+1 for renovate for at least JS deps, dependabot doesn’t support yarn v3 either so we would need to move at that point anyway On Mon, 18 Jul 2022 at 22:09, 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I'm a big fan of renovate, so I think its a good idea, but I

Release lead for 2.346.3

Hello Is anyone interested in being the release lead for 2.346.3? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 27th July Release on 10th August The documentation is at: https://github.com/jenkins-infra/release

Re: New member of jenkins.io triage team

+1 On Wed, 6 Jul 2022 at 06:50, 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > No objections by me. > > On Tue, Jul 5, 2022 at 2:01 PM Mark Waite > wrote: > > > > Kevin Martens has been running Jenkins Docs office hours (Europe) and > contributing to Jenkins

Re: New Plugin With Multiple Components Hosting Question

Hi All libraries used in a plugin must be published publicly, open source approved license, and to an artifact repository that anyone can pull from normally either maven central or Jenkins repository. Basically we can host it or you can push it to maven central if it makes sense outside of

Re: Security approval required on UI-related PRs in Jenkins core

I'd suggest another label for security review complete but needs fixes. There's currently 12 PRs showing as blocked by needing security review (1 or 2 of these may need a fix and a label could make that clearer)

Re: Is there interest for GitHub issues in core components?

Hi Basil I've updated the JEP, could you please take another look when you have time? Thanks Tim On Mon, 27 Jun 2022 at 20:14, Tim Jacomb wrote: > Yes there's been some work / plans around this for a while. (~2 years) > > A number of issues around it here: > https://github.com/j

Re: Is there interest for GitHub issues in core components?

easy or hard this > would be though ) > > Richard. > > On Tue, 28 Jun 2022, 3:53 am Basil Crow, wrote: > >> On Mon, Jun 27, 2022 at 1:15 AM Tim Jacomb wrote: >> > >> > Thanks for the feedback, I've created a JEP to capture and address it. >> >>

Re: Is there interest for GitHub issues in core components?

Hi all Thanks for the feedback, I've created a JEP to capture and address it. https://github.com/jenkinsci/jep/pull/390 Cheers Tim On Wed, 15 Jun 2022 at 16:55, Basil Crow wrote: > On Mon, May 23, 2022 at 1:25 PM Tim Jacomb wrote: > > Is there any interest in moving core c

Re: Proposal: Jenkins Core PR reviewers team

Taking the 4 +1s, I've added Alex to the Core PR reviewers team. On Mon, 20 Jun 2022 at 19:15, Basil Crow wrote: > On Mon, Jun 20, 2022 at 2:19 AM Alexander Brandes > wrote: > > where the latter would only be for review requests > > +1 from me that Alex becomes part of the "core PR reviewers"

Release lead 2.346.2

Hello Is anyone interested in being the release lead for 2.346.2? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 29th June Release on 13th July The documentation is at:

Re: Security approval required on UI-related PRs in Jenkins core

Hi Wadeck We can monitor this in the short term. My concern would be around responsiveness and turn around time. RPU hosting requests already can take a fair amount of time if there’s a few at a time It already takes a long time to get some of the UI pull requests in. As long as the security

Re: Proposal: Jenkins Core PR reviewers team

gt; Oleg Nenashev >> >> >> On Thu, Apr 15, 2021 at 10:35 PM Oleg Nenashev >> wrote: >> >>> +1. I will grant Basil permissions tomorrow if no negative feedback. And >>> again, thanks to Basil for all the contributions to Jenkins! >>> >>&

Re: Workflow approval for first time contributors

Hi Alex Workflow approval is a GitHub actions only thing. Unless it’s very spammy I don’t think it’s something to worry about, we often block these sort of people for 24 hours in case they continue. We get this sort of thing occasionally but it’s not normally that many Cheers Tim On Sat, 18

Re: javadoc issue due to Java11 on jenkins?

Throwing a couple of suggestions out there: - build on 17 - backport to Java8? - try a couple of those options out from the linked post but as James said they all have issues by the looks of it On Wed, 15 Jun 2022 at 17:33, 'jn...@cloudbees.com' via Jenkins Developers <

Re: javadoc issue due to Java11 on jenkins?

Interesting. I don't _think_ the one week early has any impact other than just raising the problem earlier. You're likely the first to hit this though. Can you tell if the javadoc was published for the plugin or if there's any issue with it? We can test it out on the test plugin

Re: Jenkinsci Cloudevents plugin

Or alternatively create a new plugin for CDEvents if the cloud events heritage doesn't make sense any more. Once you've got it working you could then go through the hosting process . Thanks Tim On Tue, 14 Jun 2022 at 13:18,

Re: BOM build errors due to conflict of baseline 2.319.3 and 2.319.1

Hi Ulli Since you've bumped past a baseline that is still supported in bom you need to pin the previous version of the dependency in the bom that your plugin doesn't support now. i.e. add echarts-api 5.3.2-1 to https://github.com/jenkinsci/bom/blob/master/bom-2.303.x/pom.xml Thanks Tim On

Re: Is there interest for GitHub issues in core components?

Hi James That thread is nearly 2 years old and the new GitHub projects and issues have come a long way in that time. To demonstrate some of what this could look like I did a POC migration based on the INFRA one: https://github.com/timja/jenkins-gh-issues-poc/issues I recreated 2 dashboards that

Re: Backporting for LTS 2.346.1 started

Fine to delay the extra week On Tue, 7 Jun 2022 at 12:01, Alexander Brandes wrote: > Hey Wadeck, > > thanks for the clarification from the views of the security team, that > sounds reasonable. I'd want to go ahead and merge the PR later today, > considering nobody expressed blocking reviews in

Re: [Jenkins Docker Images] Request for maintainer access

+1 I've granted access, welcome aboard On Wed, 25 May 2022 at 11:35, Mark Waite wrote: > > On Wed, May 25, 2022 at 4:08 AM Damien Duportal wrote: > >> Hello dear contributors, maintainers, readers. >> >> >> I'm writing this email to request a maintainer access (GitHub handle >> "dduportal") to

Is there interest for GitHub issues in core components?

Hello Is there any interest in moving core components to GitHub issues? It would involve things like: - Issue migration - LTS backporting flow updates - Documentation updates - Dashboards / reporting - maybe something like https://github.com/marketplace/actions/issue-dashboard I would be happy

Re: 2.346.1 release lead

@Mark Waite to be clear were you asking for an RC delay as well or just the final release date? On Fri, 13 May 2022 at 15:02, Tim Jacomb wrote: > Thanks! Go for it > > On Fri, 13 May 2022 at 14:52, Alexander Brandes > wrote: > >> Heyo all, >> >> I'd lik

Re: 2.346.1 release lead

. >> >> New dates: >> RC: 18th May >> Release day: 15th June >> >> On Tue, 10 May 2022 at 17:51, Mark Waite wrote: >> >>> >>> >>> On Tue, May 10, 2022 at 9:23 AM Tim Jacomb wrote: >>> >>>> Hello >>

Re: 2.346.1 release lead

Sure, I've moved the release date 2 weeks out. New dates: RC: 18th May Release day: 15th June On Tue, 10 May 2022 at 17:51, Mark Waite wrote: > > > On Tue, May 10, 2022 at 9:23 AM Tim Jacomb wrote: > >> Hello >> >> Is anyone interested in being the release lead fo

Re: Moving ATH tests closer to the code under test

I'm in favour of this although I can't dedicate time to it currently. > Whatever we have, if we end up having ATHs on core PRs to detect regressions early then we need to be prepared to maintain the ATH tests/framework or to not accept the changes. If PRs break the ATH and they are in the same

  1   2   3   4   5   6   >