Re: Unit tests failing during dependabot merge (junit upgrade)

Not sure why previous ones didn't fall, I suspect they do. I think it's referring to the Java compiler level https://github.com/jenkinsci/global-post-script-plugin/blob/master/pom.xml#L26 That should be 8 (1.8 is now 8). Also your parent pom is really old. I believe that's covered in one of mark

Unit tests failing during dependabot merge (junit upgrade)

Hi All, I am trying to merge my first PR , given by dependabot. Its a tiny change from junit from 4.11 to 4.13.1 on the pom.xml but the unit tests are failing , please see this link . It looks like more changes may be require

Re: Jenkins 2.332.1 LTS RC testing started

On Friday, February 25, 2022 at 6:19:30 AM UTC-7 Tim Jacomb wrote: > It'll be update center dynamic update sites most likely. > We've had similar issues before from what I remember with RCs > > Thanks. I've confirmed that support core plugin 2.81 loads into 2.332.1-rc correctly -- You receive

Re: Automated plugin release failing on 'check interesting categories' step

I had a chat with a GitHub staff member earlier: Hi Alex, > > Thank you for your patience with this issue. > > Our team verified today that a releases feature flag that was enabled > yesterday caused the experienced behavior with accessing draft releases > from API calls authenticated with GITHUB_

Re: Automated plugin release failing on 'check interesting categories' step

Thank you all for your comments and help. tl;dr: seems to be working now (last PR merge resulted in a new release) FTR: some notes about what I did: 1. Last night I manually ran the workflow to see if it made any difference that there was already a release draft. 1. It created an add

Re: Jenkins Security Scan now generally available

On Fri, Feb 25, 2022 at 2:43 PM Jean-Marc Meessen wrote: > > In the meantime, I will (try) to turn code scanning off so that I can get > the PRs through CI. > Removing https://github.com/jenkinsci/.github/blob/011201ac97f9e2757cca0415590952eaee704e5b/workflow-templates/jenkins-security-scan.yaml

Re: Jenkins Security Scan now generally available

Thanks for looking into this, Daniel, and let us know about the status. Looks trickier than expected. In the meantime, I will (try) to turn code scanning off so that I can get the PRs through CI. /- Jmm Le ven. 25 févr. 2022 à 11:50, 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegro

Re: Jenkins 2.332.1 LTS RC testing started

It'll be update center dynamic update sites most likely. We've had similar issues before from what I remember with RCs On Fri, 25 Feb 2022 at 12:22, Mark Waite wrote: > I'm perplexed by a behavior of the plugin manager or the update center > code (not sure which). > > The support core plugin 2.8

Re: Governance meeting Feb 23, 2022

On Wednesday, February 23, 2022 at 3:42:50 PM UTC-7 Jesse Glick wrote: Version number to 3.x when we require Java 11 or newer? > > > Rather not, because this implies that the upgrade is incompatible for most > users and a giant change in behavior, whereas it is just a newer version of > a runtim

Is there any plugin that provides necessary API that I can build a customized UI on top of it

A lot of Jenkins page, like /flowGraphTable is rendered by server side. I was wondering is there any rest API that allow me to build customized UI with? I try to search through the internet and only found a very simple one jenkinsci/pipeline-restful-api-plugin: Provide the API endpoint for Jenki

Re: Jenkins 2.332.1 LTS RC testing started

I'm perplexed by a behavior of the plugin manager or the update center code (not sure which). The support core plugin 2.81 has Jenkins 2.332 as its minimum Jenkins version. I've confirmed it installs as expected on Jenkins 2.332. When running the Jenkins 2.332.1 release candidate build (versio

Re: Jenkins Security Scan now generally available

On Wed, Feb 23, 2022 at 10:03 PM Daniel Beck wrote: > > Interesting. It probably happens because it's a PR from a fork and the > GITHUB_TOKEN used only has read permission for SecurityEvents. I'll look > into solutions tomorrow. > It looks like GitHub's action can do what I cannot because it use

Re: Automated plugin release failing on 'check interesting categories' step

Looks like others had the same idea like me and got it working with a PAT: https://github.com/release-drafter/release-drafter/issues/1081#issuecomment-1050099868 Or locally like it does work for you. timja...@gmail.com schrieb am Freitag, 25. Februar 2022 um 09:36:38 UTC+1: > Weirdly if I run

Re: Automated plugin release failing on 'check interesting categories' step

Weirdly if I run all the steps locally from the GitHub action I'm getting the right results =/ https://github.com/jenkinsci/jenkins-infra-test-plugin/runs/5330785488?check_suite_focus=true On Thu, 24 Feb 2022 at 23:37, Alex wrote: > I got it working by exchanging the GitHub token in the workflo