[JIRA] (JENKINS-61912) Clicking failure cause link on build page does not highlight location in console output

9 views
Skip to first unread message

mdealer@gmail.com (JIRA)

unread,
Apr 15, 2020, 6:32:03 AM4/15/20
to jenkinsc...@googlegroups.com
Edgars Batna created an issue
 
Jenkins / Bug JENKINS-61912
Clicking failure cause link on build page does not highlight location in console output
Issue Type: Bug Bug
Assignee: Tomas Westling
Components: build-failure-analyzer-plugin
Created: 2020-04-15 10:31
Environment: Jenkins 2.230
Build Failure Analyzer 1.25.1
latest other plugins
Labels: regression multi-branch jenkinsfile
Priority: Major Major
Reporter: Edgars Batna

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.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

mdealer@gmail.com (JIRA)

unread,
Apr 15, 2020, 6:33:03 AM4/15/20
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
Change By: Edgars Batna
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.

mdealer@gmail.com (JIRA)

unread,
Apr 15, 2020, 6:35:03 AM4/15/20
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
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 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.

mdealer@gmail.com (JIRA)

unread,
Apr 15, 2020, 6:36:02 AM4/15/20
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
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.

dbeck@cloudbees.com (JIRA)

unread,
Apr 21, 2020, 7:04:03 PM4/21/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages