Understanding Jenkins Core Vulnerabilities in plugin s

Hello everyone. I am trying to understand the impact of Jenkins core security vulnerabilities on plugin usage. Lets do this with an example: I am running Jenkins 2.319.3 and using a plugin that has 2.277.4 defined as in its pom.xml. Am I exposed to the vulnerabilities in 2.277.4? Does it

Re: Configuration as code round trip test fails with parent pom 4.35

On Monday, February 21, 2022 at 2:49:17 PM UTC-7 Jesse Glick wrote: > On Mon, Feb 21, 2022 at 2:53 PM Mark Waite wrote: > >> Based on that, I added a property to the pom file >>> >> >> >> >> false >> >> Test that was failing on my Windows computer is now passing. >> > > Good. Would you mind

Re: Configuration as code round trip test fails with parent pom 4.35

On Mon, Feb 21, 2022 at 2:53 PM Mark Waite wrote: > Based on that, I added a property to the pom file >> > > > > false > > Test that was failing on my Windows computer is now passing. > Good. Would you mind filing a PR to `plugin-pom` accordingly, so we can push out a release for the

Re: Configuration as code round trip test fails with parent pom 4.35

On Monday, February 21, 2022 at 11:14:36 AM UTC-7 Jesse Glick wrote: > Following the link trail, this is > https://issues.apache.org/jira/browse/MCOMPILER-485 so I think > https://github.com/jenkinsci/plugin-pom/pull/504 should either be > reverted until

Re: Configuration as code round trip test fails with parent pom 4.35

Following the link trail, this is https://issues.apache.org/jira/browse/MCOMPILER-485 so I think https://github.com/jenkinsci/plugin-pom/pull/504 should either be reverted until https://github.com/apache/maven-compiler-plugin/pull/95 is released, or the new feature explicitly disabled. -- You

Configuration as code round trip test fails with parent pom 4.35

The git plugin includes configuration as code round trip tests like this one . I like those tests because they confirm that configuration as code is well

Re: [jenkinsci-docs] Re: source code translation to Brazilian Portuguese

Alceu Rodrigues de Freitas Junior wrote: > I was originally using Vim to edit the property files, but I considered >> a shot with my old IntelliJ IDE > > Or NetBeans will automatically open `*.properties` in ISO-8859-1 encoding. (And use `\u` escapes as needed, though I suppose that should