Devin Nusbaum

For what it's worth, I just fixed [JENKINS-69006](https://issues.jenkins.io/browse/JENKINS-69006) in `display-url-api` 2.3.9, and I added a global configuration page to configure a default provider as well ([JENKINS-43205](https://issues.jenkins.io/browse/JENKINS-43205)) so that users don't...

This doesn't make sense to me. In https://github.com/jenkinsci/warnings-ng-plugin/pull/1599 you added `addParser` and `deleteParser` methods which in combination have effectively the same behavior as `setParsers`, so why would we only blacklist...

> Can we not just delete (or deprecate) NodeDownstreamBuildAction and change whatever code is calling is to look up org.jenkinsci.plugins.workflow.support.steps.build.DownstreamBuildAction on demand? Yes I considered this kind of approach, but...

Oh, and I'm not sure if you can just change the code that looks for the action in the special Blue Ocean `FlowNodeWrapper` class in `PipelineNodeImpl`. I think you need...

See https://github.com/jenkinsci/blueocean-plugin/pull/2540/commits/b7ef6079aa57050d441d2fd9097a7b5e4d0f1970 for an approach that moves the logic to graph processing time. Delaying build loading until a user actually clicks on one of the relevant links does not seem...

@nfalco79 Thanks for splitting this into a separate PR! For other reviewers, here is an earlier discussion about this change: https://github.com/jenkinsci/branch-api-plugin/pull/160#discussion_r418672697.

> It does not work since neither jelly section neither jelly block supports help/description attribute True, but you can add a help link manually using ``. Adding it to the...

Thanks for the PR @witokondoria! We try to track nontrivial changes through Jira issues, so would you be able to open an issue on https://issues.jenkins-ci.org/secure/Dashboard.jspa with component `durable-task`, and more...

The CI failure is because `BourneShellScriptTest.runOnUbuntuDocker` timed out on the JDK 8 build on Linux. Perhaps just a flaky test.

FWIW I was a little concerned that shebang lines like `#!/usr/bin/env python3` might break with this, but I tested it and they work fine before and after.