Re: Safe ways to handle extraction of features into new plugins

On Mon, Sep 27, 2021 at 7:18 AM Chris Kilding < chris+jenk...@chriskilding.com> wrote: > some 3rd party Jenkins management tools […] do not download transitive > plugin dependencies when they install a plugin. > So fix them, or advise your users to avoid them? -- You received this message becau

Re: Add Mark Waite to Jep editors

Oh yes please +1 -- 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 visit http

Re: How to deal with class update and serialization of Jenkins configurations

On Mon, Oct 11, 2021 at 10:51 AM Goyot, Martin wrote: > Is there a way in Jenkins to deal with such updates of classes ? > Typically solvable by adding a `readResolve` method. You are advised to verify correctness using a `JenkinsRule` test making use of `@LocalData`. -- You received this mess

Re: How to deal with class update and serialization of Jenkins configurations

On Tue, Oct 12, 2021 at 6:07 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > new options are often phrased so the legacy default behavior corresponds > to the default field value ("dontDoWhatever" field names are common). > To be clear, use of the negative sense

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

On Sun, Oct 17, 2021 at 9:58 AM Oleg Nenashev wrote: > I would actually expand that to all developer tools we have in the project Yes! At a minimum - jenkins-test-harness - pom - plugin-pom - bom - maven-hpi-plugin - incrementals-tools - acceptance-test-harness - archet

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

On Sun, Oct 17, 2021 at 4:50 AM Oleg Nenashev wrote: > Currently we have only a few issues in Jira > BTW if switching canonical issue tracker I recommend also closing any remaining open issues in Jira and refiling them in GitHub (with links in either direction for reference). -- You received t

Re: Creating a testcontainer for Jenkins Update Center

On Wed, Oct 20, 2021 at 10:05 AM Oleg Nenashev wrote: > >- What would everyone say about introducing dependency on >testcontainers into Jenkins Test Harness directly? > > Why would you need that when you can already add such a test dep yourself? > >- Should we go ahead and deprecate

Re: Creating a testcontainer for Jenkins Update Center

On Fri, Oct 22, 2021 at 9:53 AM Oleg Nenashev wrote: > W.r.t Docker Fixtures, a while ago I tried hacking a wrapper so that it > uses testcontainers under the hood. Seems risky. Probably suffices to just incrementally rewrite the relatively modest number of existing uses. Why would you need th

Re: Governance meeting Nov 3, 2021

On Thu, Nov 4, 2021 at 6:00 PM Mark Waite wrote: > less than 50% of those installations are running Java 11. > > We won't let the git client plugin depend on a JGit release that would > block a significant portion of the Jenkins installed base > As usual in these discussions, statistics about ho

Re: Support for experimental (beta) releases on JEP-229

The system is not designed to support marking releases as beta. I am not sure such a requirement is even conceptually compatible with the style of automatic deployment. If such a requirement is common, I think it would need to be done differently, as a true promotion: the same version number and bi

Re: Support for experimental (beta) releases on JEP-229

On Tue, Nov 9, 2021 at 3:06 PM José Lamas Ríos wrote: > Regarding 'conceptually compatible' I'm not sure whether you refer to >> automatic deployment in general or to the way it's implemented in this case >> > Well, any scheme by which the update center pattern-matches on plugin version numbers.

Re: Support for experimental (beta) releases on JEP-229

On Wed, Nov 10, 2021 at 7:26 PM José Lamas Ríos wrote: > GitHub does allow marking releases as in draft state and also, as a > separate concept, optionally marking them as 'pre-release' > You are right, pre-release status is what I was thinking of, not draft. I have not used this feature before

Re: Enabling CD for plugin

On Thu, Nov 11, 2021 at 10:14 AM 'jsupun' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > It looks like I enable it via jenkins-infra/repository-permissions-updater. Yes. Wasn't sure if I need to checkout the repo, make the changes to my plugin > permissions, and then make a P

Re: Windows build fails with java.lang.RuntimeException: Failed to serialize hudson.model.Project

On Fri, Nov 12, 2021 at 4:21 PM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > restructure your code so this isn't a field of your class. > Do that. https://github.com/jenkinsci/keeper-secrets-manager-plugin/blob/870ee7ee7c26df6877cb78b7831511db89974c72/src/main/j

Re: Backporting for LTS 2.319 started

I think the `lts-candidate` label should get removed when `*-fixed` is added, right? -- 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

Re: Backporting for LTS 2.319 started

Also there was some discussion about whether JENKINS-66947 was suitable for backport. > -- 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+unsu

Re: Enabling Continuous Delivery / automated release process for Gradle project

On Wed, Nov 17, 2021 at 4:05 AM Tim Jacomb wrote: > That's assuming that the gradle plugin supports incrementals which I don't > know if it does. > It does not, and the whole concept is rather specific to Maven. Stepping back, there are basically two sides to JEP-229: a backend patch to the RPU

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

On Wed, Nov 17, 2021 at 4:03 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > […] do not show a rapid growth of Java 11 adoption > > Every time this topic comes up I need to remind people that while the proportion of installations currently running 8 vs. 11 is an

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

On Wed, Nov 17, 2021 at 5:57 AM Ullrich Hafner wrote: > […] is stored in a CopyOnWriteArrayList. If your background thread > serializes my instance during the loop it can happen that the loop variable > is already set, but the list with the results is not. > Hard to follow what you are saying wi

Re: ConcurrentModificationException during pipeline serialization (MAX_SURVIVABILITY)

On Wed, Nov 17, 2021 at 10:02 AM Ullrich Hafner wrote: > I do not have fields anymore in the step > > Any class which could be referenced directly or indirectly as part of the program state (object graph rooted in Pipeline virtual threads) must be written to expect concurrent access from a serial

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

On Thu, Nov 18, 2021 at 4:57 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > On Thu, Nov 18, 2021 at 10:22 AM 'Björn Pedersen' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> you can build projects in any java version you like, even if jen

Re: release went wrong?

On Fri, Nov 19, 2021 at 4:47 PM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > It's saying the git tag already exists. > One of many headaches you need to deal with when using `maven-release-plugin`, along with local credentials. You may consider https://www.jenki

Re: BOM builds on ci.jenkins.io

On Tue, Nov 23, 2021 at 2:32 PM Damien Duportal wrote: > As part of reducing the infrastructure costs, we would like to stop > triggering builds of the pull requests on the BOM project when the target > branch is updated (as suggested in > https://issues.jenkins.io/browse/INFRA-1633 if I'm correc

Re: BOM builds on ci.jenkins.io

On Wed, Nov 24, 2021 at 2:36 PM Damien Duportal wrote: > the setting "Ignore rebuilding merge branches when only the target branch > changed" had been applied… > That probably suffices as a workaround (I have not tried this plugin

Re: Problem with accessing Jenkins items in onOffline() call from ComputerListener

On Thu, Dec 2, 2021 at 5:07 AM t4k30ff wrote: > Is this a bug? > I believe so. Most likely the thread calling `onOffline` is running under some user’s authentication (or “anonymous”) and that user lacks read permission to some jobs. Add a `Thread.dumpStack();` call to your listener to find out.

Re: Enabling Continuous Delivery / automated release process for Gradle project

On Wednesday, November 17, 2021 at 8:29:07 AM UTC-5 Jesse Glick wrote: > One thing which should be possible in principle, but which I have not had > reason to try, is to use MRP with the backend part. > Implemented in https://github.com/jenkins-infra/jenkins-maven-cd-action/pull/14. Not as smo

Re: Jelly headache, page that include other page

Whatever https://github.com/jenkinsci/nodejs-plugin/blob/6d9d6348f1a2fffddc4b9d711a5aef3557ffa21e/src/main/java/jenkins/plugins/nodejs/tools/MirrorNodeJSInstaller.java#L276-L280 was intended for, it looks wrong. Try deleting that as well as https://github.com/jenkinsci/nodejs-plugin/blob/6d9d6348f1

Re: Unable to release, unable to access my account

As an alternative, you can consider https://www.jenkins.io/doc/developer/publishing/releasing-cd/ which does not require you to have any credentials beyond GitHub write access to the plugin. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: Feedback on some analysis I'm doing

On Mon, Dec 13, 2021 at 1:35 PM 'rsomas...@netflix.com' via Jenkins Developers wrote: > That suggests that Jenkins Core would prefer plugins to use slf4j-api. If > that's the case, all plugins that depend on jenkins-core should use > slf4j-api > No, Jenkins core uses java.util.logging, and the g

Re: Enabling Continuous Delivery / automated release process for Gradle project

On Tue, Dec 14, 2021 at 9:53 AM 'jn...@cloudbees.com' via Jenkins Developers wrote: > there is possibility of something part way between the current CD flow (no > junk pushes) and m-r-p > As mentioned previously

Re: Feedback on some analysis I'm doing

Please refer to https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/ for background. -- 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

Re: Enabling Continuous Delivery / automated release process for Gradle project

On Tue, Dec 14, 2021 at 6:04 PM James Nord wrote: > the flatten plugin confuses tools Which? I think we have ironed out any problems as lots of components have picked up JEP-305. Even seems to work fine on BOMs; the last things I am hesitant

Re: Annotation versions

On Tue, Dec 14, 2021 at 11:12 PM Basil Crow wrote: > 1) … stop shipping the JARs in core This could cause issues. Though class loaders are OK just ignoring unloadable annotations, some tools which work with bytecode and reflective APIs can encounter errors. Safest to have the annotation present

Re: Expose data to API from Jenkins Shared library

On Wed, Dec 15, 2021 at 5:27 AM Oscar Arevalo Loyola wrote: > I want to achieve this: > https://wiki.jenkins-ci.org/display/JENKINS/Exposing+data+to+the+remote+API > but from a Shared Library, not from a plugin. > That is not supported. Just use a plugin. -- You received this message because y

Re: Annotation versions

On Wed, Dec 15, 2021 at 4:35 PM James Nord wrote: > The plugin pom probably needs to remove a lot of cruft that makes it work > with older release now. > I tried in https://github.com/jenkinsci/plugin-pom/pull/457 but apparently got it wrong; if someone has time to dig deeper that would be great

Re: Enabling Continuous Delivery / automated release process for Gradle project

On Thu, Dec 16, 2021 at 10:44 AM 'jn...@cloudbees.com' via Jenkins Developers wrote: > you are still tagging the commit "[maven-release-plugin] prepare release > project-a.bcd" the only difference is that these commits never appear on > the mainline branch (master) > Yes, this is possible. Gene

Re: Annotation versions

On Fri, Dec 17, 2021 at 3:51 PM Basil Crow wrote: > I propose we explicitly add javax.annotation-api to the core BOM and > plugin POM as we already do for spotbugs-annotations, > jcip-annotations, and access-modifier-annotation. Seems reasonable. A similar question applies to symbol-annotation

Re: Annotation versions

On Fri, Dec 17, 2021 at 4:30 PM Basil Crow wrote: > Sorry, I should have clarified that I was proposing that we add > symbol-annotation to plugin-pom with scope=provided and optional=true Do we even need to? It is just listed as a plain dependency of `jenkins-core`. So it should be in the plug

Re: Annotation versions

On Fri, Dec 17, 2021 at 5:34 PM Basil Crow wrote: > I suppose by the same logic we should remove > access-modifier-annotation, spotbugs-annotations, and > animal-sniffer-annotations from plugin-pom as well. > To the extent that you can verify that these libraries would be in the classpath for an

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

On Sun, Dec 19, 2021 at 9:13 PM Basil Crow wrote: > When loading plugins without "Jakarta-Ready: true" in a Jakarta EE 9 > environment, we will probably need to apply some special compatibility > transformations, exempli gratia, transforming the binaries after > exploding the plugin or loading th

Re: Jenkins 2.319.2 LTS RC testing started

Should we not start requiring builds to be stable, and then using the Incrementals download URL? https://ci.jenkins.io/job/Core/job/jenkins/job/stable-2.319/16/testReport/ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe fro

Re: Setting up automated plugin release

On Wed, Dec 22, 2021 at 6:10 AM Marit M wrote: > 202 > Error: > on='[ERROR] Make sure `git status -s` is empty before using -Dset.changelist > https://github.com/jenkinsci/bmc-cfa-plugin/pull/12 -- Y

Re: Setting up automated plugin release

https://github.com/jenkinsci/bmc-cfa-plugin/pull/15 ought to fix the version format I think. 61.vb33105387180 etc. You cannot easily delete a release, but there is not generally any need to. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: Setting up automated plugin release

On Tue, Dec 28, 2021 at 5:50 AM Marit M wrote: > now I understand that Incrementals appends a commit number, plus a SHA, to > version numbers. > https://www.jenkins.io/doc/developer/publishing/releasing-cd/#pom-file-modifications says so; is there a way we could make this more prominent? -- Yo

Re: Backward compatibility policy regarding dependent plugins

On Fri, Dec 31, 2021 at 8:14 AM 'Réda Housni Alaoui' via Jenkins Developers wrote: > Looking at https://plugins.jenkins.io/sonar-gerrit/#dependencies, I do > not see any public dependent plugin. > What's the policy in this kind of situation? > > Should I go ahead and potentially break compatibili

Re: Jakarta Mail and Jakarta Activation

On Sun, Jan 2, 2022 at 4:36 PM Basil Crow wrote: > The pesky validation routine in > JenkinsLocationConfiguration#doCheckAdminAddress could be reworked to > use UberClassLoader to invoke that same functionality from > javax-mail-api and/or jakarta-mail-api (if installed), or the > validation coul

Re: Backward compatibility policy regarding dependent plugins

On Tue, Jan 4, 2022 at 3:15 AM 'Réda Housni Alaoui' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I guess at least @DataBoundSetter and @DataBoundConstructor would have to > be kept for pipeline scripts. > If you are talking about a `Step` or a `Describable` used by one, yes t

Fwd: Succession of timeouts during Docker actions on ci.jenkins.io

[Somehow did not get sent to the list. Reposting:] On Tue, Jan 4, 2022 at 7:57 AM Chris Kilding wrote: > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal io.fabric8:docker-maven-plugin:0.38.0:start (start-moto) on project > : I/O Error > This is rather opaque. Th

Re: Jakarta Mail and Jakarta Activation

On Tue, Jan 4, 2022 at 12:40 PM Basil Crow wrote: > I think the needs of the Jenkins project would be best served if we had > the ability to merge and release PRs for those odds and ends, but this > isn't simple to arrange because they generally live in Kohsuke's own > GitHub organization rather

Re: ASM in core

On Tue, Jan 4, 2022 at 3:07 PM Basil Crow wrote: > the only remaining consumers of ASM in core will be Stapler and > access-modifier > `access-modifier` is not a big deal since it is used only at compile time—need not be shipped in core. The usage in Stapler is an obstacle. IIUC until a plugin

Re: ASM in core

On Tue, Jan 4, 2022 at 5:22 PM Basil Crow wrote: > So should I look into the shading approach further? That basically takes us back to the unfortunate state we were in with Kohsuke’s series of shaded & repackaged ASM libraries, where we could not give a clear answer as to what we were actually

Re: [jenkins-infra] Succession of timeouts during Docker actions on ci.jenkins.io

On Wed, Jan 5, 2022 at 7:41 AM Chris Kilding wrote: > Log is here: > More useful is the test stderr https://ci.jenkins.io/job/Plugins/job/aws-secrets-manager-secret-source-plugin/job/PR-37/2/testReport/io.jenkins.plugins.casc.secretsmanager/SecretSourceIT/linux_11_2_263_4___Build__linux_11_2_263

Re: Incremental releases show not up as GitHub action result anymore

On Wed, Jan 5, 2022 at 11:45 AM Tim Jacomb wrote: > See > https://github.com/jenkinsci/incrementals-tools/releases/tag/parent-1.3 > No, that is unrelated. I have also noticed this. The artifact does actually get deployed, e.g. https://github.com/jenkinsci/prism-api-plugin/pull/2/commits/2b9b13

Re: [jenkins-infra] Succession of timeouts during Docker actions on ci.jenkins.io

On Mon, Jan 10, 2022 at 6:19 AM Chris Kilding < chris+jenk...@chriskilding.com> wrote: > kubernetes-pipeline-plugin and gitlab-plugin appear to be the 2 other > plugins under jenkinsci that use docker-maven-plugin. Is it worth advising > them to switch to Testcontainers at some point as well? > W

Re: Abstract type and groovy syntax

On Sun, Jan 9, 2022 at 5:11 AM 'Réda Housni Alaoui' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Now I need to find a way to keep supporting the map style. Perhaps with a > setter accepting a Map? > You mean the map style with `$class`? You need not do anything special, this

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

Anyone with infra-level permissions up for this? I just tried to switch `maven-hpi-plugin` to GH Issues but noticed I lack admin access to the repo (and certainly I would lack permissions to mark a Jira component closed for entry of new issues, which I think is an option). -- You received this me

Re: Help needed with a stuck PR merge

On Thu, Jan 20, 2022 at 9:51 AM Konstantin Voin wrote: > No luck > https://github.com/jenkins-infra/helpdesk/issues/new/choose -- 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

Re: Jenkins 2.319.3 LTS RC testing started

On Wed, Jan 26, 2022 at 4:06 AM 'Ildefonso Montero' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Download the release from > https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/jenkins-war/2.319.3-SNAPSHOT/jenkins-war-2.319.3-20220126.084922-1.war > Maybe be

Re: assistance with running test locally

On Fri, Jan 28, 2022 at 2:16 PM Niv Keidan wrote: > command: mvn -Dtest=hudson.model.NodeTest test The exact same command works for me. Are you using JDK 8? Did you try `mvn -Pquick-build clean install` to start? Did you check behavior in `master`? -- You received this message because you are

Re: Plugin BOM upgrade, 2.289.1 vs. 2.289.3

I am not sure there is a consensus yet in this area; see discussion in https://github.com/jenkinsci/archetypes/pull/376#discussion_r781199364 and elsewhere. My inclination is to require 2.289.3; there does not seem to be much point in testing against an outdated LTS point release, especially one th

Re: Plugin BOM upgrade, 2.289.1 vs. 2.289.3

On Mon, Jan 31, 2022 at 10:26 AM 'jn...@cloudbees.com' via Jenkins Developers wrote: > Testing (binary api) of the compatibility set is done in the BOM itself > For plugins *in* the BOM. There are other reasons to want to use a reasonably recent BOM: you may see newly available APIs, or new dep

Re: Plugin BOM upgrade, 2.289.1 vs. 2.289.3

On Mon, Jan 31, 2022 at 10:02 AM Jesse Glick wrote: > I will file a docs PR making that policy change and see where the > discussion goes. > https://github.com/jenkins-infra/jenkins.io/pull/4876 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Artifactory permissions for components with CD enabled

On Tue, Feb 8, 2022 at 6:02 AM 'jn...@cloudbees.com' via Jenkins Developers wrote: > we are still granting users permission to Artifactory for deployment of a > plugin that they maintain even if the plugin is using CD > > Is there any reason still to do this? > The initial stance for JEP-229 was

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 no

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 rec

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 regressi

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

To follow up, 4.36 should fix this. -- 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

Re: Jenkins Security Scan now generally available

Do we generally recommend this for any plugin? If so, it would be great to add this to `archetypes`. -- 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 jenkin

Re: Jenkins Security Scan now generally available

Tried it out on a plugin I maintain. Seems to work. I suppose any results would appear in `/security/code-scanning` to repo admins only? Will the *Checks* tab of a PR or trunk commit always be green so long as scanning completed, even if there are violations? The scan should pass `-ntp` to Maven b

Re: Jenkins Security Scan now generally available

On Tue, Feb 22, 2022 at 4:41 PM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > PR-specific results are shown directly and publicly in the PR. GitHub > compares results from the PR to results from the target branch to only show > differences. > Oh nice. > And if

Re: Jenkins Security Scan now generally available

On Wed, Feb 23, 2022 at 3:29 PM Basil Crow wrote: > curl: (22) The requested URL returned error: 403 > Failed to upload results > I get the same on a trunk commit. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

Re: Governance meeting Feb 23, 2022

> >- > >Version number to yearly? >- > > Starting in with 23.01 being the first week of the year 2023 > - > > Harder to skip/reissue/etc a release > > 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… Versi

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

On Thu, Feb 24, 2022 at 8:42 AM Mark Waite wrote: > more exploring of potential issues related to the transition. >> > My main concern is about bugs, like JENKINS-59910 which no one seems to be evaluating. If stuff works when run on 8 and does not work when run on 11 then users will not accept th

Re: Governance meeting Feb 23, 2022

On Wed, Feb 23, 2022 at 6:46 PM Slide wrote: > Windows installers have issues with versions like this Interesting. In general native packagings may have to process the version number to follow specific conventions or restrictions. The product version is already mangled to support LTS releases,

Re: New maven message from hpi plugin 3.26?

Filing as https://github.com/jenkinsci/maven-hpi-plugin/issues/325. -- 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.

Re: Java 17 support added to build toolchain

Thanks Basil! Mark I added an analysis in your PR. -- 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

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

On Tue, Apr 12, 2022 at 1:40 PM Tim Van Holder wrote: > a relatively simple way to have a build step for freestyle that would > essentially then have a dropdown for the 11 "real" steps which then shows > their configuration when selected > This is straightforward. (`ui-samples-plugin` may be ins

Re: Capturing the remoteIpAddr on login failure?

On Wed, Apr 13, 2022 at 5:21 AM 'Cyrille Le Clerc' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > did we consider making the Jenkins SecurityListener > an > adapter of the Spring ApplicationEventPublisher >

Re: Jenkins build failure: "...project cli: Error creating shaded jar: duplicate entry: META-INF/services/io.jenkins.cli.shaded.jakarta.websocket.ContainerProvider"

On Fri, Apr 15, 2022 at 12:08 PM 'Cyrille Le Clerc' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Is it a known build problem? > Other than Maven 3.8.5 being broken as Mark mentioned, there are not in general known build problems. Someone would fix the problem right away, if i

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

On Mon, Apr 18, 2022 at 4:38 AM 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? > It is possible with an `@Initializer`. I'd have to keep them around for pipeline use a

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

On Mon, Apr 18, 2022 at 3:16 PM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Potentially doable via readResolve as well. > > Unfortunately you cannot do this sort of thing via `readResolve` so far as I know. Ideally there would be some API which you could call f

Re: get all agents used by a build

On Wed, Apr 20, 2022 at 4:03 AM Mathieu DELROCQ wrote: > I have a Run object and I would like to get all agents used in this run. > For `AbstractBuild` (traditional job types), there is a getter. For Pipeline (`FlowExecutionOwner.Executable`) you would need to iterate the `FlowNode`s looking for

Re: get all agents used by a build

On Fri, Apr 22, 2022 at 11:18 AM Mathieu DELROCQ wrote: > get the duration of the stage wich use the agent > Should be possible to calculate given https://javadoc.jenkins.io/plugin/workflow-api/org/jenkinsci/plugins/workflow/actions/TimingAction.html -- You received this message because you ar

Re: Moving ATH tests closer to the code under test

On Tue, Apr 26, 2022 at 12:28 PM Basil Crow wrote: > I wonder if we could design a system such that for the common case only a > single Maven project is needed Sounds tricky. `acceptance-test-harness` has a bunch of dependencies some of which clash with those in Jenkins core or some plugins, so

Re: Guidance on whether/where to file issues for build warnings

On Fri, May 13, 2022 at 5:50 PM Tim Van Holder wrote: > I don't have any direct references to either of these. Is this a bug in > the BOM? > Or the parent POM, or something. If you manage to track down the root cause, please file a PR to fix it. And these warnings went away when using Maven 3.8

Re: Configure release drafter

> > On Thursday, May 19, 2022 at 5:26:51 AM UTC-6 Priya wrote: > >> The step here >> https://www.jenkins.io/doc/developer/publishing/releasing-cd/#configure-release-drafter >> > Are you intending to configure your plugin for continuous delivery? says to include *_extends: .github* on >> https://gi

Re: 409 errr on plugin release

On Sat, May 21, 2022 at 4:21 PM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > You are trying to release a plugin using JEP-229 CD without having it > configured correctly > As mentioned in https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/1#iss

Re: 409 errr on plugin release

On Tue, May 24, 2022 at 1:09 PM priya jagyasi wrote: > could you please let me know what needs to be done to enable CD on my > plugin. > Please read the instructions. https://www.jenkins.io/doc/developer/publishing/releasing-cd/#update-maven-pom-and-config -- You received this message because

Re: 409 errr on plugin release

https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6 -- 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...@googlegrou

Re: Plugin Updates

On Wed, May 25, 2022 at 1:37 PM priya jagyasi wrote: > Can anyone please let me know how much time it takes to have the plugin > under 'Updates' in the Jenkins update center for any instance after the > GitHub workflow release is completed successfully? Is it immediate or any > approximate time?

Re: New Plugin hosting request: Docker Ephemeral Cloud

On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu wrote: > I believe the real horse race is between the > underlying docker libraries. In the end, we'll likely have a clear winner, > and can standardize a group of plugins around that. Perhaps docker-commons > becomes that focal point, and we have smaller

Re: Secrets in cloudbees builds of plugins

On Tue, Nov 17, 2015 at 1:57 PM, Gavin Mogan wrote: > I love having my plugins built constantly through cloudbees. I presume you mean: https://jenkins.ci.cloudbees.com/job/plugins/ ? > Is there a way to do post build tasks (like run codecov) Well you include that in your POM. There is no way cu

Re: Why doesn't this jelly page show the configuration

On Wed, Nov 18, 2015 at 9:56 AM, Nigel Magnay wrote: > public class HelloWorldPlugin extends Plugin implements > Describable Oof. Just do not use `Plugin`; consider it deprecated. Try `GlobalConfiguration` instead. -- You received this message because you are subscribed to the Google Groups "

Re: Why doesn't this jelly page show the configuration

On Wed, Nov 18, 2015 at 11:53 AM, Kanstantsin Shautsou wrote: > Somebody should add to Plugin javadoc link to GlobalConfig I am tempted to simply deprecate `Plugin` (or perhaps just its constructor, which subclasses would be forced to call) in favor of the modern replacements: · `GlobalConfigura

Re: Why doesn't this jelly page show the configuration

On Wed, Nov 18, 2015 at 1:21 PM, Kanstantsin Shautsou wrote: > I thought it is right entry Point if somebody wants to use some plugin > specific actions as it obvious entry point for plugin Maybe I am not understanding what you wrote, but why do you need to extend `Plugin` at all if you just wan

Re: Upgrading Plugin to use Credentials

On Thu, Nov 19, 2015 at 6:19 PM, Gavin Mogan wrote: > Is there a way to setup a parent default credential? (job -> folder -> global) There is not currently any support for per-job credentials (JENKINS-27398), but per-folder credentials are routine. The user may configure credentials at the system

Re: best ide

On Fri, Nov 20, 2015 at 5:15 AM, Stephen Connolly wrote: > For developing and debugging Jenkins, in my experience, keep as far away > from Eclipse as possible I have also heard of a lot of problems, but some people do it anyway. Dedicated plugins exist for Jenkins plugin development in both IDEA

Re: Why doesn't this jelly page show the configuration

On Fri, Nov 20, 2015 at 7:58 AM, Kanstantsin Shautsou wrote: > With annotations in different parts of > code you can't handle sequence of actions during start/stop. Spreading many > start/stop/post-init hooks with annotations in different classes makes not > obvious lifecycle Nothing is stopping

Re: Using Guice to Inject something in build (publish) steps

On Mon, Nov 23, 2015 at 2:07 PM, Kirill Merkushev wrote: > when i use @Inject annotation on @Extension class - all works perfectly, > but with any kind of Describable (which should be created same as any > extension i think) it doesn't work. `Describable`s are not singletons or extensions and can

Re: Using Guice to Inject something in build (publish) steps

Actually what you are trying to do has nothing to do with `Describable`, but with `Builder`. At any rate, that does not work either. DI in Jenkins is very limited. You can only wire extensions, or `Jenkins`, to one another. If you want my opinion, you should not bother with it at all. -- You rece

  1   2   3   >