I'm using this plugin along with Describe With Params plugin in my build configuration to add the generated Build ID to the build description. After Describe With Params plugin, that runs as build step, is executed everything is shown correctly.

      However, after this plugin is executed as post-build step, there is an extra <br /> added in front of the description that is generated by the plugin.

          [JENKINS-72555] <br /> is shown before description

          Mark Waite added a comment -

          Thanks for reporting the issue. You can avoid the issue by downgrading to the 1.10 release. That extra tag was added many years ago on the master branch but was only released yesterday. I hope to resolve the issue with a new release reasonably soon.

          Mark Waite added a comment - Thanks for reporting the issue. You can avoid the issue by downgrading to the 1.10 release. That extra tag was added many years ago on the master branch but was only released yesterday. I hope to resolve the issue with a new release reasonably soon.

          Mark Waite added a comment -

          I'm having difficulty duplicating the issue as described. Steps that I took while trying to duplicate the problem as described:

          1. Run Jenkins 2.401.3 with description setter plugin, markdown plugin, OWASP formatter plugin
          2. Configure a freestyle job that takes a single parameter named "ONE_LETTER", enable the described with params plugin, add a shell step that performs "echo Modified build ID is mod-$BUILD_ID" and configure the description setter to match that message and include the "mod-$BUILD_ID" value as the description, with the setter configure to append the additional description
          3. Run the job and see the first result, where describe with param and the description setter both output a visible 'br' tag like this:
          4. Configure Jenkins with the safe HTML formatter and run the job again. Then no tag is visible but a line break is inserted due to the trailing '<br>' in the Describe with params plugin. It looks like this:
          5. Configure Jenkins with the markdown formatter and run the job again. Then the tags are visible for describe with params and for description setter. It looks like this:

          Can you describe your configuration in more detail so that the issue can be duplicated?

          Mark Waite added a comment - I'm having difficulty duplicating the issue as described. Steps that I took while trying to duplicate the problem as described: Run Jenkins 2.401.3 with description setter plugin, markdown plugin, OWASP formatter plugin Configure a freestyle job that takes a single parameter named "ONE_LETTER", enable the described with params plugin, add a shell step that performs "echo Modified build ID is mod-$BUILD_ID" and configure the description setter to match that message and include the "mod-$BUILD_ID" value as the description, with the setter configure to append the additional description Run the job and see the first result, where describe with param and the description setter both output a visible 'br' tag like this: Configure Jenkins with the safe HTML formatter and run the job again. Then no tag is visible but a line break is inserted due to the trailing '<br>' in the Describe with params plugin. It looks like this: Configure Jenkins with the markdown formatter and run the job again. Then the tags are visible for describe with params and for description setter. It looks like this: Can you describe your configuration in more detail so that the issue can be duplicated?

          Michael added a comment - - edited

          I just checked, and we are running Jenkins 2.414.3, and we had markup formatter configured as Plain Text. My original screenshots were done with release 1.10 of the plugin. Describe With Params plugin was configured to use blank for line terminator as recommended for Plain Text markup formatter.

          Michael added a comment - - edited I just checked, and we are running Jenkins 2.414.3, and we had markup formatter configured as Plain Text. My original screenshots were done with release 1.10 of the plugin. Describe With Params plugin was configured to use blank for line terminator as recommended for Plain Text markup formatter.

          Mark Waite added a comment -

          If markup formatter is configured as plain text, then the most recent release of the plugin will resolve the issue. When https://github.com/jenkinsci/description-setter-plugin/releases/tag/239.vd0a_6b_785f92d sees plain text markup formatter, it uses a space character instead of the br HTML tag.

          Mark Waite added a comment - If markup formatter is configured as plain text, then the most recent release of the plugin will resolve the issue. When https://github.com/jenkinsci/description-setter-plugin/releases/tag/239.vd0a_6b_785f92d sees plain text markup formatter, it uses a space character instead of the br HTML tag.

          Michael added a comment -

          markewaite, thank you very much for a quick response and prompt resolution of this issue!

          Michael added a comment - markewaite , thank you very much for a quick response and prompt resolution of this issue!

            huybrechts huybrechts
            mgorovoy Michael
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: