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

Jenkins auto linkification for Bugzilla is broken on the build page

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • bugzilla-plugin
    • Jenkins ver. 2.7.3

      On the job's main page, Recent Changes correctly link to Bugzilla bugs. However, if we go to specific builds' Recent Changes, links are broken.

      On a build's page, something like the following is shown
      <a href='https://bugzilla/.../?id=1234'>Bug 1234</a> - $COMMIT_MESSAGE

      which should have been like $LINK_TO_BUG1234 $COMMIT_MESSAGE

      From the page's source, it looks like all leading angled brackets are missing from the beginning of the Bugzilla URL's. For example

      &lt;a href='https://bugzilla/.../?id=1234'>Bug 1234&lt;/a>&lt;br>$COMMIT_MESSAGE

          [JENKINS-38581] Jenkins auto linkification for Bugzilla is broken on the build page

          mdonohue added a comment -

          I tested just now with the 'ocaml' repo: http://caml.inria.fr/svn/ocaml/trunk
          The hyperlinks work fine from both the main page and the specific build page, so I am not able to reproduce. Can you provide more details? Or do you have a public repo that reproduces this?

          mdonohue added a comment - I tested just now with the 'ocaml' repo: http://caml.inria.fr/svn/ocaml/trunk The hyperlinks work fine from both the main page and the specific build page, so I am not able to reproduce. Can you provide more details? Or do you have a public repo that reproduces this?

          Darya A.Z. added a comment -

          Thanks @mdonohue for your comment.

          Attached is the screenshot of what we see in our Jenkins. Please note that <br> is missing at the beginning where the hyperlink should have been create (at least this is what we think is causing the issue).

          <a href='https://bugzilla/.../?id=1234'>Bug 1234</a><br>$COMMIT_MESSAGE

          Please let me know if you need more info.

          Thanks

          Darya A.Z. added a comment - Thanks @mdonohue for your comment. Attached is the screenshot of what we see in our Jenkins. Please note that <br> is missing at the beginning where the hyperlink should have been create (at least this is what we think is causing the issue). <a href='https://bugzilla/.../?id=1234'>Bug 1234</a><br>$COMMIT_MESSAGE Please let me know if you need more info. Thanks

          mdonohue added a comment -

          What plugin is causing those 'fisheye' links? I think another plugin is processing the text and changing the angle brackets.

          mdonohue added a comment - What plugin is causing those 'fisheye' links? I think another plugin is processing the text and changing the angle brackets.

          mdonohue added a comment -

          Ok, the git plugin provides 'fisheye' links. I tried a Git repo, with fisheye enabled. Still can't repro your problem. Are you able to make a test install of Jenkins with just the git + bugzilla plugins, and reproduce this problem? I think it's some other plugin interacting.

          mdonohue added a comment - Ok, the git plugin provides 'fisheye' links. I tried a Git repo, with fisheye enabled. Still can't repro your problem. Are you able to make a test install of Jenkins with just the git + bugzilla plugins, and reproduce this problem? I think it's some other plugin interacting.

          Darya A.Z. added a comment -

          We're using Subversion Plug-in version 2.6

          Darya A.Z. added a comment - We're using Subversion Plug-in version 2.6

          mdonohue added a comment -

          I am still not able to reproduce with the subversion plugin, alongside Fisheye integration. It's very difficult to guess what the root cause is without a way to reproduce the problem. Can you try building a test Jenkins setup, and add one plugin at a time, until the problem reproduces there?

          mdonohue added a comment - I am still not able to reproduce with the subversion plugin, alongside Fisheye integration. It's very difficult to guess what the root cause is without a way to reproduce the problem. Can you try building a test Jenkins setup, and add one plugin at a time, until the problem reproduces there?

          Darya A.Z. added a comment -

          Our Jenkins instance is very large with many plugins installed, it is impossible for us to install the plugins one by one and narrow this down. I tried to downgrade the subversion plugin to see if anything would change but the downgrade broke a few other plugins and I had to quickly revert back and install the latest version of subversion plugin. If it helps, I can provide you with the list of our plugins.

          Darya A.Z. added a comment - Our Jenkins instance is very large with many plugins installed, it is impossible for us to install the plugins one by one and narrow this down. I tried to downgrade the subversion plugin to see if anything would change but the downgrade broke a few other plugins and I had to quickly revert back and install the latest version of subversion plugin. If it helps, I can provide you with the list of our plugins.

          mdonohue added a comment -

          Sorry, I'm volunteering here - you'll need to do the legwork to get this one fixed. it's almost certainly not the bugzilla plugin at fault.

          mdonohue added a comment - Sorry, I'm volunteering here - you'll need to do the legwork to get this one fixed. it's almost certainly not the bugzilla plugin at fault.

            mdonohue mdonohue
            daryaa Darya A.Z.
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: