Jim Klimov

Regarding integration with GUI, you can look at my recent PR #5764 as an example that added a field to individual build agent configuration, in the onDemand area. I suspect...

FWIW, I saw this warning "a2x: WARNING: --destination-dir option is only applicable to HTML based outputs" while building NUT (https://github.com/networkupstools/nut/pull/281) and tried to clean up the makefiles so the error...

Makes sense. Just in case for posterity, we linked to this issue from NUT makefiles so we don't try to make things pretty (no warnings) but not working (generation into...

In our use-case, there are a lot of stack traces (probably the majority of what the jenkins instance logs) while there is no credential set up AND the "Manage hooks"...

Help would be welcome :( Despite a number of guesswork iterations, this fix fails on `org.jenkinsci.plugins.github.admin.GitHubHookRegisterProblemMonitorTest.shouldReportAboutHookProblemOnUnregister()` and `...OnRegister()` tests. By the logic, there should be no registered failure if the...

As somewhat usual, I spent a lot more effort fighting self-tests than adding the actual feature. Sigh. ;)

After applying the custom build of plugin and restarting our master, I do not see the log noise anymore. Would be nice if someone could check that the resulting plugin...

Sorry I fell out of the loop, hope to get back to that soon. Or feel free to follow up with PRing wanted cleanups on top of that :)

I'm not with computers for a month, so hope to check by October :) Jim On Sat, Aug 14, 2021, 17:05 Oleg Nenashev ***@***.***> wrote: > Is it still relevant...

Looking at the merge conflicts, it seems that #225 introduced a `repoWithWebhookAccess()` in src/main/java/org/jenkinsci/plugins/github/webhook/WebhookManager.java with similar effect. I don't think I've been running vanilla master versions of the plugin lately,...