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

credentials() parameter does not support HTML in description

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: credentials-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.121.1
      Pipeline Model Definition Plugin 1.3.1
      Credentials Plugin 2.1.17
    • Similar Issues:

      Description

      Hi,

      We have a declarative Pipeline definition cfr.

      def xra31_user_password_credentials_defaultValue = ''
      def xra31_user_password_credentials_description = '''Default password for the <em>xra31</em> user.
      <br />An appropriate password is selected by default (when "<em>- none -</em>" is selected).
      <br />Please choose the appropriate password for the <tt>XRA31_IMAGE_TYPE</tt>.
      <br />Especially <em>development</em> vs. <em>non-development</em> system.'''
      
      pipeline {
          parameters {
              credentials(name: 'XRA31_USER_CREDENTIALS',
                          credentialType: 'com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl',
                          defaultValue: xra31_user_password_credentials_defaultValue,
                          description: xra31_user_password_credentials_description,
                          required: false)
          }
      }

      When building this project ("Build with Parameters"), we don't see any HTML markup.

      See screenshot:

        Attachments

          Activity

          Hide
          stephenconnolly 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

          Show
          stephenconnolly 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

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            tom_ghyselinck Tom Ghyselinck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: