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

Parameterised build won't save parameter description for "built-in" parameter types

      The description for parameter types such as boolean and string won't save when edited. Editing of the description for an extended choice parameter works fine.
      This behaviour works in v1.523 so it's a recent problem, possibly related to JENKINS-22628 Change comments/description to use String.format() instead

      I'm wondering if this is also the root cause for JENKINS-23026.

      For me this is blocking the roll-out of this version to resolve an issue with AD authentication so although its minor, its really getting in the way.

      The work-around is to edit descriptions in the job config.xml and reload the Jenkins configuration from disk.

          [JENKINS-23300] Parameterised build won't save parameter description for "built-in" parameter types

          Chris Tutty created issue -
          Chris Tutty made changes -
          Description Original: The description for parameter types such as boolean and string won't saved when edited. Editing of the description for an exetended choice parameter works. New: The description for parameter types such as boolean and string won't saved when edited. Editing of the description for an exetended choice parameter works.
          This behaviour works in v1.523 so is recent, possibly related to

          I'm wondering if this is related to JENKINS-23026
          Chris Tutty made changes -
          Description Original: The description for parameter types such as boolean and string won't saved when edited. Editing of the description for an exetended choice parameter works.
          This behaviour works in v1.523 so is recent, possibly related to

          I'm wondering if this is related to JENKINS-23026
          New: The description for parameter types such as boolean and string won't saved when edited. Editing of the description for an exetended choice parameter works.
          This behaviour works in v1.523 so it's a recent problem, possibly related to JENKINS-22628 Change comments/description to use String.format() instead

          I'm wondering if this is also the root cause for JENKINS-23026
          Chris Tutty made changes -
          Description Original: The description for parameter types such as boolean and string won't saved when edited. Editing of the description for an exetended choice parameter works.
          This behaviour works in v1.523 so it's a recent problem, possibly related to JENKINS-22628 Change comments/description to use String.format() instead

          I'm wondering if this is also the root cause for JENKINS-23026
          New: The description for parameter types such as boolean and string won't saved when edited. Editing of the description for an extended choice parameter works fine.
          This behaviour works in v1.523 so it's a recent problem, possibly related to JENKINS-22628 Change comments/description to use String.format() instead

          I'm wondering if this is also the root cause for JENKINS-23026.

          For me this is blocking the roll-out of this version to resolve an issue with AD authentication, so it's really getting in the way.
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Chris Tutty made changes -
          Description Original: The description for parameter types such as boolean and string won't saved when edited. Editing of the description for an extended choice parameter works fine.
          This behaviour works in v1.523 so it's a recent problem, possibly related to JENKINS-22628 Change comments/description to use String.format() instead

          I'm wondering if this is also the root cause for JENKINS-23026.

          For me this is blocking the roll-out of this version to resolve an issue with AD authentication, so it's really getting in the way.
          New: The description for parameter types such as boolean and string won't save when edited. Editing of the description for an extended choice parameter works fine.
          This behaviour works in v1.523 so it's a recent problem, possibly related to JENKINS-22628 Change comments/description to use String.format() instead

          I'm wondering if this is also the root cause for JENKINS-23026.

          For me this is blocking the roll-out of this version to resolve an issue with AD authentication so although its minor, its really getting in the way.

          The work-around is to edit descriptions in the job config.xml and reload the Jenkins configuration from disk.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 155865 ] New: JNJira + In-Review [ 179150 ]

            Unassigned Unassigned
            christutty Chris Tutty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: