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

Plug-ins should define their credential type. This type should be pre-selected.

XMLWordPrintable

      When adding credentials to any of the plug-ins, the Credential Type dropdown box has some random, nonsense credential type pre-selected.

      So you always have to look-up the correct credential type for each of the plug-ins every time before being able to accomplish your task. This is a true, repeating niusance.

      Hence, I propose that ...

      1. plug-ins define their preferred credential type, and
      2. Jenkins is going to pre-select this type, read from the corresponding plug-in's properties, in the Credential Type dropdown box when adding a new credential to the plug-in.

      This will dramatically ease setting up credentials in Jenkins.

          [JENKINS-52291] Plug-ins should define their credential type. This type should be pre-selected.

          A. D. created issue -
          Oleg Nenashev made changes -
          Component/s New: credentials-plugin [ 16523 ]
          Component/s Original: plugin-proposals [ 15491 ]
          Oleg Nenashev made changes -
          Assignee New: Stephen Connolly [ stephenconnolly ]

          Oleg Nenashev added a comment -

          Looks like an RFE for Credentials API

          Oleg Nenashev added a comment - Looks like an RFE for Credentials API

          Stephen Connolly added a comment -

          Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA
          Stephen Connolly made changes -
          Assignee Original: Stephen Connolly [ stephenconnolly ]

            Unassigned Unassigned
            settrend A. D.
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: