[JIRA] (JENKINS-58634) Custom ID cause broken link in job view

[jochen.steinmann2@de.bosch.com (JIRA)]

Jochen Steinmann created an issue

Jenkins / JENKINS-58634 Custom ID cause broken link in job view Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-07-24 09:46 Labels: jenkins Priority: Minor Reporter: Jochen Steinmann If recordIssues is called with a custom id, the job view link is broken and leads to HTTP ERROR 404. For example: The URL behind the Link is generated like: https://Jenkins/job/BBB/job/test/job/master/1000 but should be https://Jenkins/job/BBB/job/test/job/master/45/1000 where 45 is in my example HEAD of the job list. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-58634

Re: Custom ID cause broken link in job view Actually the link is correct. It should just not create a 404, it should navigate to the latest results of the tool with ID 1000.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner edited a comment on JENKINS-58634

Re: Custom ID cause broken link in job view

Actually the link is correct. It should just not create a 404, it should navigate to the latest results of the tool with ID {{1000}}. See https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/master/pmd as a working example.

Add Comment

[jochen.steinmann2@de.bosch.com (JIRA)]

Jochen Steinmann updated an issue

Jenkins / JENKINS-58634

Custom ID cause broken link in job view

Change By: Jochen Steinmann If recordIssues is called with a custom id, e.g{{ }} {{recordIssues aggregatingResults: true, tools: [clangTidy(id: '1000', name: 'Clang-Tidy: Aggregated Results', pattern: 'build/**/clang-tidy.txt')]}},

the job view link is broken and leads to HTTP ERROR 404. For example: The URL behind the Link is generated like:

{{ [ https://Jenkins/job/BBB/job/test/job/master/1000 |https://jenkins/job/BBB/job/test/job/master/1000] }} but should be [https://Jenkins/job/BBB/job/test/job/master/45/1000|https://jenkins/job/BBB/job/test/job/master/45/1000]

where 45 is in my example HEAD of the job list.

Add Comment

[jochen.steinmann2@de.bosch.com (JIRA)]

[jochen.steinmann2@de.bosch.com (JIRA)]

Jochen Steinmann commented on JENKINS-58634

Re: Custom ID cause broken link in job view If I use the build-in ID everything works fine, as soon I add id:'1000' it don't working: recordIssues aggregatingResults: true, tools: [clangTidy(name: 'Clang-Tidy: Aggregated Results', pattern: 'build/**/clang-tidy.txt')] don't

recordIssues aggregatingResults: true, tools: [clangTidy(id: '1000', name: 'Clang-Tidy: Aggregated Results', pattern: 'build/**/clang-tidy.txt')]

Add Comment

[jochen.steinmann2@de.bosch.com (JIRA)]

Jochen Steinmann edited a comment on JENKINS-58634

Re: Custom ID cause broken link in job view

Is your working in example called with custom id . ?

Add Comment

[jochen.steinmann2@de.bosch.com (JIRA)]

Jochen Steinmann commented on JENKINS-58634

Re: Custom ID cause broken link in job view Is your working in example called with custom id.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-58634

Re: Custom ID cause broken link in job view

No, that is why it is working

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-58634

Custom ID cause broken link in job view

Change By: Ulli Hafner

If recordIssues is called with a custom id, e.g

recordIssues aggregatingResults: true, tools: [clangTidy(id: '1000', name: 'Clang-Tidy: Aggregated Results', pattern: 'build/**/clang-tidy.txt')]

the job view link is broken and leads to HTTP ERROR 404. For example: The URL behind the Link is generated like: {{[https://Jenkins/job/BBB/job/test/job/master/1000|https://jenkins/job/BBB/job/test/job/master/1000]}}

but The link should be automatically mapped to the latest results, e.g. to

[https://Jenkins/job/BBB/job/test/job/master/45/1000|https://jenkins/job/BBB/job/test/job/master/45/1000] where 45 is in my example HEAD of the job list.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-58634 Custom ID cause broken link in job view Change By: Ulli Hafner

If recordIssues is called with a custom id, e.g recordIssues aggregatingResults: true, tools: [clangTidy(id: '1000', name: 'Clang-Tidy: Aggregated Results', pattern: 'build/**/clang-tidy.txt')] the job view link is broken and leads to HTTP ERROR 404. For example: The URL behind the Link is generated like: {{[https://Jenkins/job/BBB/job/test/job/master/1000|https://jenkins/job/BBB/job/test/job/master/1000]}}

The link should be automatically mapped to the latest results, e.g. to

{{ [https://Jenkins/job/BBB/job/test/job/master/45/1000|https://jenkins/job/BBB/job/test/job/master/45/1000] }} where 45 is in my example HEAD of the job list.

Add Comment

[jochen.steinmann2@de.bosch.com (JIRA)]

Jochen Steinmann edited a comment on JENKINS-58634

Re: Custom ID cause broken link in job view

Is your working in example called with custom id?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner resolved as Won't Fix

The problem is that you are using a numeric only ID. Seems that such IDs are claimed as build number IDs somewhere in Jenkins core (Build or Run instance). So my URL actually will never be resolved. If you use an id with character in it m1000 then everything works as expected. That means I can do nothing in my plugin here. You can try to file that as bug in core but I doubt that this will be fixed by someone as an actual build number can also resolve to the ID you have chosen.

Jenkins / JENKINS-58634

Custom ID cause broken link in job view

Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner edited a comment on JENKINS-58634

Re: Custom ID cause broken link in job view

The problem is that you are using a numeric only ID. Seems that such IDs are claimed as build number IDs somewhere in Jenkins core (Build or Run instance). So my URL actually will never be resolved.

If you use an id with character in it like {{m1000}} then everything works as expected. That means I can do nothing in my plugin here. You can try to file that as bug in core but I doubt that this will be fixed by someone as an actual build number can also resolve to the ID you have chosen.

Add Comment