Re: Plugin with Java 17 minimum dependencies

> Am 27.04.2024 um 09:24 schrieb Valentin Delaye (jonesbusy) > : > > Hi, > > I'm a bit confused on the minimum required Java version for plugins > > I maintain the https://github.com/jenkinsci/flyway-api-plugin which is an API > plugin for flyway dependencies. > > Since flyway 10 Java 17

Re: Building Jenkins core and plugins with Java 22

Thanks! Is it intentional that you are using "Jenkins Developers“ as mail from (and not your name Alex anymore)? It is somewhat strange to not see who actually sent the mail in the thread (without looking at all the headers)... > Am 01.04.2024 um 17:46 schrieb 'Alexander Brandes' via Jenkins

Re: Remove Suggestimate from issues.jenkins.io?

+1 > Am 11.03.2024 um 14:48 schrieb Mark Waite : > > The Jenkins Jira instance uses a Jira datacenter > license that is donated to the Jenkins project by Atlassian. > > The Suggestimate plugin >

Re: 2.440 as Feb 21, 2024 LTS baseline?

+1 > Am 13.01.2024 um 10:27 schrieb Tim Jacomb : > > +1 > > On Sat, 13 Jan 2024 at 08:51, 'Alexander Brandes' via Jenkins Developers > mailto:jenkinsci-dev@googlegroups.com>> > wrote: >> I’m +1 for 2.440 :) >> >> >>> On 13. Jan 2024, at 02:32, Mark Waite >>

Re: Banned dependencies error compiling SAML plugin PR

The correct setting is: 17 17 > Am 13.12.2023 um 12:55 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Wed, Dec 13, 2023 at 5:56 AM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: >> I think our tool chain will accept Java 17 dependencies if

Re: Banned dependencies error compiling SAML plugin PR

I think our tool chain will accept Java 17 dependencies if you explicitly declare it as supported by setting the java.version in you pom. But this makes no sense in your case, as you are just using a wrong dependency. (I have a plugin distributed that is based on Java 17 as the underlying

Re: does not have help

he following > > Used for databinding. TBD. > > I've also overridden the getHelpFile() method in my descriptor to see which > fieldName are passed and I do see all other fields besides the checkbox. > Is there a way to troubleshoot this? > > > > On Tue, Nov 14

Re: does not have help

A checkbox has a help as well. Maybe your Java field name does not match? E.g. in my plugin I have a help-file help-ignoreFailedBuilds.html that is mapped to the checkbox ignoreFailedBuilds with a getter getIgnoreFailedBuilds and setIgnoreFailedBuilds.  > Am 14.11.2023 um 09:20 schrieb tzach

Re: Tests are failing with Unable to inject class hudson.model.UserIdMapper after upgrading the build from java 8 to java 11

Does it fail locally? Did you try Java 17 (we are currently in the process of testing Java 21, so nobody is looking at Java 11 JDK anymore). > Am 06.11.2023 um 22:01 schrieb Anna Karyakina : > > Hi everyone, > > I got stuck with upgrading my plugin build from java 8 to java 11. It > compiles,

Re: October 30, 2023 Governance Board Agenda

afner > <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#Action-Items>Action Items > Alexander Brandes and Ullrich Hafner run the officer and board elections for > 2023 > 57 registered voters > Timeline > Nominations are closed (September 18 - October 27) > All roles have at

Re: auto release form branch or manual release of multimodule project

Our developer documentation is part of the website: https://github.com/jenkins-infra/jenkins.io/ > Am 27.10.2023 um 16:02 schrieb Jiri Vanek : > >> That is the trick which did the trick! >> Tyvm for providing such direct solution. I would not found those >> attributes... >> The build needed

Re: auto release form branch or manual release of multimodule project

I think the incremental tools do not work with multi-module projects. I always cd to my plugin folder and start mvn release from there. > Am 26.10.2023 um 12:10 schrieb Jiri Vanek : > > Hello! > > I have a plugin - https://github.com/jenkinsci/report-jtreg-plugin/ - where > main branch is

Re: Splitting a plugin into a legacy and supported part

> Am 13.10.2023 um 15:02 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Fri, Oct 13, 2023 at 2:38 AM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: >> there might be still some users that use the old and deprecated steps > > Like, Pipeline

Splitting a plugin into a legacy and supported part

Hi, I want to retire a lot of old and legacy code in the code-coverage-api plugin in order to simplify the development experience (e.g., there are duplicate classes and jelly views). It is difficult for new contributors to start development when they do not know which classes and views are

Re: 2.426 as Nov 15, 2023 LTS baseline?

+1 > Am 04.10.2023 um 17:27 schrieb Basil Crow : > > +1 > > We'll likely need to backport the fix for JENKINS-71937. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails

Re: Jelly dropdown list with filter?

You can use a > Am 08.09.2023 um 04:56 schrieb Michael Carter : > > > > Is there an option or variant that has a filter in it? Some of the > dropdowns I have can get quite large and before I go writing something wanted > to see if there was something out there available to plugin

Re: JSON license

> > > On Tuesday, July 25, 2023 at 4:24:04 PM UTC-6 Filipe Roque wrote: > I have not found any discussion on the mailing list about this. > > JSON License has not been considered an open source license by Apache [1], > Debian [2] and FSF [3] and is not OSI approved [4]. > > Douglas Crockford

Re: Did Tippy.js add Popper2 to Jenkins core?

Is there a reason that we are still bundling the JUnit plugin in our war? It has been removed from core quite some years ago... > Am 17.07.2023 um 20:33 schrieb Basil Crow : > > On Mon, Jun 12, 2023 at 10:39 AM Basil Crow > wrote: > > > > Then > >

Re: July 10, 2023 Governance Board Agenda

I got stuck in a train and will not make it today…Ulli-- Ulli - Typed with big thumbs on small phoneAm 10.07.2023 um 18:14 schrieb Mark Waite :The Jenkins governance board meets today at 6:00 PM UTC on Zoom.  The Zoom URL is

Re: Requesting Admin access to the jenkinsci organization

+1 from me > Am 05.06.2023 um 09:50 schrieb Alexander Brandes : > > Hey everyone, > > I would like to increase my involvement within the Jenkins project beyond a > maintainer scope, and would like to request admin access to the jenkinsci > GitHub organization. > > Besides my seat on the

Re: Permission to upload new Sonargraph Jenkins plugin release 5.0.2 to plugin repository

> The colleague who was working on our plugin before no longer maintains that > plugin. He left the company (hello2morrow). > > I submitted a PR (pull request) to obtain authorization. I got feedback, that > I would need the authorization of 3 developers, which all no longer work for > our

Re: Did Tippy.js add Popper2 to Jenkins core?

> I strongly feel the solution is to have more jelly or web components, that do > the standard ui behavior with encapsulation and contracts, and those that > want to be able to do custom logic, should include their own dependencies via > a bundler. Rather than reinventing the wheel we should

Re: Did Tippy.js add Popper2 to Jenkins core?

> Am 24.05.2023 um 18:57 schrieb Basil Crow : > > On Tue, May 23, 2023 at 10:18 AM 'Gavin Mogan' via Jenkins Developers > wrote: >> I tried accessing "Popper.createPopper" on ci.jenkins.io and it doesn't seem >> to be defined, so I don't think its exposed? > > Then why was

Re: Did Tippy.js add Popper2 to Jenkins core?

May 23, 2023 at 11:57 AM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: >> > >> >> I think that users also will benefit from views that do not load the same >> >> library multiple times (loading time of a page). Also it duplicates the >> >

Re: Did Tippy.js add Popper2 to Jenkins core?

> >> I think that users also will benefit from views that do not load the same >> library multiple times (loading time of a page). Also it duplicates the >> development effort if we create a plugin API for each JS library that we are >> using in core. > > These are indeed benefits, but I think

Re: CDF Project Representative nominations

I am also +1 that Mark would be a good representative person of the Jenkins project for the CDF TOC. > Am 22.05.2023 um 21:14 schrieb Alyssa Tong : > > Thank you Oleg for your role in the CDF TOC. > I am +1 for Mark as TOC candidate for Jenkins. > > BR, > alyssa > > On Mon, May 22, 2023 at

Re: Did Tippy.js add Popper2 to Jenkins core?

In JS and CSS and Jelly we have no concepts of encapsulation and APIs in the moment. Everything what is available in the browser is public by default. In JS this is even more complex to hide than in Java. I think that users also will benefit from views that do not load the same library

Re: Default selection in jelly with cookies

Ah, you want to use it on the server side. Sorry, then there is no equivalent available. > Am 22.05.2023 um 17:03 schrieb Michael Carter : > > Turns out I was thinking way to complicated: > >value="${h.getCookie(request,'project').getValue()}" /> >

Re: Default selection in jelly with cookies

Why do you want to use cookies? This is better implemented by storing the value in the browser's local storage. Example: https://github.com/jenkinsci/data-tables-api-plugin/blob/831d74b746337e6990c6aae5bff2591b2308103d/src/main/webapp/js/table.js#L148 > Am 22.05.2023 um 16:36 schrieb

Re: Revise "Bug" template fields on Jira

I think it makes sense to make the description mandatory. I’m not sure if the same should be done for the environment property (at least not globally). Wouldn’t it make more sense to make the affected core version selectable with something like a list box? > Am 17.04.2023 um 18:39 schrieb

Re: Jenkins JSON API

Please use the users mailing list or our community forum to post questions on how to use Jenkins. And please use an internet search before asking such questions. This is a developer mailing list. > Am 17.04.2023 um 07:45 schrieb selvavi...@gmail.com > : > > Thanks for the update. > Can you

Re: Jenkins JSON API

No, this is not possible. > Am 16.04.2023 um 16:16 schrieb selvavi...@gmail.com > : > > Hi, > I have below doubts on Jenkins JSON based API, > 1) Is it possible to apply filter on Jenkins Jobs API, like fetch success > build alone or fetch build take more than 2ms > 2) is it possible to

Re: script to configure repository labels

I am using the action https://github.com/jenkinsci/warnings-ng-plugin/blob/master/.github/workflows/sync-labels.yml With the configuration in https://github.com/jenkinsci/warnings-ng-plugin/blob/master/.github/labels.yml In all my repositories. It uses

Re: What shall be the main building block for such a plugin

Your use case sounds familiar, isn’t it already supported by the https://plugins.jenkins.io/promoted-builds/? Ulli > Am 16.03.2023 um 15:05 schrieb Tamás Mucs : > > Dear Community, > > I have been struggling hard with implementing a new plugin. While some of the > core concepts are more or

Re: Prototype.js replacing JSON.stringify

462/war/src/main/js/util/jenkins.js#L20-L54 > In theory that makes JSON.stringify work again, but would make the other > prototype js fail, so would have to be done temporarily. > > > On Thu, Mar 2, 2023 at 1:59 PM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: &

Re: Download local files from jenkins plugin page

> Am 06.03.2023 um 02:37 schrieb Young CJ : > > Here are more details. I have a mac mini for iOS app packaging, and I > installed jenkins on this computer so we can access jenkin by localhost:8080. > After finishing iOS packaging, it will produce some files in local > folder(include IPA

Re: Download local files from jenkins plugin page

I think you need to add some more details. What do you mean with local files? Do you want to have files uploaded from your local computer to the Jenkins controller? Or the other way round, provide a link to a file that is stored in a folder of the Jenkins controller? Where are these files

Re: Prototype.js replacing JSON.stringify

> > Hi! > I was looking at some javascript that was behaving differently on Jenkins > than it does on other apps. I boiled it down to the simplest reproducible > test case. > It turned out that serialization was behaving differently when calling > JSON.stringify. > > This is the sample code

Re: Press Contacts

+1 for me as well > Am 10.02.2023 um 13:25 schrieb Baptiste Mathus : > > +1 to remove/rework this and just point to the board's email. > > 1) I did receive many such sollications in the past, many legitimate. But in > 99% of the cases, I have mostly just forwarded requests to the board when

Re: Adoption request JQuery Detached

Indeed, for jquery 3.x we already have a plugin: https://plugins.jenkins.io/jquery3-api/ > Am 02.02.2023 um 22:06 schrieb Alexander Brandes : > > Hello, > > As far as I am aware, the jquery-detached plugin is not up for adoption. In > fact, it's deprecated according to its plugin page. >

Re: Artifact caching proxy activation

Sorry, false alarm :-) Now everything is back to normal... > Am 02.02.2023 um 16:36 schrieb Ullrich Hafner : > > Does this affect local builds as well? > > I now get failures while trying to fetch incremental releases: > > [ERROR] Failed to execute goal on proje

Re: Artifact caching proxy activation

Does this affect local builds as well? I now get failures while trying to fetch incremental releases: [ERROR] Failed to execute goal on project warnings-ng: Could not resolve dependencies for project io.jenkins.plugins:warnings-ng:hpi:10.0.0-SNAPSHOT: The following artifacts could not be

Re: Migration to Java11 and modules

> Am 03.01.2023 um 15:42 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Tue, Jan 3, 2023 at 8:08 AM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: >> Do we already have some guidelines on how to migrate a plugin to Java 11? > > Yes; no

Migration to Java11 and modules

I’m currently starting the Java 11 migration of my plugins and my local builds are failing due to several Java modules failures (package x.y.z is declared in the unnamed module, but a.b.c does not use it, error: module not found: x.y.z). Do we already have some guidelines on how to migrate a

Re: Solving “failing Parent Pom upgrade from 4.51 to 4.52 build” cheatsheet

> Am 14.12.2022 um 21:51 schrieb Basil Crow : > > On Wed, Dec 14, 2022 at 12:37 PM Ullrich Hafner > wrote: >> >> I would suggest to always update the major version of our plugin-pom if we >> make breaking changes. This is the second time that we deliver incompat

Re: Solving “failing Parent Pom upgrade from 4.51 to 4.52 build” cheatsheet

Thanks for the checklist! > Easily overlooked, the bump of plugin from 4.51 to 4.52 > has a > breaking change. The plugin build toolchain now requires at least Java 11 and > at least Jenkins 2.361. > I would suggest to always

Re: Zoom account access for Alex Brandes of governance board

+1 > Am 05.12.2022 um 19:23 schrieb 'Bruno Verachten' via Jenkins Developers > : > > +1 from me too. > > On Mon, Dec 5, 2022 at 7:03 PM 'Alyssa Tong' via Jenkins Developers > mailto:jenkinsci-dev@googlegroups.com>> > wrote: >> +1 from me >> >> On Mon, Dec 5, 2022 at 9:24 AM Mark Waite >

Re: Next baseline shift

+1 from me as well (after release of 2.375.1) > Am 28.11.2022 um 19:50 schrieb Basil Crow : > > Historically we have supported old baselines for a long time in the > build toolchain. The current build toolchain supports baselines as far > back as 2.249. This provides a high degree of flexibility

Re: Allow up to 2 elected board members from a single company

I am currently -1 for this change, but I do not yet have access to the full governance board discussion yet. Basically, the reasoning for this change is not clear for me. Looking back in the history of the governance board, we are 4 active members making all the decisions. As far as I

Re: Permission Request for the community Google Document "Jenkins Social Media Covers / Artwork"

Are you asking for approval or for someone adapting the permissions? I am +1 for your request but have no rights to change the permissions. > Am 23.11.2022 um 12:40 schrieb Alexander Brandes : > > +1 from me :) > > On Wednesday, 23 November 2022 at 12:08:51 UTC+1 damien@gmail.com wrote:

Re: Removing security vulnerability warning from CloudFormation plugin

Please follow our guidelines when reporting vulnerabilities, please see https://www.jenkins.io/security/ for details! > Am 19.11.2022 um 20:50 schrieb Damir Suleymanov : > > Hi, > I recently addressed vulnerability CVE-2019-1003061 in the CloudFormation > plugin

Re: BOM compiles plugins with target 11

> Am 10.11.2022 um 16:00 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Thu, Nov 10, 2022 at 2:03 AM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: >> This causes a failure of: >> >> [ERROR] Failed to execute goal >> org.apache

BOM compiles plugins with target 11

I’m struggling with the BOM builds of some plugins: https://github.com/jenkinsci/bom/pull/1513 Bump versions of JS libs by uhafner · Pull Request #1513 · jenkinsci/bom github.com It seems that the BOM compiles and builds plugins with target JDK 11 even though the plugin is not yet ready for

Re: Request for access to YouTube account

+1 > Am 26.10.2022 um 14:42 schrieb timja...@gmail.com : > > +1 > > On Wednesday, 26 October 2022 at 13:18:13 UTC+1 goun...@gmail.com wrote: > Hi group, > > I sometimes run the Platform SIG meeting (like > https://www.youtube.com/watch?v=R2322YxIciQ >

XStream Serialization: SortedSet vs. NavigableSet vs. TreeSet

In one of my serialized instances I am using a TreeSet to store some properties. When I declare the Java field as SortedSet (interface) or TreeSet (class), the Jenkins XStream correctly serializes the model. However, when I declare my field as NavigableSet (interface), then the serialization

Re: ATH broswer supprt

I don’t think that it makes much sense to use HTMLUnit with ATH. I’m fine with deleting the support. > Am 14.10.2022 um 16:43 schrieb 'jn...@cloudbees.com' via Jenkins Developers > : > > Hi all, > > Does anyone use the HTMLUnit browser in the jenkins acceptance-test-harness > suite? > > I

Re: Found the changeset View

Isn’t the component that contains the view shown in the issue? Which issue are you referring to? > Am 06.10.2022 um 17:19 schrieb Elton Alves : > > I'm starting to contribute with jenkins core and I got a noobie issue. > > I need to change the icon placed in changeset view but i can't found

Re: argLine when running integration tests with Java 17

> https://stackoverflow.com/questions/24115142/intellij-error-when-running-unit-test-could-not-find-or-load-main-class-suref > > <https://stackoverflow.com/questions/24115142/intellij-error-when-running-unit-test-could-not-find-or-load-main-class-suref> > > Regards, > > Al

argLine when running integration tests with Java 17

I recently switched my development to Java 17 and most things work flawlessly now. One thing that I can’t get to work is debugging of integration tests in IntelliJ. It seems that the argLine command (that opens Java modules) is not sent to the debugging process. However, the same tests run

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

+1 > Am 29.07.2022 um 00:49 schrieb Basil Crow : > > 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: GSoC Project - Plugin Health Score Survey for Maintainers

Maybe it would help to post in https://community.jenkins.io as well? It would be also helpful to ask the users what they think, so the users mailing list may increase the number of return answers? > Am 12.07.2022 um 17:24 schrieb Adrien Lecharpentier > : > > Hello everyone, > > just a

Re: spotbugsXml.xml

Do you mean SUPPORTED_FORMATS? - https://github.com/jenkinsci/warnings-ng-plugin/blob/master/SUPPORTED-FORMATS.md - https://github.com/jenkinsci/analysis-model/blob/master/SUPPORTED-FORMATS.md

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

I see, thanks! Shouldn’t the BOM also follow our guidelines and support only releases 2.303.3 and 2.319.3 and newer? There is a 2.289.x folder in there as well. > Am 13.06.2022 um 17:47 schrieb Tim Jacomb : > > Hi Ulli > > Since you've bumped past a baseline that is still supported in bom

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

> Am 13.06.2022 um 11:11 schrieb 'jn...@cloudbees.com' via Jenkins Developers > : > > Hi Ulli, > > Can you clarify what these guidelines are and where they are (I did not see > anything in a scan of the ML, nor on jenkins.io)? > > With my Jenkins user hat on I would be somewhat annoyed if I

BOM build errors due to conflict of baseline 2.319.3 and 2.319.1

I recently updated my plugins to follow the new guidelines to use 2.319.3 rather than 2.319.1 as a plugin baseline. But now all my plugin upgrade PRs fail in the BOM project (https://github.com/jenkinsci/bom/pulls ). What do I need to do to get those PR

Re: warnings-ng-plugin-devenv/analysis-model/bin/go.sh missing a step?

> Am 08.06.2022 um 19:56 schrieb Simon Matthews : > > More on what is stopping deploy.sh > > I see this error message, which I had erroneously ignored previously: > cp: cannot stat 'code-coverage-api-plugin/target/*hpi': No such file or > directory > Ups, the path has been changed. I fixed

Re: warnings-ng-plugin-devenv/analysis-model/bin/go.sh missing a step?

Workaround 1: use a pipeline and not a Freestyle Job Workaround 2: register your parser in the warnings plugin, see: - documentation: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Custom-Plugin.md#register-the-tool

Re: warnings-ng-plugin-devenv/analysis-model/bin/go.sh missing a step?

In your Jenkinsfile of your job where you want to use the parser. Or are you using a Freestyle project? I think in Freestyle projects I forgot to add a dynamic selection of the parser ID in the UI up to now. I should file an issue for this bug. In this case you need to register your parser in

Re: warnings-ng-plugin-devenv/analysis-model/bin/go.sh missing a step?

The parser is not listed in the UI, because the parser is not registered in the warnings plugin yet. But you can invoke the parser already using: recordIssues tool: analysisParser(pattern: 'your-report-file.xml', analysisModelId: 'your-id') Does that work? > Am 03.06.2022 um 20:35 schrieb

Re: warnings-ng-plugin-devenv/analysis-model/bin/go.sh missing a step?

> Am 03.06.2022 um 00:34 schrieb Simon Matthews : > > I have now got this to build and run in Jenkins (I installed the latest > version of Docker and the docker-compose-plugin so that I could use the > scripts without modification), Good to see. I need to spend some time to investigate why

Re: warnings-ng-plugin-devenv won't build

I think that I replaced all HTTP references quite some time ago. If you find one, please let me know. > Am 02.06.2022 um 09:16 schrieb 'Daniel Beck' via Jenkins Developers > : > > That URL hasn't worked in a long time. Cloning the devenv repo and running > the clone script, including build,

Re: Trying to use the warnings-ng-plugin-devenv

Yes, the script is from the time before the integration of docker-compose into docker. I tried to replace docker-compose with docker compose in the script but it seems that the implementation is different and does not update the Jenkins version to the latest one so I finally did not change

Re: Building an hpi file?

Yes, using the development environment is the recommended way, since the setup simplifies the build steps. The analysis-model is split into two modules: - analysis-model: a Java library (jar file) that is used in Jenkins or in GitHub Actions - analysis-model-ap-plugin: a Jenkins Plugin Wrapper

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

As mentioned several times before I think that using or allowing 2 different issue tracker systems for *any* Jenkins component (core and plugins) is a mess for users and developers. > Am 23.05.2022 um 20:54 schrieb Basil Crow : > > On Thu, Apr 28, 2022 at 1:22 AM 'Daniel Beck' via Jenkins

Re: Moving ATH tests closer to the code under test

> Am 26.04.2022 um 18:28 schrieb Basil Crow : > > On Tue, Apr 26, 2022 at 7:45 AM Ullrich Hafner > wrote: > >> Those tests will run in a special docker container with a headless browser >> (chrome or firefox). > > Ideally, I think we would want to

Re: Moving ATH tests closer to the code under test

> Am 27.04.2022 um 12:37 schrieb 'Antonio Muñiz' via Jenkins Developers > : > > I was working/planning with Oliver for some time on this. One of the > identified downsides of this approach is that the Jenkins UI does often > evolve in a backward incompatible way (ie. table to divs change,

Re: Moving ATH tests closer to the code under test

>> Although ATH uses RESTish endpoints for a few purposes, for the most part >> the test setup (not just the actual assertions) uses the browser. In all >> cases the whole test run is “black-box”. This has its appeal (stronger >> coverage) but GUI setup makes tests much slower and either REST

Re: Moving ATH tests closer to the code under test

Thanks Basil for bringing this topic to attention! I am all in for this new approach! I think when we spend time to write UI tests (which are expensive to write and maintain, and slow to run, see test pyramid of Mike Cohen) then we should consider to run them as real system tests using a real

Re: Need Jenkins Jira access to create a Support ticket

https://accounts.jenkins.io/login > Am 08.04.2022 um 08:49 schrieb Vinothkumaar Venkataraman > : > > Hi Team, > > We would need to create a support Jenkins JIRA ticket for about a Security > Vulnerability. Could you please provide the access to create an account for > my mail id -

Re: Intellij Stapler Framework Support compatibility

Currently 2022.1 is in beta so I think it would be save to use 2021.1 as minimum baseline. Stapler plugin users are developers which typically use latest versions rather than outdated versions. So please go ahead and change the baseline. > Am 30.03.2022 um 06:41 schrieb Denys Digtiar : > > I

Re: Using data-tables-api-plugin

om/jenkinsci/bmc-cfa-plugin/tree/stat> > >> >> >> >> >> ב-יום שלישי, 15 במרץ 2022 בשעה 22:47:28 UTC+2, timja...@gmail.com >> <http://gmail.com/> כתב/ה: >> If you can share your code / a branch with what you have you might get >> b

Re: Using data-tables-api-plugin

imja...@gmail.com כתב/ה: > If you can share your code / a branch with what you have you might get better > help if that's possible > > On Tue, 15 Mar 2022 at 19:44, Ullrich Hafner > wrote: > > >> Am 11.03.2022 um 07:31 schrieb Marit M > >: >> >>

Re: Using data-tables-api-plugin

> Am 11.03.2022 um 07:31 schrieb Marit M : > > Hi, > > I'm trying to implement tables with dynamic model based content in my plugin. > Only the table columns are displayed, while the the content is missing, and > instead the following message is displayed: "Loading - please wait ...". > > I

Re: webhook plugin development for multibranchPipelineJob

You should upgrade the plugin to a recent Jenkins Version like 2.303.1, then the BOM will provide a solution for all of these problems (https://github.com/jenkinsci/bom). > Am 08.02.2022 um 20:17 schrieb John Patrick : > > Hi, > > I'm looking adding support for `multibranchPipelineJob` to a

Re: Plugin BOM upgrade, 2.289.1 vs. 2.289.3

The docs are here: https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ While I understand the reasoning for using the latest patch version of an LTS I think this increases the

Re: Plugin BOM upgrade, 2.289.1 vs. 2.289.3

> Am 31.01.2022 um 15:46 schrieb Mark Waite : > > Dependabot proposed a git plugin pull request > to update the > 2.289.x bom from 1117.v62a_f6a_01de98 to 1135.va_4eeca_ea_21c1. > > The pull request CI build >

Re: Help needed with a stuck PR merge

Is your PR up to date with master branch (merge or rebase?)? > Am 20.01.2022 um 05:36 schrieb Konstantin Voin : > > Hello, > > Can someone help with the last check on this PR: > https://github.com/jenkinsci/fortify-on-demand-uploader-plugin/pull/108 >

Re: Plugin for adoption: OWASP Dependency Check

And please note: Since a couple of releases an OWASP dependency check parser is part of the warnings plugin as well (https://github.com/jenkinsci/warnings-ng-plugin/blob/master/SUPPORTED-FORMATS.md ). So if

Re: INFRA project issues migration from Jira to Github

> > My regret is the fact I've learned about the "notifyUsers=false" Jira REST > API parameter too late. > Well, I think it is very important to notify reporters that their issues have been moved to a new system. -- You received this message because you are subscribed to the Google Groups

Re: INFRA project issues migration from Jira to Github

; > There’s hundreds of old issues to review and likely close which should end up > with a much more manageable backlog > > On Wed, 12 Jan 2022 at 23:42, Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: > It seems that the reporters (and assignees) of the issues ha

Re: INFRA project issues migration from Jira to Github

It seems that the reporters (and assignees) of the issues have not been mapped. Is this planned? > Am 12.01.2022 um 14:50 schrieb 'Herve Le Meur' via Jenkins Developers > : > > Hello! > > As some of you might have already noticed, all issues related to the > Infrastructure project have been

Incremental releases show not up as GitHub action result anymore

Since a couple of days, incremental releases do not show up as GitHub action result anymore. Is this a know problem in our infrastructure? E.g. Pull Request: https://github.com/jenkinsci/prism-api-plugin/pull/2 Available incrementals from this PR:

Re: Setting up automated plugin release

Maybe you can inline the existing Abstract form the JEP before the section ‚Prerequisites‘? And add an example that shows the old and new versions in the abstract as well? > Am 28.12.2021 um 14:58 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Tue, Dec 28, 2021 at 5:50 AM Marit M

Re: Expose data to API from Jenkins Shared library

Does your action implement a method: public Api getApi(); ? > Am 15.12.2021 um 02:12 schrieb Oscar Arevalo Loyola : > > Hi, > > I'm trying to expose internal Run data to the REST API. > Currently I'm using a Shared Library to create an object containing data > about downstream builds in

Re: StaplerProxy getTarget

velopers > : > > > > On Wed, Dec 15, 2021 at 1:13 AM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: > (Code https://github.com/jenkinsci/warnings-ng-plugin/pull/1145/ > <https://github.com/jenkinsci/warnings-ng-plugin/pull/1145/>) > > Is this the correc

StaplerProxy getTarget

I am implementing StaplerProxy for some of my detail views. When I am returning a new view object in the getTarget method that is part of my plugin then everything shows up correctly. When I return an object from another plugin I get a 404 error. Is this some restriction (class loader?) that I

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

sign flaw that I did overlook. I think a simple solution is to create new objects as you already mentioned. Thanks! > A more robust change would be to make AnnotatedReport and all of its fields > (and their fields recursively) immutable like Jesse mentioned. > > On Wed, Nov 17, 2021

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

> Am 17.11.2021 um 14:42 schrieb 'Jesse Glick' via Jenkins Developers > : > > On Wed, Nov 17, 2021 at 5:57 AM Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote: > […] is stored in a CopyOnWriteArrayList. If your background thread serializes > my instance du

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

block of variables, or how is this handled? > Am 16.11.2021 um 18:09 schrieb Ullrich Hafner : > > Thanks for this in depth description of the problem! I see how much work is > required in order to rewrite that part of the code. > >> Am 16.11.2021 um 17:42 schrieb 'Devin

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

Thanks for this in depth description of the problem! I see how much work is required in order to rewrite that part of the code. > Am 16.11.2021 um 17:42 schrieb 'Devin Nusbaum' via Jenkins Developers > : > > The CPS VM thread is responsible for saving the Pipeline's execution state, > so if

  1   2   3   4   5   6   >