Re: Updating detached plugins

On Tue, Apr 9, 2024 at 9:34 PM Basil Crow wrote: > Daniel, I am not aware of any such examples. > Thanks for that confirmation. At this point I'm not entirely convinced JENKINS-69361 is real, and unless you know more than is present in Jira, we don't understand it well enough to act on it.

Re: Updating detached plugins

On Tue, Apr 9, 2024 at 8:28 PM Basil Crow wrote: > Third, we have occasionally seen a need to mitigate the impact of > JENKINS-69361. > Since 2022 I have been regularly updating detached plugins, justified > as an exception to the usual policy in order to mitigate the impact of >

Re: Building Jenkins core and plugins with Java 22

On Tue, Apr 2, 2024 at 9:27 PM Ullrich Hafner wrote: > 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)... > This is how

Re: New plugin

On Fri, Mar 22, 2024 at 11:12 AM DuMaM wrote: > My work environment requires from me to give users privileges to create > new jobs, but I need to lock creation of non pipeline jobs. > I could take a solution proposed a long time ago by Daniel Beck, but I > fought that maybe it's

Re: Wrong administrative monitor for SECURITY-3379?

On Thu, Mar 21, 2024 at 9:40 AM 'Björn Pedersen' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > there is an administrative monitor for SECURITY-3379 popping up in 2.450 > weekly, saying that there is no solution yet, while > https://www.jenkins.io/security/advisory/2024-03-20/

Re: Retire some of my old plugins

On Sun, Mar 17, 2024 at 9:01 AM 'Alexander Brandes' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > To mark the plugins as EOL, I recommend adding the “deprecated” topic to > the GitHub repositories, adding a note to the README that the plugin is > EOL, closing open PRs and

Re: GitHub Issues

On Wed, Mar 13, 2024 at 9:08 AM 'Michael Kriese' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Found it. > > - https://maven.apache.org/pom.html#issue-management > - >

Re: Error: Could not find or load main class com.mathworks.polyspace.jenkins.PolyspaceHelpers

On Fri, Mar 1, 2024 at 11:43 PM Stéphane BOBIN wrote: > - What is the recommended and secure way to have scripts on agents to call > utilities from the plugin? > It's not a common enough use case to have a general recommendation. Some ideas: publish the utilities separately rather than as part

Re: CVE-2023-50164 Struts question

On Fri, Dec 22, 2023 at 4:26 PM 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > Now, if you are not sure, you can still contact the security team, but I > will ask you to provide more details, like which plugin, which CVE, and > your doubts. > After discussing with Wadeck, I'd like to

Re: Adopt plugin openid-plugin

On Sun, Feb 18, 2024 at 5:56 PM Adrien Lecharpentier < adrien.lecharpent...@gmail.com> wrote: > Please note that the plugin has multiple public security issues. I'm sure > the security team will require you to resolve them before any release can > be deployed. > While we definitely prefer that

Exclusive JEP-229 CD mode announcement

Hi everyone, For JEP-229[1] enabled plugins, RPU[2] manages the permissions required to have CD releases and periodically refreshes the Artifactory token for the CD action in the GitHub repository. Until recently, releases through JEP-229 CD were always enabled _in addition_ to manual uploads

Re: GetStatic Jelly Tag

On Thu, Dec 7, 2023 at 5:44 PM Bryan Stopp wrote: > It does not find my packages/classes in my plugin for referencing static > values. > https://issues.jenkins.io/browse/JENKINS-26579 ? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: does not have help

On Tue, Nov 14, 2023 at 10:27 AM tzach solomon wrote: > From what I can see, checkbox.jelly has the 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 >

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

On Thu, Oct 26, 2023 at 2:51 PM Jiri Vanek wrote: > [ERROR] jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is > not a valid repository name > Looks like the attributes in

Re: Splitting a plugin into a legacy and supported part

On Fri, Oct 13, 2023 at 8:38 AM Ullrich Hafner wrote: > Or is there even anotheroption that I do not see? > Depending on the scope of the problem, deprecation and finally removal of the obsolete stuff you want to remove. Use usage-in-plugins to identify callers and consider providing

Re: 2.426 as Nov 15, 2023 LTS baseline?

On Fri, Oct 6, 2023 at 9:56 AM Jan Meiswinkel wrote: > I would appreciate if PR-7056 > would make it into the > next LTS, if that is possible without any downsides. > Too much of an API addition IMO. If a decision is made to backport, should be

Re: September 18, 2023 Governance Board Agenda

On Tue, Sep 19, 2023 at 4:32 PM 'Jenkins Developers' via Jenkins Developers wrote: > > In order to limit Java support to two LTS releases, the Jenkins project > will adopt a “2+2+2” model where a new Java LTS release is supported for > two years, then becomes the minimum required Java version

Re: Request for Status Update on Parasoft Findings Plugin 10.6.3 Release

On Fri, Sep 1, 2023 at 11:05 PM Mark Waite wrote: > > > On Friday, September 1, 2023 at 2:38:07 PM UTC-6 Yuqian wrote: > > Hi, > > This is Yuqian from Parasoft. > > I attempted to release the Parasoft Findings Plugin 10.6.3 using "mvn > release:prepare" and "mvn release:perform." Both commands

Re: commit access lost to blueocean-plugin

FTR I resolved both issues. -- 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...@googlegroups.com. To view this discussion on the web

Re: Adopting the remote-jobs-view-plugin plugin

On Sun, Jul 30, 2023 at 11:16 AM Swamy M S wrote: > Can we enable this plugin wiki and release this plugin in jenkins again? > Distribution will be restored once there is a fix for the security vulnerability that caused distribution to be suspended, and a release has been made. The last release

Re: Revise "Bug" template fields on Jira

On Mon, Apr 17, 2023 at 6:39 PM Mark Waite wrote: > > I'd like the Jira experts like Basil Crow and Daniel Beck to voice their > opinions. > Should be doable. It looks like we'd need to copy the field configuration, mark the fields required in the copy, define a new field configur

Re: Jenkins Security Scan now generally available

On Mon, Mar 20, 2023 at 3:13 AM Basil Crow wrote: > Does the Jenkins Security Scan need to be adapted to use the artifact > caching proxy? > The workflow would need to be adapted to use the caching proxy, but given uncertainty around unauthenticated future use of Artifactory I am hesitant to

Re: Trouble with dynamically updating Jelly textbox

On Fri, Mar 31, 2023 at 5:43 AM Dane Wrye wrote: > Hey All, > > I am a new to Jenkins/Jelly and trying to pick it up as I add > functionality to a new codebase. With that said, I am looking at > dynamically updating a textbox on my form when the selected option of a > select element changes. I

Re: Can someone delete https://plugins.jenkins.io/packageversion/

On Tue, Feb 21, 2023 at 12:08 AM Alexander Brandes wrote: > impactful enough to justify a suspension of the plugin In particular, exploitation requires the parameter to be shown on a view that doesn't mitigate the vulnerability, of which there are few. There's a good chance nobody is actually

Re: How does /monitoring skip starting splash page?

PluginImpl#start adds HudsonMonitoringFilter to the PluginServletFilter list, which should be happening before PLUGINS_STARTED, so it doesn't wait for items to load etc. On Wed, Feb 8, 2023 at 2:47 PM Michael Carter wrote: > "jenkins is starting up" is the screen I'm talking about. >

Re: Jenkins Security Scan now generally available

findings in code: using comments or using a @SuppressWarnings annotation. The detailed finding descriptions on the GitHub UI explain how to use these to suppress specific findings (re-run the scan if needed to get an updated description). Regards Daniel On Tue, Feb 22, 2022 at 6:29 PM Daniel Beck

Re: Removing inactive Core maintainers to reduce risk

On Mon, Jan 30, 2023 at 7:26 PM Basil Crow wrote: > A compromised account with unnecessary commit access could very well > have that level of impact if it is used to introduce malicious content > into a release. > Exactly, which is why this was done. As a reminder, you originally responded to

Re: Removing inactive Core maintainers to reduce risk

On Mon, Jan 30, 2023 at 12:27 PM Daniel Beck wrote: > I also see this less as a step to remove maintainers who are not doing any > maintenance (which goes beyond what the officers' mission is) and more > limiting risk (which is in scope). IMO if one of the affected folks were to

Re: Removing inactive Core maintainers to reduce risk

On Sun, Jan 29, 2023 at 8:53 PM Basil Crow wrote: > By the same logic, we could dispense with core PR reviews because any > commit can be reverted without problems. Such an approach would appear > to go against the consensus-driven nature of the project. > If there were votes taken for release

Re: About the MVN Jenkins upgrade issue

On Wed, Jan 11, 2023 at 2:05 PM hongkeung ling wrote: > -B … -DarchetypeVersion=1.7 > This specifically chooses a really old version of the archetype. Don't do that. But note that even the latest archetypes depend on a slightly older version of Jenkins than is current. I recommend you mostly

Re:

On Mon, Jan 9, 2023 at 2:10 PM Kul Bhushan Srivastava wrote: > Until now I was able to compile the maven dependencies against java8. > > All of sudden the dependencies which are getting downloaded are compatible > with java11 and not with java8. > You're probably using Jenkins 2.357 or newer as

Re: Towards new kubernetes-client 6.x

On Thu, Jan 5, 2023 at 5:18 PM Vincent Latombe wrote: > A new major version of this library (6.x) has been available for a while > and has breaking changes (See > https://github.com/fabric8io/kubernetes-client/blob/v6.3.1/doc/MIGRATION-v6.md > for details) requiring coordinated changes across

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Fri, Dec 16, 2022 at 7:43 PM sghil...@gmail.com wrote: > > Last I checked, generated poms were also invalid, which is a problem for > any consumers of these artifacts that do more than just download the hpi. > > I believe this was fixed in 2019 as v0.31.0 >

Re: Renaming a plugin

On Fri, Dec 30, 2022 at 7:51 AM Marit M wrote: > I changed the name, and I would still like to change the *artifactId *as > well. > Please advise the steps that should be taken. > You shouldn't, see https://github.com/jenkins-infra/repository-permissions-updater#changing-plugin-id If you

Re: Maintenance with downtime of JFrog Artifactory (repo.jenkins-ci.org) 18 of December of 2022

On Fri, Dec 9, 2022 at 4:55 PM Damien Duportal wrote: > - No artifacts can be downloaded (failing builds on your machines as well > as builds on ci.jenkins.io) > Could you put ci.j.io into quiet down mode for the time to prevent builds failing for infra reasons? -- You received this message

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes wrote: > There's no support for automated releases (CD, JEP-229), missing metadata > for the plugin page and a few other limitations, which don't make it a > great experience using it. > … > I would be ready to lift this restriction again if the

Re: JDK19 is now available on ci.jenkins.io

On Thu, Dec 8, 2022 at 11:02 AM 'Stephane Merle' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hello dear developers, > > I’m happy to announce that in order to allow contributors to prepare the > future of Jenkins by working in advance with new JDK, we’ve added JDK19 on >

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes wrote: > There's no support for automated releases (CD, JEP-229), missing metadata > for the plugin page and a few other limitations, which don't make it a > great experience using it. > Last I checked, generated poms were also invalid, which is

Re: End of year holidays and Jenkins 2.375.2 release schedule

On Tue, Nov 22, 2022 at 9:53 PM Tim Jacomb wrote: > Is there an issue with what’s already in the calendar? > A one month RC period makes it more likely to have requests for post-RC changes crop up. I'd prefer to shorten it for that reason (like Mark suggested). -- You received this message

Re: Translating some tutorials?

On Wed, Oct 26, 2022 at 11:59 AM 'Alina Strohaya' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I'm kind of surprised that you said this about maintenance, because if > it's in OSS, and gets outdated, or people notice something they want to > improve, they can file a PR and

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

On Thu, Oct 13, 2022 at 9:11 AM Tim Jacomb wrote: > I would like to propose Alexander Brandes (@NotMyFault > ) to join the Jenkins Core team. > +1 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Recommendations for updating minimum Jenkins version on plugin

On Mon, Oct 10, 2022 at 10:01 AM Jamie Tanna wrote: > > Would it be best to create a new conversation to chat about this and > request support / is there a better place I can see if anyone can give a > hand with it? > Please note that the vast majority of plugins are built with Maven, so

Re: Artifactory Problems?

On Wed, Sep 28, 2022 at 3:21 PM DuMaM wrote: > > Could you share sample of correct settings.xml file so i can compare it? > The linked documentation has two complete examples of the settings.xml file you need (just needs replacing username/password entries as appropriate). -- You received

Re: Artifactory Problems?

On Wed, Sep 28, 2022 at 3:19 PM DuMaM wrote: > https://repo.jenkins-ci.org/ui/login/ > Following with this tutorial > https://www.jenkins.io/doc/developer/publishing/releasing-manually/ Re-read step 7. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Artifactory Problems?

On Wed, Sep 28, 2022 at 1:16 PM DuMaM wrote: > > central (https://repo.jenkins-ci.org/artifactory/remote-snapshot-repos, > releases=true, snapshots=false), > snapshots (https://repo.jenkins-ci.org/artifactory/remote-snapshot-repos, > releases=true, snapshots=true) > This looks like

Re: Random String Parameter Plugin has several vulnerabilities

On Wed, Sep 7, 2022 at 2:11 PM Khachatur Ashotyan < khachatur.ashot...@gmail.com> wrote: > I'm not sure, that I want to adopt this plugin, …. I'm ready to maintain > this plugin. > Could you clarify what you mean, because these don't seem to go together? We call it "adoption" when someone starts

Re: Error injecting: public org.apache.maven.repository.internal.DefaultVersionResolver org.apache.maven.repository.internal.DefaultVersionResolver.setRepositoryEventDispatcher(org.eclipse.aether.impl

On Thu, Sep 1, 2022 at 1:37 PM Mehul Parmar wrote: > ### Jenkins and plugins versions report > > > Environment > > > ```text > Paste the output here > ``` > > > The instructions Basil provided in https://github.com/jenkinsci/jenkins-test-harness/issues/480#issuecomment-1226073300

Re: Apache Jelly grammar and parser

On Fri, Aug 26, 2022 at 5:04 PM Alceu Rodrigues de Freitas Junior < alceu.freitas...@gmail.com> wrote: > > Supposedly the XML parser is getting the tooltip text as expected, but > the rest I would need to do an additional effort to parse properly. >

Re: Apache Jelly grammar and parser

On Thu, Aug 25, 2022 at 9:28 PM Tim Van Holder wrote: > I would expect that in most cases, the jelly files used by Jenkins and its > plugins would already be using localized strings (like "${%Hello World}" > which will use the "Hello World" resource from the bundle matching the > jelly file's

Re: Apache Jelly grammar and parser

On Wed, Aug 24, 2022 at 6:29 PM Alceu Rodrigues de Freitas Junior < alceu.freitas...@gmail.com> wrote: > I've being working in a CLI to parse the properties and Jelly files from > the Jenkins project, in order to help the translation process from English > to other languages. > > The project is

Re: ASM in core

On Thu, Aug 18, 2022 at 6:40 AM Basil Crow wrote: > Recent weeklies no longer consume ASM. So shall we detach it to a > library plugin? > I might miss some context, as this thread has been going for a while, but is a clean removal like JNR doable here as well? A quick GH search indicates that

Re: Merging multiple build steps into one (with nested Describables)

On Sun, Aug 14, 2022 at 6:14 PM Tim Van Holder wrote: > The only thing that would be additionally useful is an automated migration > step; I wonder if there's any way I could have a button/link in the > config.jelly that would allow me to construct the new step based on the old > step's

Re: Advanced button issue

On Fri, Aug 12, 2022 at 12:52 PM Nikhil Bhoski wrote: > Hi I am planning to include advanced section in my plugin I am using this > documentation as reference > https://wiki.jenkins.io/display/JENKINS/Jelly-form-controls.html and > used following code in the resources folder and action class

Re: unable to perform jenkins release

On Thu, Aug 11, 2022 at 9:29 AM 'Mohammad Jameel Uddin' via Jenkins Developers wrote: > I am unable to perform mvn release:perform, getting error like this > > Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) > on project aiq: Failed to deploy

Re: AIX server is showing out of memory post jenkins upgrade.

On Fri, Jul 29, 2022 at 9:02 PM Damodara Devops wrote: > We have upgraded to Jenkins 2.332.3 , post > upgrade all the job ran on AIX server is showing 'out of memory'. > All the jobs are running fine before the upgrade. > Would like to know if any one have come across

Re: Next LTS baseline

On Fri, Jul 29, 2022 at 7:53 PM Alexander Brandes wrote:+1 for 2.361 > > It's worth to mention that 2.361 contains several regression fixes too, > which you don't want to miss out. > They could always be backported into 2.360.x. So the question to ask is, do we want everything in 2.361? FWIW I

Re: Script-security

Are you a Jenkins administrator, whose scripts are automatically approved, while those methods are invoked? -- 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

Re: comment-ops-bot available in jenkinsci and jenkins-infra

On Mon, Jul 25, 2022 at 12:20 PM Tim Jacomb wrote: > > Can we have review requests enabled by default while label changes are > opt in? > > I'm not sure if that would scale across the number of infrequently touched > repositories that we have. > Infrequently touched repos are the problem for

Re: comment-ops-bot available in jenkinsci and jenkins-infra

On Mon, Jul 25, 2022 at 12:03 PM Alexander Brandes wrote: > opt out. > Can we have review requests enabled by default while label changes are opt in? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: comment-ops-bot available in jenkinsci and jenkins-infra

On Mon, Jul 25, 2022 at 10:22 AM Tim Jacomb wrote: > It requires no organization permissions, which means anyone can request a > review and add labels to issues and pull requests. > What if I don't want randos on the internet messing up labeling of open PRs in repos I maintain? -- You

Re: Frontend unit tests in core

On Fri, Jul 22, 2022 at 6:39 PM Basil Crow wrote: > > some sort of tab bar. > Looks like it's the tabs over job config forms ("scrollspy" elsewhere). For freestyle at least they were replaced with sidepanel items with similar behavior (plus icons) in 2.360. > I am inclined to vote in favor of

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

On Tue, Jul 19, 2022 at 5:31 AM Mark Waite wrote: > The preferred fix needs a new release of the commons-lang3-api plugin > . The current > maintainer has not responded to previous requests nor to the current > request >

Re: Governance meeting - July 11, 2022

On Mon, Jul 11, 2022 at 6:22 PM Mark Waite wrote: > >- > >Trademark usage request > >from Luminous Productions Co., Ltd > > That's a private mailing list, so this link isn't helpful. Since when are

Re: Is there interest for GitHub issues in core components?

On Thu, Jun 30, 2022 at 10:01 PM Basil Crow wrote: > For example, moving from our > traditional Jira server to Jira Software Cloud (with HTTP redirects if > necessary) would be almost completely transparent to core and plugin > maintainers from the perspective of existing Jira issues, which are

Re: New Plugin With Multiple Components Hosting Question

On Thu, Jun 30, 2022 at 8:55 PM Mark Diesburg wrote: > We could submit just the source for the test-management plugin portion > with reference to the other two components on GitHub since they can be used > independently for other purposes. > > Would this be acceptable? > > Or would we have to

Re: Security approval required on UI-related PRs in Jenkins core

On Wed, Jun 22, 2022 at 9:26 PM 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > Great idea Alex => *@jenkinsci/core-security-review* created > > Thanks for the feedback and yes Tim, I will allocate more people to those > reviews, compared to the hosting requests that were mainly

Re: 401 unauthorized when attempting plugin release

On Wed, Jun 22, 2022 at 4:43 PM Philip Madden wrote: > Plugin: https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin > Release Tag: > https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin/tree/hashicorp-vault-pipeline-1.4 > maven version: 3.8.4 > > After following the instructions

Re: Backporting for LTS 2.346.1 started

On Wed, Jun 22, 2022 at 4:24 PM 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > Hey there, especially Tim, > > The next question related to the extra week delay, what do you expect to > do for the .2 LTS release? It seems that currently it's still scheduled in > 3 weeks. > > I'd keep

Re: TransientActionFactory question

is one that isn't trivial to do otherwise (having a reference to the run after loading from disk), so I can see why this might get ignored in the transient action factory case, that's easy to solve. Here's a patch to make it work: https://gist.github.com/daniel-beck/34b7a1425f85bfa499bd43823d17f030

Re: New gradle plugin, attempting to publish or upload hpi for the 1st time

On Tue, Jun 14, 2022 at 8:51 PM 'ggillman ggillman' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > 2022-06-13T10:11:11.174-0500 [ERROR] > [org.gradle.internal.buildevents.BuildExceptionReporter] > Could not PUT ' >

Re: Is there interest for GitHub issues in core components?

On Mon, Jun 13, 2022 at 9:05 PM 'Jesse Glick' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > On Mon, Jun 13, 2022 at 10:02 AM 'Daniel Beck' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> On Mon, Jun 13, 2022 a

Re: Is there interest for GitHub issues in core components?

On Mon, Jun 13, 2022 at 3:55 PM Tim Jacomb wrote: > The barrier to entry on Jira is a lot higher than on GitHub, many people > struggle to report issues. > Is people not reporting issues they experience really a problem we have? Unless we step up our responsiveness, having a backlog of issues

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

That URL hasn't worked in a long time. Cloning the devenv repo and running the clone script, including build, works for me. Are you sure you don't have a Maven settings.xml file or something that specifies custom URLs? On Thu, Jun 2, 2022 at 2:18 AM Simon Matthews wrote: > I am running on a

Re: 409 errr on plugin release

> On 21. May 2022, at 20:10, priya jagyasi wrote: > > Can anyone please tell me what this implies? What am I doing wrong, please > help. You are trying to release a plugin using JEP-229 CD without having it configured correctly as documented at

Re: Configure release drafter

On Thu, May 19, 2022 at 1:27 PM priya jagyasi wrote: > I need help in configuring the release drafter to release my Jenkins > plugin. The step here > https://www.jenkins.io/doc/developer/publishing/releasing-cd/#configure-release-drafter > says to include *_extends: .github* on >

Re: How does dropdownList work and what can affect the descriptorImpl

On Mon, May 9, 2022 at 7:13 PM Michael Carter wrote: > debug var.: > org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition$DescriptorImpl@72d8eb26 > > debug currDesc: > org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition$DescriptorImpl@6904e8d2 > This means there are two different instances

Re: Next LTS baseline

On Sat, May 7, 2022 at 12:22 AM Mark Waite wrote: > The issues that worried me were: > >- JENKINS-68303 - >Schedule build icon no longer indicates the "scheduled to be built" state >since 2.321 - merged for 2.347 next Tuesday > > … >

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

On Thu, Apr 28, 2022 at 12:20 AM Oleg Nenashev wrote: > Jenkins Test Harness is not a core component, it is a separate deliverable > with its own release lifecycle > Same for other developer tools AFAICT > Not part of the core deliverable, but core team repos. Projects still likely cross issue

Re: Correct permission checks to add

On Thu, Apr 28, 2022 at 1:12 AM Tim Van Holder wrote: > For those bits related to the global tool setup, I simply use Jenkins.get > ().checkPermission(Jenkins.MANAGE); instead. Again, this seems to make > sense, given the tool setup lives among the Manage Jenkins options. > Just in case, please

Re: Checking whether a step from a plugin is in actual use in an instance

> On 18. Apr 2022, at 10:38, Tim Van Holder wrote: > > Can a plugin include code that will update a freestyle project that uses the > DotNetFoo builder to use the DotNet builder with a Foo argument instead? Potentially doable via readResolve as well. -- You received this message because

Re: Checking whether a step from a plugin is in actual use in an instance

On Mon, Apr 11, 2022 at 11:53 PM Tim Van Holder wrote: > I maintain a plugin (dotnet-sdk) that mostly provides a global tool and > associated wrapper. > But it also has a bunch (currently 11) convenience steps that can be used > (instead of the wrapper plus bat/pwsh/...). > I got a ticket saying

Re: Jenkins on SQLite

> On 3. Apr 2022, at 03:58, Basil Crow wrote: > > I put together a quick prototype today at > https://github.com/basil/jenkins/tree/sqlite. This is really cool, thanks for sharing! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Intellij Stapler Framework Support compatibility

On Wed, Mar 30, 2022 at 6:41 AM Denys Digtiar wrote: > > Would anybody be opposed if I bump compatibility to some newer version? > Maybe 2020.x or something like that? > > Go for it. As with Jenkins, if you don't update the core, you're probably not updating plugins either. -- You received

Re: Reverting JENKINS-20679

On Wed, Mar 30, 2022 at 7:32 AM Basil Crow wrote: > > > 1. IIRC I've seen plugins requiring Java 11 that just don't declare it. > So it's not unused because it isn't needed, but perhaps because plugin > authors are unaware of it? > > I am not familiar with such cases, but I seriously doubt there

Re: Reverting JENKINS-20679

On Wed, Mar 30, 2022 at 7:16 AM Basil Crow wrote: > As part of my work on Java platform support in Jenkins, I have > encountered the subsystem introduced in JENKINS-20679, which allows > plugins to request a newer version of Java than the corresponding > core. Based on a preliminary search of

Re: error occuring during mvn release

On Thu, Mar 24, 2022 at 1:26 PM 'Mohammad Uddin' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi All, > > I am getting this error "The initial value of this parameter is ignored, > and the parameter is overwritten here. This often indicates a mistaken > belief that the write

Re: [jenkins-infra] Re: Missing Version Installation Count

On Wed, Mar 23, 2022 at 3:46 PM Bryan Stopp wrote: > I don't suppose there's any way to control the detailed output from a > config in my project? For example, drop all the 1.x installs? No. People have those versions installed and report them as such. The filters that exist attempt to filter

Re: Request to add sponsored-issues

This topic seems vaguely related to the Jenkins job board topic from a few months ago ( https://groups.google.com/g/jenkinsci-dev/c/q2F1AcFBbBE/m/6Ew7pMpDBAAJ ); as this is essentially a variant on contract work. Perhaps there's a solution covering both? -- You received this message because you

Re: Request to add sponsored-issues

On Mon, Mar 21, 2022 at 9:55 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > https://app.bountysource.com/issues/106189146-jenkins-67963-add-option-to-save-bandwidth-and-resources-which-are-wasted-unnecessarily > > Looks like it just imported all the

FYI: Problems publishing artifacts in Artifactory

Hi everyone, We've observed problems publishing artifacts in Artifactory, logs indicate the disk is full. So if you're unable to release stuff the next few days, that is probably why. Daniel -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Publishing plugin leads to 401

On Fri, Mar 4, 2022 at 8:23 AM Philipp Straubinger < philipp.straubin...@uni-passau.de> wrote: > Yes, I took the whole generated settings.xml to ~/.m2/settings.xml > That's wrong. Try doing what the instructions I link to say. -- You received this message because you are subscribed to the

Re: Publishing plugin leads to 401

On Thu, Mar 3, 2022 at 1:43 PM Philipp Straubinger < philipp.straubin...@uni-passau.de> wrote: > Hi, > > this is how it looks like in Artifactory after following the documentation: > … > > The generated settings.xml is in the attachments. > Did you take the encrypted password from this file, and

Re: Jenkins 2.332.1 LTS RC testing started

On Wed, Mar 2, 2022 at 3:47 PM Alex wrote: > I still get the warning about the DoS vulnerability with XStream, though > that fix is included. Does the warning magically vanish once the LTS builds > are shipped for GA? Addressed by https://github.com/jenkins-infra/update-center2/pull/573 --

Re: Publishing plugin leads to 401

On Wed, Mar 2, 2022 at 7:19 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > So i confirmed > https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-gamekins.yml > has the right path (would appreciate a second pair of

Re: Governance meeting Feb 23, 2022

On Thu, Feb 24, 2022 at 11:27 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > Or format as a date, like 2022.02.23, so we can issue up to one release > a day. Or drop MRP and use CD versions… > > how would lts work? 2022.02.23.1? I think that'll confuse a lot

Re: Jenkins 2.332.1 LTS RC testing started

On Fri, Feb 25, 2022 at 2:19 PM Tim Jacomb wrote: > It'll be update center dynamic update sites most likely. > Correct: $ curl -IL https://updates.jenkins.io/update-center.json?version=2.332.1 HTTP/1.1 302 Found Date: Mon, 28 Feb 2022 23:45:56 GMT Server: Apache/2.4.29 (Ubuntu) Location:

Re: Jenkins Security Scan now generally available

On Mon, Feb 28, 2022 at 8:00 PM Basil Crow wrote: > After upgrading a dozen or so plugins to Security Scan v2, the Jenkins > Security Scan workflow on the main branch failed with: > > Called workflows cannot be queued onto self-hosted runners across > organisations/enterprises. Failed to queue

Re: Jenkins Security Scan now generally available

On Fri, Feb 25, 2022 at 11:49 AM Daniel Beck wrote: > > It looks like GitHub's action can do what I cannot because it uses an > undocumented API. > > > I'll update this thread once it works, meanwhile you can watch > https://github.com/jenkins-infra/jenkins-security-scan/iss

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

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

  1   2   3   4   5   6   7   8   9   10   >