If exceptions occur in a stage, Jenkins Blue Ocean will only show the exception message in the log. Additional context via the stacktrace is only available if users explicitly switch back to the "old" log viewer.

Given this behavior, in case of missing credentials, the behavior of the credentials binding plugin is problematic. If it fails, it only provides the credentials ID as output via the CredentialNotFoundException message. This makes it hard for Blue Ocean users to get a grasp of the problem.

See: SCREENSHOT

We created a PR that would fix the issue. A review is appreciated.

https://github.com/jenkinsci/credentials-binding-plugin/pull/48