Re: Allowed licenses for libraries in Jenkins plugins?

> On 21. Jul 2021, at 04:39, Mark Waite wrote: > > The maverick-synergy library is LGPL3 licensed. Is it allowed to use an > LGPL3 licensed library in a Jenkins plugin? > The governance document explicitly allows LGPL even for use in core. We don't care about plugins distributed by the pr

Postponing 2.303.2 by two weeks

Hi everyone, I'd like to postpone 2.303.2 by two weeks. RC would be scheduled for September 22, the final release on October 6. All future scheduled dates would be postponed accordingly. We've done this occasionally in the past when there are scheduling or availability issues, typically around

Re: Hosting && Gavin Schedule

> On 17. Sep 2021, at 04:32, 'Gavin Mogan' via Jenkins Developers > wrote: > > So sure, someone other than you can do more in-depth reviews of the code. > I've been doing absolute basic checks with the expertise I have. I was very > clear when I took over the hosting lead position that I wa

Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team

> On 22. Sep 2021, at 11:14, Oleg Nenashev wrote: > > It would be great to have Basil joining the Jenkins core maintainers team. I > propose to officially add Basil to the Jenkins core team. IMHO the code > reviewer stage can be skipped, because he has been already contributing a lot > to t

Re: Release team

On Mon, Sep 27, 2021 at 10:07 AM Tim Jacomb wrote: > Can someone create the GitHub team please and make me maintainer? > Do it yourself? :P (FTR I made Tim an owner of jenkinsci, seemed silly for him not to be.) -- You received this message because you are subscribed to the Google Groups "J

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

On Mon, Sep 27, 2021 at 1:17 PM Chris Kilding < chris+jenk...@chriskilding.com> wrote: > However there is a problem that some 3rd party Jenkins management tools > (i.e. not Jenkins' own tools like Plugin Installation Manager CLI) do not > download transitive plugin dependencies when they install a

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

On Mon, Sep 27, 2021 at 1:53 PM Chris Kilding < chris+jenk...@chriskilding.com> wrote: > As long as both extracting a feature and adding a feature with a > dependency would cause Jenkins to stop with an early initialisation error, > so that the admin knows they've got to go and install the extra d

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

On Tue, Oct 12, 2021 at 10:14 AM Goyot, Martin wrote: > Thanks for your input. I agree with the readResolve but then I'm wondering > about the maintainability of the class. Let's say in a future version I add > another field, and in a next one yet another. My readResolve is going to be > huge and

Re: bitbucket-plugin | update maintainer list

The plugin site shows (with slight delay, caches etc.) maintainer information from the permissions file at https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-bitbucket.yml File a PR to update maintainer information. -- You received this message because

Re: Plugin Maintainer alumni metadata

> On 17. Oct 2021, at 10:15, Oleg Nenashev wrote: > > Just to follow-up on https://groups.google.com/g/jenkinsci-dev/c/e3T6QG24YVg > , I propose adding a new "Alumni" category to > https://github.com/jenkins-infra/repository-permissions-updater to reference > ex maintainers of the plugins.

Re: Plugin Maintainer alumni metadata

> On 17. Oct 2021, at 10:52, Oleg Nenashev wrote: > > GitHub contributor metadata does not list former maintainers specifically, > unless you want to query audit log > Listing all contributors is possible through that and it would be cool > indeed, but it is not a specific use-case for maint

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

> On 17. Oct 2021, at 10:50, Oleg Nenashev wrote: > > I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. > This is a test framework, and it is not exposed to the user ecosystem. Using > GitHub issues would be ore convenient for use-cases, and particularly for > onboar

Re: unable to perform jenkins release through local machine

It should be there. Make sure it's not installed and that you're using Jenkins 2.303.1 or newer. -- 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-

Re: Company plugins in Jenkins org

On Thu, Oct 21, 2021 at 1:47 PM 'jn...@cloudbees.com' via Jenkins Developers wrote: > Additionally to make RPU easier, we are planning to add support for groups > of users so that we would just need to modify a single "group definition > file" to update permissions in artifactory. > Sounds great

Re: Company plugins in Jenkins org

On Thu, Oct 21, 2021 at 3:47 PM Baptiste Mathus wrote: > Care to elaborate what you mean and how that would work? IIUC, what you're > describing would quite entail refactoring all existing "xyz-plugin > developer" groups on GitHub side? > And as you know we currently have close to no notion of gi

Re: Unable to perform Plugin release

Reset your password on accounts.jenkins.io. -- 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 discus

Re: New LTS baseline selection

If you like 2.318 for this, you should wait for 2.319, which will only contain security fixes. -- 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-de

Re: Company plugins in Jenkins org

On Wed, Oct 27, 2021 at 1:18 PM 'jn...@cloudbees.com' via Jenkins Developers wrote: > > I am open to extending irc-bot with a command like `jenkins-admin: invite > user to the organisation` or `jenkins-admin: Make USER a member on TEAM` if > that helps at all. > Would be useful; we've done that

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

On Fri, Nov 12, 2021 at 10:09 PM 'jsupun' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > For the ci.jenkins.io Windows build, for a test I'm getting a failure of > > 14:12:17 java.lang.RuntimeException: java.io.IOException: > java.lang.RuntimeException: Failed to serialize >

Re: Getting 409 Conflict for CD GHA

On Tue, Nov 16, 2021 at 7:35 AM 'jsupun' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Getting closer. When running the cd.yaml I'm getting an error for the > release step. > > [WARNING] The requested profile "consume-incrementals" could not be > activated because it does not e

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

On Wed, Nov 17, 2021 at 12:49 AM Oleg Nenashev wrote: > I think we should eventually drop Java 8 support but only when we have > enough Java 11 adoption About that… https://stats.jenkins.io/plugin-installation-trend/jvms.json seems unlikely given we switched the Docker images around. Even Octo

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

On Wed, Nov 17, 2021 at 10:03 AM Daniel Beck wrote: > > In fact, looking at the difference between > https://stats.jenkins.io/jenkins-stats/svg/total-jenkins.svg and the JVM > stats, we can see they were almost equal (99+%) up to early 2019. And then > around the time https://www.jenkins.io/chang

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

On Thu, Nov 18, 2021 at 10:22 AM 'Björn Pedersen' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > between the java version used to run jenkins and the version used to > really build java projects. I think that could warrant a bit more > epxlanation that you can build projects in

Re: Plugin documentation not showing on site

On Thu, Nov 18, 2021 at 11:48 AM Jean-Marc Meessen < jean-m...@meessen-web.org> wrote: > > I have a README.md in the root of the workspace and the POM's seems > properly configured. Any ideas or explanations? > While changes to README.md are effective quickly (~caching) once that's known to be t

Re: Plugin documentation not showing on site

On Thu, Nov 18, 2021 at 1:13 PM Daniel Beck wrote: > > > On Thu, Nov 18, 2021 at 11:48 AM Jean-Marc Meessen < > jean-m...@meessen-web.org> wrote: > >> >> I have a README.md in the root of the workspace and the POM's seems >> properly configured. Any ideas or explanations? >> > > While changes to

Re: 405 Method Not Allowed - Deploy to staging

The staging procedure is unique to security updates prepared in private. That does not apply here, so none of the instructions related to security fixes should be used. Do a normal release:prepare release:perform as with any other release you create. > On 18. Nov 2021, at 15:48, kudos-dude w

Re: 405 Method Not Allowed - Deploy to staging

On Fri, Nov 19, 2021 at 3:56 PM kudos-dude wrote: > Getting a 401 now. I'm assuming this has something to do with my > `settings.xml` file? > > Does someone have an example one for deploying to Jenkins-CI? > https://www.jenkins.io/doc/developer/publishing/releasing-manually/#artifactory-credenti

Re: 405 Method Not Allowed - Deploy to staging

On Fri, Nov 19, 2021 at 4:45 PM kudos-dude wrote: > I've created my `settings.xml` file based off the article above. It > includes my Jenkins credentials that allows me to sign in to all other > Jenkins related logins (encrypted login/password created via `mvn > --encrypt-password`. > Please try

Simplifying agent-to-controller security

Hi everyone, While it's not yet quite there in terms of JEP process, feedback is already welcome for this JEP and the corresponding core PRs: https://github.com/jenkinsci/jep/pull/381 Abstract: The agent-to-controller security subsystem is greatly simplified: it is always enabled and exceptio

Re: Enabling jenkins-security-scan ?

On Thu, Dec 2, 2021 at 4:11 PM Jean-Marc Meessen wrote: > While checking a reference project (file-parameter-plugin > ) for proper CD > setup, I have seen that the repository is flagged as " > *jenkins-security-scan-enabled*". I understand, but

Re: Unable to release plugin - auth to Artifactory failing, but works with other Jenkins infra

On Thu, Dec 2, 2021 at 4:21 PM David Conneely wrote: > Hi, > > Thanks for the suggestions, but I think it's not just the encryption in > *settings.xml > *as I can't even use the same credentials to log in to Artifactory > (although they work for Jira). > I have also tried using both encrypted an

Re: 405 Method Not Allowed - Deploy to staging

On Fri, Dec 3, 2021 at 10:15 PM kudos-dude wrote: > It looks like I've gotten the release out correctly in JFrog, but the > updated release is still not showing up in the `updates.jenkins.io`. Any > ideas? > Last update was several hours ago, as you can see in the file timestamps. I'm looking in

Re: 405 Method Not Allowed - Deploy to staging

On Sat, Dec 4, 2021 at 12:00 AM kudos-dude wrote: > Still have the security notice on the plugin after the update. How does > that end up removed? > https://www.jenkins.io/security/plugins/#followup -- You received this message because you are subscribed to the Google Groups "Jenkins Develope

Re: Simplifying agent-to-controller security

On Sat, Nov 20, 2021 at 12:03 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > https://github.com/jenkinsci/jep/pull/381 > > Abstract: The agent-to-controller security subsystem is greatly > simplified: it is always enabled and ex

Re: Request to be made a maintainer for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

Repo admins (the default for maintainers now) can add/remove external collaborators (a reason we have so many). Team maintainers can add/remove team members. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group an

Re: how to change log4j-over-slf4j-1.7.31 to 2.15 version

On Tue, Dec 14, 2021 at 1:15 PM Mohammad Jameel Uddin < mohammad.jameelud...@saucelabs.com> wrote: > Yes, they(my organization) requested an update to autonomiq plugin, but it > is not on the list of affected plugins. > > https://issues.jenkins.io/browse/JENKINS-67353?jql=labels%20%3D%20CVE-2021-4

Re: StaplerProxy getTarget

On Wed, Dec 15, 2021 at 1:13 AM Ullrich Hafner wrote: > (Code https://github.com/jenkinsci/warnings-ng-plugin/pull/1145/) > Is this the correct PR? Looking at the plugin, only ResultAction has a getTarget returning an IssuesDetail, and neither is involved in the PR. -- You received this messag

Re: StaplerProxy getTarget

On Wed, Dec 15, 2021 at 12:06 PM Ullrich Hafner wrote: > I found the problem. Seems that during my merge the index.jelly file has > been deleted. > > It would be nice though if Stapler would actually print the thing that is > not found rather than writing just "Not Found“. > Set stapler.trace to

Re: Accessing current path from inside Plugin

On Thu, Dec 16, 2021 at 10:38 AM 'simon' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > how can I access the current request path* from inside a class extending > `hudson.model.Action`? I would like to extend the sidebar link plugin to > add a reference to the url. > https://gi

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

> On 21. Dec 2021, at 21:01, Tim Jacomb wrote: > > I think we should target the LTS after next for dropping Java 8 support. > > That would be: > • Weekly - 2nd February (week after baseline selection for next LTS) > • LTS - approx 7th June (roughly when ths LTS after next will be

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

> On 23. Dec 2021, at 17:49, Basil Crow wrote: > > > Do we expect that a notable subset of users will be unable to switch to > > Java 11 due to platform issues (or perhaps just shitty policies)? > > I do not expect so. Users who are not consuming the Docker image may > trivially install Ope

Re: New Year blogpost for Jenkins

On Fri, Dec 24, 2021 at 3:42 PM Mark Waite wrote: > >- Security fixes and improvements > - 19 security advisories published > > I'm certainly biased here, but our work on agent-to-controller security (both the fixes delivered in early November, as well as JEP-235) is notable in this con

Re: Migrating username & secret password to credentials plugin

> On 8. Jan 2022, at 13:59, 'Réda Housni Alaoui' via Jenkins Developers > wrote: > > Is there a best practice for this kind of data migration? What should I do > with the old field data? Should I automatically create one credentials > instance per legacy username & password in a new readRes

Re: INFRA project issues migration from Jira to Github

On Thu, Jan 13, 2022 at 11:41 AM Ullrich Hafner wrote: > Well, I think it is very important to notify reporters that their issues > have been moved to a new system. > Once, sure, but 500+ times? 🙃 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers

Re: Request to be made a maintainer for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

On Thu, Jan 20, 2022 at 4:51 AM Alberto Bec wrote: > Hi all, I was part of this request to be added to the repo. Konstantin > doesn't see me in the org to give me permissions, turns out I missed the > GitHub invitation email to accept being added to the org. Can that be > resent? Done -- You

Re: bitbucket-plugin - release is not published

The release does not exist in the Maven repo, so it cannot be made available. Release drafter says the release was created from GH actions, but I cannot find the CD run creating it. Timing-wise it should probably be between 42 and 41. Any idea why some runs are attributed to the ghost user? --

Re: Artifactory permissions for components with CD enabled

On Tue, Feb 8, 2022 at 12:01 PM 'jn...@cloudbees.com' via Jenkins Developers wrote: > Hi all, > > A point raised in a permission update for a plugin in RPU is that we are > still granting users permission to Artifactory for deployment of a plugin > that they maintain even if the plugin is using C

Re: bitbucket-plugin - release is not published

On Mon, Feb 7, 2022 at 8:34 PM tzach solomon wrote: > Daniel, you are correct. > I've manually triggered the git actions since I saw it was triggered by > merge. > The trigger was #27 > https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1795360127 > > What have I done wrong? I thought tha

Re: bitbucket-plugin - release is not published

On Tue, Feb 8, 2022 at 1:25 PM tzach solomon wrote: > Thanks Daniel (AGAIN! :) > > Can you please point me out what to read in order to fix these issues? > On what did it fail? > [image: image.png] > > > This checks the "status" of the commit to be released as reported by CI. It looks like if, at

Re: webhook plugin development for multibranchPipelineJob

On Wed, Feb 9, 2022 at 1:07 AM John Patrick wrote: > So I've; > 1) updated parent > 2) updated jenkins.version to 2.289.1 > 3) updated jenkins-test-harness.version to 2.72 > 4) updated junit to 4.13.2 > 5) added/edited some provided dependencies > 6) fixed hamcrest issue > 7) fixed a casting issu

Re: Understanding Jenkins Core Vulnerabilities in plugin s

On Tue, Feb 22, 2022 at 7:25 AM Niv Keidan wrote: > 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? > No, this only defines the minimum compatible version. The same applies to dependencies to other p

Jenkins Security Scan now generally available

Hi everyone, I've published the previously private[1] Jenkins code scanning rules for CodeQL. These are static analysis rules covering mostly Jenkins-specific issues, like unprotected Stapler web methods and use of APIs that are generally not a good idea in the context of Jenkins plugins. While t

Re: Jenkins Security Scan now generally available

On Tue, Feb 22, 2022 at 6:59 PM 'Jesse Glick' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Do we generally recommend this for any plugin? If so, it would be great to > add this to `archetypes`. > > That's where I think we should end up, but I'd like to get some more scan quali

Re: Jenkins Security Scan now generally available

On Tue, Feb 22, 2022 at 10:17 PM 'Jesse Glick' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I suppose any results would appear in `/security/code-scanning` to repo > admins only? > PR-specific results are shown directly and publicly in the PR. GitHub compares results from the

Re: Jenkins Security Scan now generally available

On Wed, Feb 23, 2022 at 9:29 PM Basil Crow wrote: > > curl: (22) The requested URL returned error: 403 > Failed to upload results > Error: Process completed with exit code 1. > Interesting. It probably happens because it's a PR from a fork and the GITHUB_TOKEN used only has read permission for S

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 cannot because it use

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 https://github.com/jenkinsci/.github/blob/011201ac97f9e2757cca0415590952eaee704e5b/workflow-templates/jenkins-security-scan.yaml

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/issues/3 > I've updated

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 th

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: https

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 o

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

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

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 s

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 Googl

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" group

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 publish-as

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 a

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: 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 t

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 sou

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: 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 th

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 un

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: 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 yo

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: 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 t

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: 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: 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 > https://github.c

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 https://www.jenkins.io/doc/developer/publishi

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 fres

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 n

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

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 ' > https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ws-c

Re: TransientActionFactory question

The run is null, so there's nothing to get a sidepanel from. The RunAction2 special behavior isn't supported by TransientActionFactory, so you need to add a constructor argument to end up with a reference to the Run. Could be as designed based on the RunAction2 Javadoc. The problem it solves is on

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 the

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 h

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 out-of-

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 s

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: 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 trademar

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: 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: 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 received

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 sto

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 ove

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 to

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

  1   2   >