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

Error message of missing credentials entry not meaningful to end user

XMLWordPrintable

      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

          [JENKINS-49535] Error message of missing credentials entry not meaningful to end user

          Benjamin Heilbrunn created issue -
          Benjamin Heilbrunn made changes -
          Description Original: 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]           		New: 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]
          Jesse Glick made changes -
          Assignee Original: Jesse Glick [ jglick ] New: Benjamin Heilbrunn [ benhei ]
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-45378 [ JENKINS-45378 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "Page (Jenkins Wiki)" [ 20281 ]
          Jesse Glick made changes -
          Remote Link Original: This issue links to "Page (Jenkins Wiki)" [ 20281 ] New: This issue links to "Page (Jenkins Wiki)" [ 20281 ]

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

              Created:
              Updated:
              Resolved: