Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
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
Attachments
Issue Links
- is duplicated by
-
-
- Resolved
-
- mentioned in
-
Page Loading...
Activity
Benjamin Heilbrunn
created issue -
Benjamin Heilbrunn
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
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: [https://user-images.githubusercontent.com/916316/35906147-cd18d0e2-0be9-11e8-95f8-17eae02c54ea.png|http://example.com/] We created a PR that would fix the issue. A review is appreciated. [https://github.com/jenkinsci/credentials-binding-plugin/pull/48] |
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|https://user-images.githubusercontent.com/916316/35906147-cd18d0e2-0be9-11e8-95f8-17eae02c54ea.png] We created a PR that would fix the issue. A review is appreciated. [https://github.com/jenkinsci/credentials-binding-plugin/pull/48] |
| Assignee | Jesse Glick [ jglick ] | Benjamin Heilbrunn [ benhei ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Link |
This issue is duplicated by |
| Remote Link | This issue links to "Page (Jenkins Wiki)" [ 20281 ] |
| Remote Link | This issue links to "Page (Jenkins Wiki)" [ 20281 ] | This issue links to "Page (Jenkins Wiki)" [ 20281 ] |