Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49535

Error message of missing credentials entry not meaningful to end user

    Details

    • Similar Issues:

      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

            Activity

            Hide
            jglick Jesse Glick added a comment -

            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.

            Show
            jglick Jesse Glick added a comment - 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.

              People

              • Assignee:
                benhei Benjamin Heilbrunn
                Reporter:
                benhei Benjamin Heilbrunn
              • Votes:
                5 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: