@JenkinsRule plugin list customisation

In the context of how can I customise the list of plugins that the test runs with to detect a missing dependency in tests? There is https://wiki.jenkins.io/display/JENKINS/Unit+Test#UnitTest-@WithPlugin(NameOfPlugin) but there is no @WithoutPlugin and it seems that JenkinsRule somehow installs

Re: LTS baseline selection for the successor of 2.249

Since the selection took place and I can see 2.263.1 in https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in https://github.com/jenkinsci/bom ? On Monday, 9 November 2020 at 14:06:02 UTC+1 Mark Waite wrote: > Yes, 2.263 is the selected baseline for the next Jenkins LTS. > > On

Re: LTS baseline selection for the successor of 2.249

> > >> Since the selection took place and I can see 2.263.1 in >> https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in >> https://github.com/jenkinsci/bom ? >> >> > I think that you will eventually see 2.263.x in the bom rather than > 2.264.x. I'm sure that a pull request would be

Re: LTS baseline selection for the successor of 2.249

> > > Since the selection took place and I can see 2.263.1 in > https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in > https://github.com/jenkinsci/bom ? > I think that you will eventually see 2.263.x in the bom rather than 2.264.x. I'm sure that a pull r

Re: GitHub issues option in HOSTING

Resurrecting via PR: https://github.com/jenkinsci/.github/pull/42/files - let's discuss this there. Regarding Security issues - maybe GH new Security Advisories hub could be used for that? https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories https://

Re: GitHub issues option in HOSTING

>> Regarding Security issues - maybe GH new Security Advisories hub could be used for that? >> https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories >> https://github.blog/2020-05-26-giving-credit-for-security-advisories/ > Our usual workflow is docum

SonarCloud JenkinsCI organisation?

Hey, I'm trying to hook jira-plugin into SonarCloud, but when I'm trying to create jenkins or jenkinsci organisation, it shows me that the organisation already exists. Additionally, apparently I need organisation admin permissions on github.com/jenkinsci organisation to be able to link it autom

Re: GitHub issues option in HOSTING

I would like to vote +1 for GitHub Issues. I tried migration via the API for jira plugin and the only thing that we would lose is the original reporter (it would be noted in the comment but not the issue creator) - I think that this can be lived with. See https://github.com/warden/jira-plugin/i

GitHub Team Discussions in jenkinsci GH Org

I'm sure than other people co-maintaining the plugins over the world also have the problem that we have multiple ideas and discussions regarding project maintenance. Those obviously could be maintained in GitHub Issues, but since we have dedicated GitHub Teams per plugin maintainers, I'd like t

Automating plugin release process via GitHub Actions

I'm thinking about automating the plugin release process using GH Actions: - https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets - https://github.com/marketplace/actions/maven-release - https://help.github.com/en/actions/re

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Definitely +1 for core channel, definitely -1 for gitter and +1 for Slack or some other alternative like Rocket.Chat: I'd also love to have a channel for #infra. Something on that: https://medium.com/@gabriel_wilkes/why-tech-groups-can-get-away-with-using-slack-for-free-but-open-source-projects-a

Equalizing external dependency between plugins

While implementing dependabot in jira-plugin, we had a discussion about version incompatibility between different Jenkins plugins that might use the same external library. I'm wondering what's the current best practice in

Re: Jenkins-ci.org v.2 (for love or money!)

On Wednesday, 7 October 2015 13:51:15 UTC+2, James Nord wrote: > > One thing I just realize is that we have our documentation (javadocs) on a > separate website. > Most sites these days just have a "documentation " section which will also > have an api section within the same site (and themed in

Re: jira-plugin repository access

One quick follow up. Currently when there is a new JIRA ticket created in Jenkins JIRA, I am not getting any notifications, even if the correct component is selected. Is there a way we can send out notifications to the plugin maintainers when JIRA issues are created? One way to achieve that usi

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

Actually I think something's wrong. I have the same issue with jira-plugin that was released over 24h ago. v.2.2 is visible in both places: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/jira/ http://updates.jenkins-ci.org/download/plugins/jira/ but still not visible in Update Center

Re: Secrets in cloudbees builds of plugins

Resurrecting an old thread, Jesse, did anything change? On the current infra, is there any way to provide securely the token for coveralls? Travis has done it in the neat way: https://docs.travis-ci.com/user/environment-variables/#Defining-encrypted-variables-in-.travis.yml So this can be easily

jira-plugin repository access

Hi, There is a pile of PRs waiting in https://github.com/jenkinsci/jira-plugin/pulls and nobody seems to maintain it anymore. Please grant committer access (gh user: warden) Thanks! Regards, Radek -- You received this message because you are subscribed to the Google Groups "Jenkins Develope

Package naming convention for deprecated API migrations

I recently looked at Basil's PR migrating deprecated EE8 APIs to EE9: https://github.com/jenkinsci/jira-plugin/pull/635. Thank you for taking on this task—it’s much appreciated! While reviewing the PR, I noticed a naming convention that I had hoped we’d moved past, hence my stupid comment in t

Re: Caused by: java.lang.LinkageError: loader constraint violation

Interestingly I see the same problem in jira-plugin right now when doing tests before a new release: https://github.com/jenkinsci/jira-plugin/issues/643 I started from a clean env (no target/) and then after running mvn hpi:run I see only: $ find target -name 'jcl-over-slf4j*' target/jetty/webap

VSCode --add-opens run configuration setup

Hi guys, I'm wondering if anyone is using VSCode to develop the plugins and has a setup that can share? I'm having trouble setting up properly workspace options so that the --add-opens are passed to the Maven test runner.

[jira-plugin] move bug reporting to github issues

Hi, I'd like to remove the 'jira-plugin' component from Jira in favor of reporting all issues on Github Issues: https://issues.jenkins.io/issues/?jql=project+%3D+JENKINS+AND+component+%3D+jira-plugin https://github.com/jenkinsci/jira-plugin Is there a preferred approach to do this (apart from c

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

Raise a help desk issue asking for the component to be archived. That will stop new issues from being raised there but preserve existing ones. (You can also migrate them if you wish) Thanks Tim, is there any migration script available already somewhere that I can run myself on selected JQL or

[info] commons-collections4-api-plugin wrapper is now available

For anyone using (or wanting to use) Commons Collections 4.x, just a short announcement that the wrapper for Apache Commons Collection 4.x API is now available: https://github.com/jenkinsci/commons-collections4-api-plugin -- You received this message because you are subscribed to the Google Gro

Re: commons 4 api plugin

t probably not all plugins are > well maintained, or they are abandoned or up for adoption. > > -- > *From:* jenkin...@googlegroups.com on behalf > of Radek Antoniuk > *Sent:* Monday, May 26, 2025 1:18 PM > *To:* Jenkins Developers > *Subject:* Re: commons 4 api plugin

Re: commons 4 api plugin

collections4 so they could benefit as well > > > -- > *From:* jenkin...@googlegroups.com on behalf > of Radek Antoniuk > *Sent:* Friday, May 23, 2025 11:21 AM > *To:* Jenkins Developers > *Subject:* commons 4 api plugin > > Hi, > > Jenkins curren

commons 4 api plugin

Hi, Jenkins currently has https://github.com/jenkinsci/commons-lang3-api-plugin but there are some useful methods added in 4.x that I'd like to use . Is there any plan to creat

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: Reflection API - a weird test failure while bumping pom to next LTS

hanged 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 > a écrit : > &g

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

I'm updating the jira-plugin to the next LTS and one test suddenly started failing with: Found no instances of hudson.model.Job$BuildNumberAssigner registered java.lang.IllegalStateException at hudson.ExtensionList.lookupFirst(ExtensionList.java:482) at hudson.model.Job.assignBuildNumber(Job.ja

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...