A user of the pipeline should be able to set, at a pipeline level, what parameters are required.

      This is configuring the inputs as can be seen in parametrised jobs (so you can refer to the design for parametrised jobs if it helps, for the types of fields configurable).

      In scope:

      • User can set what fields are required and their type
      • Design should also work when configuring "input" step type (even if input configuration is not implemented initially, as it is the same logic).

          [JENKINS-41971] Support for parameters in editor

          Michael Neale created issue -
          Michael Neale made changes -
          Epic Link New: JENKINS-35755 [ 171716 ]

          Michael Neale added a comment -

          kzantow not sure what is known via metadata/model about job property types - is there anything in it?

          Michael Neale added a comment - kzantow not sure what is known via metadata/model about job property types - is there anything in it?
          Michael Neale made changes -
          Link New: This issue relates to JENKINS-41970 [ JENKINS-41970 ]
          James Dumay made changes -
          Epic Link Original: JENKINS-35755 [ 171716 ] New: JENKINS-36291 [ 172300 ]
          James Dumay made changes -
          Sprint New: post-release [ 181 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          James Dumay made changes -
          Sprint Original: post-release [ 181 ] New: up next [ 171 ]
          James Dumay made changes -
          Rank New: Ranked lower

            jamesdumay James Dumay
            michaelneale Michael Neale
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: