The markup for a Pipeline's input step is rendered inconsistently depending on the UI. They're all bad in their own ways. It makes it hard to build good experiences for users.

      Here, you can see discrepencies between: how the message is formatted. Should it be plaintext or HTML? Similiarly for text area inputs, shouldn't it use textareas everywhere?

      Here's a sample Pipeline Job:

      def message = "Hello!"
      def stackProperties = [
        app_name: "asdf",
        app_version: "1234" 
      ]
      
      stage("Hello") {
        input(
          message: message + "\n\nWrite a short description of the release notes (think customer facing). Supports slack formatting",
          parameters: [text(name: 'deploy-notes', defaultValue: """Deploying
      ${stackProperties.app_name}@${stackProperties.app_version}
      *Changes*:
      -
      
      *Impact*:
      - none""")],
          submitterParameter: 'PASSES_QA_APPROVER'
        )
      }

      I've attached some screenshots of the three places where I see inputs:

      • Pipeline Overview
      • Job's Input Page
      • Job's Blue Ocean Input Page

       

       

          [JENKINS-47418] Pipeline input visual inconsistency

          James Dumay added a comment -

          rymndhng thanks for the report. This is a duplicate of JENKINS-45251.

          James Dumay added a comment - rymndhng thanks for the report. This is a duplicate of JENKINS-45251 .

            Unassigned Unassigned
            rymndhng Ray H
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: