search

jenkinsci / build-monitor-plugin

Jenkins Build Monitor Plugin
https://plugins.jenkins.io/build-monitor-plugin/
MIT License
728 stars 279 forks source link

build-number has incorrect link #79

Closed tinu1976ch closed 10 years ago

tinu1976ch commented 10 years ago

hi there,

me again ;-)

I'm using plugin 1.5+build.119 with Jenkins 1.573

Problem is, that the build-number links to a wrong location! actually links to: http://localhost:7280/view/Build-Monitor/31fab821-accb-48a6-a93d-b0db1b321907/job/head_rsync/536/ should link to: http://localhost:7280/job/head_rsync/536/

thx for helping me.

Greets from Switzerland Tinu

mjblue commented 10 years ago

Hi, We are also seeing an issue after upgrading from 1.3+build.72 to 1.5+build.119. We are using Jenkins V1.515

The problem I have is that the 'view' name isn't being populated in the link:

it links to "http://servername:8090/view/job/AE6_EURO_PLAN/" when this should have the viewname in the link "http://servername:8090/view/EUROTESTS/job/AE6_EURO_PLAN"

Do we need to upgrade Jenkins for this?

Thanks

Mark

jan-molak commented 10 years ago

Thanks for reporting this, I'll have a look. Is it only the build number that has an incorrect link, or are you also having troubles with the job-name link?

tinu1976ch commented 10 years ago

job-name is linking to: http://localhost:7280/view/Build-Monitor/job/head_rsync/ which shows the same as: http://localhost:7280/job/head_rsync/

=> means job-name link is correct

mjblue commented 10 years ago

I am having the issue with JUST job name.. job number link does have the "view name":

job number link CORRECT: http://server:8091/view/EUROTESTS/job/AE6_EURO_PLAN/20/ job name link INCORRECT: http://server:8091/view/job/AE6_EURO_PLAN/

Thanks

Mark

jan-molak commented 10 years ago

@mjblue - I've only just noticed that you're using Jenkins Core 1.515. Please note that Build Monitor requires at least Jenkins 1.535. Could you please upgrade to a stable, Long-Term Support (LTS) release that meets these criteria and let me know if the problem still persists?

Thanks, Jan

jan-molak commented 10 years ago

@TinuCH1976 - the problem you're seeing has been introduced in Jenkins 1.569; please note that 1.569 is not a stable release. I'd strongly recommend using a stable, Long-Term Support (LTS) release instead. 1.565.1 is the latest and greatest at the moment.

I've raised the problem you reported with the Jenkins core team and am currently helping them to debug it.

update: Thanks to the help from Mr. @jglick we managed to track down the problem to an issue in Stapler. Feel free to vote on JENKINS-24165 while I'm looking for a workaround

jglick commented 10 years ago

Analyzed as JENKINS-24165 and some potential plugin workarounds suggested.

tinu1976ch commented 10 years ago

@jan-molak - thx 4 your info... i didn't realized, that there are stable version too... i just visit jenkins-homepage und downloaded "latest and greatest"... but that there was also a tab "long term support release" i didn't saw :-( how to "downgrade"?!? just replacing the war-file?

jan-molak commented 10 years ago

Hey Tinu, I should be able to work around issues introduced in the latest Jenkins builds this week. If you can't wait you can downgrade Jenkins by replacing the war file as described on the Jenkins WIKI. If you decide to downgrade make sure you backup your Jenkins 'work' directory first.