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

+1 This is break is quite severe Cheers, Raihaan On Tue, Jul 19, 2022, 1:20 PM Basil Crow wrote: > +UINT64_MAX > > On Mon, Jul 18, 2022 at 8:31 PM Mark Waite > wrote: > >> A release of the Apache mina API plugins (core and common) have exposed a >> cyclic dependency between the mina plugins,

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

+UINT64_MAX On Mon, Jul 18, 2022 at 8:31 PM Mark Waite wrote: > A release of the Apache mina API plugins (core and common) have exposed a > cyclic dependency between the mina plugins, configuration as code, and > other plugins. Details are into from >

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

your first link doesn't actually goto https://issues.jenkins.io/browse/JENKINS-69034 I'm very much +1 with the mess of that sshd plugin has caused all day. I've been redirecting threads and issues and stuff. Gavin On Mon, Jul 18, 2022 at 8:31 PM Mark Waite wrote: > > A release of the Apache

Grant timja immediate permissions to commons-lang3-api plugin

A release of the Apache mina API plugins (core and common) have exposed a cyclic dependency between the mina plugins, configuration as code, and other plugins. Details are into from https://issues.jenkins.io/browse/JENKINS-69034

[Stapler Framework Support for IntelliJ] StackOverflow fix testing

If you've been using the Stapler Framework Support IntelliJ plugin to edit Jelly files, you might have noticed the StackOverflowError in the JetBrains error reporter. The bug is tracked in https://github.com/jenkinsci/idea-stapler-plugin/issues/66 I tried to fix it. It is a somewhat

Re: Let renovate handle dependency updates in jenkinsci/jenkins

On Mon, Jul 18, 2022 at 2:48 PM Alexander Brandes wrote: > Although, I don't think we need two bots alongside for different package > ecosystems, when one bot can do both. We do if we want to optimize globally (organization-wide) rather than locally (repository-wide) for decreased cognitive

Re: Let renovate handle dependency updates in jenkinsci/jenkins

> Is there a compelling reason to prefer Renovate for Jenkins core Java dependencies? dependabot and renovate can manage Java dependencies equally fine, the drawback for frontend deps apply here too, you get one PR each, if that is a reasonable and frequent concern (it is not from what I've

Re: Let renovate handle dependency updates in jenkinsci/jenkins

+1 for Renovate for JavaScript dependencies, for the reasons you have pointed out: it does a better job of combining multiple updates together, increasing the success rate of the resulting proposed change. Is there a compelling reason to prefer Renovate for Jenkins core Java dependencies? I can

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

Re: Let renovate handle dependency updates in jenkinsci/jenkins

> don't touch core, so have no idea what the impact would be. The PoC contains a renovate file instead of the dependabot file, but the configuration has been carried over. The transition would be a drop in

Re: Let renovate handle dependency updates in jenkinsci/jenkins

I'm a big fan of renovate, so I think its a good idea, but I also don't touch core, so have no idea what the impact would be. On Mon, Jul 18, 2022 at 1:19 PM Alexander Brandes wrote: > > Small ammandment: The semantic commit messages on the PoC can be turned off, > but are picked up, because

Re: Releasing a new plugin fails due to 'Check interesting categories' failure

gh api /repos/jenkinsci/bmc-change-manager-imstm-plugin/releases 10++ jq -e -r '.[] | select(.draft == true and .name == "next") | .body' 11++ egrep '[⚠]|:(boom|tada|construction_worker):' Seems like it gets "releases" for the plugin, looks for a draft named "next" and then checks for any

Re: Let renovate handle dependency updates in jenkinsci/jenkins

Small ammandment: The semantic commit messages on the PoC can be turned off, but are picked up, because recent (my) commits use them. On Monday, 18 July 2022 at 22:15:32 UTC+2 Alexander Brandes wrote: > Hey everyone, > > dependabot does a good job at handling single artifacts, but it does a bad

Let renovate handle dependency updates in jenkinsci/jenkins

Hey everyone, dependabot does a good job at handling single artifacts, but it does a bad to no job handling modules of monorepos, see babel -cli, -core, -env, etc. for example. This typically leads me to moving several submodule dependency update PRs into a single PR, before reviewing,

Re: java.lang.NoClassDefFoundError: hudson/os/PosixAPI

Thanks, I updated the plugin parent POM to 4.32. ב-יום שני, 18 ביולי 2022 בשעה 18:25:17 UTC+3, m...@basilcrow.com כתב/ה: > As of jenkinsci/jenkins#6323 > (released in 2.338 > ),

Releasing a new plugin fails due to 'Check interesting categories' failure

https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/runs/7396269153?check_suite_focus=true Though I added *an appropriate category label* ( enhancement) to the PR before merging.https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/pull/2 Please advise how to proceed. Thanks,

Re: java.lang.NoClassDefFoundError: hudson/os/PosixAPI

As of jenkinsci/jenkins#6323 (released in 2.338 ), you need to be running jenkinsci/jenkins-test-harness#350 (released in

java.lang.NoClassDefFoundError: hudson/os/PosixAPI

Hi, I'm trying to release a new plugin, and I get the following error: https://ci.jenkins.io/job/Plugins/job/bmc-change-manager-imstm-plugin/view/change-requests/job/PR-1/4/console *18:10:16* [INFO] --- *18:10:16* [INFO] T E S T S *18:10:16*

New Gradle Plugin for JTE Plugin

Hey everyone, I'm going to be publishing a Gradle plugin that extends the Gradle JPI Plugin that allows users to package their libraries for the Jenkins Templating Engine as their own