I've pushed the backport for fixing this build error. For those curious: the problem was the "recordIssues" build step requires a Jenkins agent to execute, and I had configured the pipeline not to use on at the root level. The mail and slackSend steps are both node-less steps (i.e., they're basically Jenkins plugins executing via the Jenkins master), and those would have otherwise worked fine in the existing Jenkinsfile. In declarative pipeline syntax, nodes are referenced through the "agent" directive.
And in case the Jenkins nomenclature is confusing, a node and an agent/slave are all effectively the same thing; node is a superset term that includes the Jenkins master when it has executors enabled (an insecure configuration setting in shared Jenkins masters). On Sun, 12 Apr 2020 at 12:46, Apache Jenkins Server <jenk...@builds.apache.org> wrote: > > > There is a build failure in log4j/release-2.x. > > Build: https://builds.apache.org/job/log4j/job/release-2.x/14/ > Logs: https://builds.apache.org/job/log4j/job/release-2.x/14/console > Changes: https://builds.apache.org/job/log4j/job/release-2.x/14/changes > > -- > Mr. Jenkins -- Matt Sicker <boa...@gmail.com>