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

Claim link on all views, but only works from "All" view

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • claim-plugin
    • None
    • Platform: All, OS: All

      If you create separate builds, the "Claim" link shows up on all views, but only
      works on the main page (the "ALL" view). For example:

      http://hudson:8090/ is my main Hudson view. However, I have a view called FOO
      with the following URL:

      http://hudson:8090/view/FOO

      On both the main page and in the FOO view, the Hudson "Claim Report" link is
      shows on the left hand side. But clicking on the link in the FOO view gives me a
      404 error (going to URL http://hudson:8090/view/FOO/claims). Clicking on the
      Claims Report link from the main page gives me the Claim report (going to URL
      http://hudson:8090/claims).

          [JENKINS-3534] Claim link on all views, but only works from "All" view

          mdonohue added a comment -

          Issue 3064 is for the ci-game, which is distinct from the claim plugin. I'm not
          aware of a common root cause.

          mdonohue added a comment - Issue 3064 is for the ci-game, which is distinct from the claim plugin. I'm not aware of a common root cause.

          jotimail added a comment -

          Added link to 100papercuts report - this would make the claim feature more
          usefull and I hope it would not be too much work to be on the papercuts list.

          jotimail added a comment - Added link to 100papercuts report - this would make the claim feature more usefull and I hope it would not be too much work to be on the papercuts list.

          redsolo added a comment -

          added to cc list

          redsolo added a comment - added to cc list

          huybrechts added a comment -

          not fea

          huybrechts added a comment - not fea

          redsolo added a comment -

          I fixed a similar problem in the ci-game plugin (issue 3064). I discussed it with Kohsuke
          in the IRC chat, and he suggested that the getUrl() should return "/ci-game" instead of
          "ci-game". Doing this (http://fisheye4.atlassian.com/changelog/hudson/?cs=21105) fixed
          the issue.

          redsolo added a comment - I fixed a similar problem in the ci-game plugin (issue 3064). I discussed it with Kohsuke in the IRC chat, and he suggested that the getUrl() should return "/ci-game" instead of "ci-game". Doing this ( http://fisheye4.atlassian.com/changelog/hudson/?cs=21105 ) fixed the issue.

          redsolo added a comment -

          I fixed a similar problem in the ci-game plugin (issue 3064). I discussed it with Kohsuke
          in the IRC chat, and he suggested that the getUrl() should return "/ci-game" instead of
          "ci-game". Doing this (http://fisheye4.atlassian.com/changelog/hudson/?cs=21105) fixed
          the issue.

          redsolo added a comment - I fixed a similar problem in the ci-game plugin (issue 3064). I discussed it with Kohsuke in the IRC chat, and he suggested that the getUrl() should return "/ci-game" instead of "ci-game". Doing this ( http://fisheye4.atlassian.com/changelog/hudson/?cs=21105 ) fixed the issue.

          Code changed in hudson
          User: : huybrechts
          Path:
          trunk/hudson/plugins/claim/pom.xml
          trunk/hudson/plugins/claim/src/main/java/hudson/plugins/claim/ClaimColumn.java
          trunk/hudson/plugins/claim/src/main/java/hudson/plugins/claim/ClaimPublisher.java
          trunk/hudson/plugins/claim/src/main/java/hudson/plugins/claim/ClaimedBuildsReport.java
          trunk/hudson/plugins/claim/src/main/resources/hudson/plugins/claim/ClaimColumn/column.jelly
          trunk/hudson/plugins/claim/src/main/resources/hudson/plugins/claim/ClaimedBuildsReport/index.jelly
          http://fisheye4.cenqua.com/changelog/hudson/?cs=24187
          Log:

          • some cleanup
          • JENKINS-3534 claim report link on views now works, but it still shows the report for ALL projects (not just the view)
          • [FIXED JENKINS-4389] added a column showing a claim badge

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : huybrechts Path: trunk/hudson/plugins/claim/pom.xml trunk/hudson/plugins/claim/src/main/java/hudson/plugins/claim/ClaimColumn.java trunk/hudson/plugins/claim/src/main/java/hudson/plugins/claim/ClaimPublisher.java trunk/hudson/plugins/claim/src/main/java/hudson/plugins/claim/ClaimedBuildsReport.java trunk/hudson/plugins/claim/src/main/resources/hudson/plugins/claim/ClaimColumn/column.jelly trunk/hudson/plugins/claim/src/main/resources/hudson/plugins/claim/ClaimedBuildsReport/index.jelly http://fisheye4.cenqua.com/changelog/hudson/?cs=24187 Log: some cleanup JENKINS-3534 claim report link on views now works, but it still shows the report for ALL projects (not just the view) [FIXED JENKINS-4389] added a column showing a claim badge

          jminne added a comment -

          "claim report link on views now works, but it still shows the report for ALL projects (not just the view)" is not exactly true. The links from all the views go to the default view, not the All view. So if your default view is anything other than All then only claims from jobs visible that tab(view) are visible.

          This was a step backwards for me since I never use All as a default view. I'm hoping there is some jelly hack to get the claims link working again or a patch soon.

          jminne added a comment - "claim report link on views now works, but it still shows the report for ALL projects (not just the view)" is not exactly true. The links from all the views go to the default view, not the All view. So if your default view is anything other than All then only claims from jobs visible that tab(view) are visible. This was a step backwards for me since I never use All as a default view. I'm hoping there is some jelly hack to get the claims link working again or a patch soon.

          Steve Roth added a comment -

          this is still an issue in Jenkins 1.454

          Steve Roth added a comment - this is still an issue in Jenkins 1.454

          Fixed in 2.0

          Christian Bremer added a comment - Fixed in 2.0

            huybrechts huybrechts
            qazwart qazwart
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: