[JIRA] (JENKINS-49535) Error message of missing credentials entry not meaningful to end user
Title: Message Title Jesse Glick assigned an issue to Benjamin Heilbrunn Jenkins / JENKINS-49535 Error message of missing credentials entry not meaningful to end user Change By: Jesse Glick Assignee: Jesse Glick Benjamin Heilbrunn Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49535) Error message of missing credentials entry not meaningful to end user
Title: Message Title Jesse Glick resolved as Fixed Not really sure why it did not just use AbortException to begin with but I fear there may now be scripts which explicitly catch the CredentialNotFoundException type. Jenkins / JENKINS-49535 Error message of missing credentials entry not meaningful to end user Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-49535) Error message of missing credentials entry not meaningful to end user
Title: Message Title Benjamin Heilbrunn updated an issue Jenkins / JENKINS-49535 Error message of missing credentials entry not meaningful to end user Change By: Benjamin Heilbrunn 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 |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] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49535) Error message of missing credentials entry not meaningful to end user
Title: Message Title Benjamin Heilbrunn created an issue Jenkins / JENKINS-49535 Error message of missing credentials entry not meaningful to end user Issue Type: Improvement Assignee: Jesse Glick Components: credentials-binding-plugin Created: 2018-02-13 17:40 Priority: Minor Reporter: Benjamin Heilbrunn 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 We created a PR that would fix the issue. A review is appreciated. https://github.com/jenkinsci/credentials-binding-plugin/pull/48 Add Comment
