Token expansion fails when workspace is not available

If the workspace of a job is not available, task name token expansion fails since the token macro plugin is trying to get the workspace of the node where the build was performed. If the workspace or node is not available, token expansion fails which causes a TokenMacroException. A log message will be emitted and TokenUtils returns an empty string. If your view contains a lot of tasks / pipelines the Jenkins log will be flooded. See https://github.com/Diabol/delivery-pipeline-plugin/blob/master/src/main/java/se/diabol/jenkins/pipeline/token/TokenUtils.java#L51.

This causes the configured task names not to be shown in the delivery pipeline view (even if no expandable variables exist), which makes the task names default to the job name.

Workaround is to downgrade token-macro plugin to 1.x of 1.9 or later.