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

Clicking failure cause link on build page does not highlight location in console output

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I'm using multibranch pipelines. I've set up a few global failure causes and they are indeed shown on the build page as needed. But, clicking the failure link just shows the console output, not the exact location inside the output.

      I remember using this plugin extensively in freestyle projects few years ago and clicking the links always opened the exact location in the console output, so this must be a regression.

      The "regression" is not new and has always been happening with multibranch pipelines for us (since 2017). I assumed it will get fixed eventually, but so far I can't even find a similar issue.

      I don't see any exceptions in the analyzer log.

      The plugin is kinda pointless for us, if it doesn't show the location in the log.

        Attachments

          Activity

          gl1koz3 Edgars Batna created issue -
          gl1koz3 Edgars Batna made changes -
          Field Original Value New Value
          Description I'm using multibranch pipelines. I've set up a few global failure causes and they are indeed shown on the build page as needed. But, clicking the failure link just shows the console output, not the exact location inside the output.

          I remember using this plugin extensively in freestyle projects few years ago and clicking the links always opened the exact location in the console output, so this must be a regression. This has always been happening with multibranch pipelines for us (since 2017), I assumed it will get fixed eventually, but so far I can't even find a similar issue.

          I don't see any exceptions in the analyzer log.
          I'm using multibranch pipelines. I've set up a few global failure causes and they are indeed shown on the build page as needed. But, clicking the failure link just shows the console output, not the exact location inside the output.

          I remember using this plugin extensively in freestyle projects few years ago and clicking the links always opened the exact location in the console output, so this must be a regression. This has always been happening with multibranch pipelines for us (since 2017), I assumed it will get fixed eventually, but so far I can't even find a similar issue.

          I don't see any exceptions in the analyzer log.

          The plugin is kinda pointless for us, if it doesn't show the location in the log.
          gl1koz3 Edgars Batna made changes -
          Description I'm using multibranch pipelines. I've set up a few global failure causes and they are indeed shown on the build page as needed. But, clicking the failure link just shows the console output, not the exact location inside the output.

          I remember using this plugin extensively in freestyle projects few years ago and clicking the links always opened the exact location in the console output, so this must be a regression. This has always been happening with multibranch pipelines for us (since 2017), I assumed it will get fixed eventually, but so far I can't even find a similar issue.

          I don't see any exceptions in the analyzer log.

          The plugin is kinda pointless for us, if it doesn't show the location in the log.
          I'm using multibranch pipelines. I've set up a few global failure causes and they are indeed shown on the build page as needed. But, clicking the failure link just shows the console output, not the exact location inside the output.

          I remember using this plugin extensively in freestyle projects few years ago and clicking the links always opened the exact location in the console output, so this must be a regression. The "regression" is not new and has always been happening with multibranch pipelines for us (since 2017). I assumed it will get fixed eventually, but so far I can't even find a similar issue.

          I don't see any exceptions in the analyzer log.

          The plugin is kinda pointless for us, if it doesn't show the location in the log.
          gl1koz3 Edgars Batna made changes -
          Description I'm using multibranch pipelines. I've set up a few global failure causes and they are indeed shown on the build page as needed. But, clicking the failure link just shows the console output, not the exact location inside the output.

          I remember using this plugin extensively in freestyle projects few years ago and clicking the links always opened the exact location in the console output, so this must be a regression. The "regression" is not new and has always been happening with multibranch pipelines for us (since 2017). I assumed it will get fixed eventually, but so far I can't even find a similar issue.

          I don't see any exceptions in the analyzer log.

          The plugin is kinda pointless for us, if it doesn't show the location in the log.
          I'm using multibranch pipelines. I've set up a few global failure causes and they are indeed shown on the build page as needed. But, clicking the failure link just shows the console output, not the exact location inside the output.

          I remember using this plugin extensively in freestyle projects few years ago and clicking the links always opened the exact location in the console output, so this must be a regression.

          The "regression" is not new and has always been happening with multibranch pipelines for us (since 2017). I assumed it will get fixed eventually, but so far I can't even find a similar issue.

          I don't see any exceptions in the analyzer log.

          The plugin is kinda pointless for us, if it doesn't show the location in the log.
          danielbeck Daniel Beck made changes -
          Labels jenkinsfile multi-branch regression jenkinsfile multi-branch

            People

            Assignee:
            t_westling Tomas Westling
            Reporter:
            gl1koz3 Edgars Batna
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: