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

"Configure" breadcrumb shows "undefined" on all entries

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • 2.401.1-RC
    • 2.401.1

      On the 2.401.1 release candidate version, the Configure breadcrumb entries all show "undefined" at the end.

          [JENKINS-71345] "Configure" breadcrumb shows "undefined" on all entries

          Cathy added a comment -

          This has been fixed on 2.403, apparently as a side effect of https://github.com/jenkinsci/jenkins/pull/7474 and https://github.com/jenkinsci/jenkins/pull/7887.

          Cathy added a comment - This has been fixed on 2.403, apparently as a side effect of  https://github.com/jenkinsci/jenkins/pull/7474  and  https://github.com/jenkinsci/jenkins/pull/7887 .

          Mark Waite added a comment - - edited

          I'm hesitant to include the Tippy.js change into the 2.401.1 LTS as a backport. It is a larger change that I had hoped would have more time to evaluate in Jenkins weekly releases. However, I'm not aware of any known issues with the Tippy.js change.

          Bisecting now to try to understand which commit inserted that into the 2.401 (or earlier) release.

          Mark Waite added a comment - - edited I'm hesitant to include the Tippy.js change into the 2.401.1 LTS as a backport. It is a larger change that I had hoped would have more time to evaluate in Jenkins weekly releases. However, I'm not aware of any known issues with the Tippy.js change. Bisecting now to try to understand which commit inserted that into the 2.401 (or earlier) release.

          Mark Waite added a comment -

          As far as I can tell, the problem first arrived in 2.401. The 2.400 release does not have the issue. Now to narrow to the specific commit

          Mark Waite added a comment - As far as I can tell, the problem first arrived in 2.401. The 2.400 release does not have the issue. Now to narrow to the specific commit

          Mark Waite added a comment - - edited

          The problem seems to first be visible in commit 291f5edcc5942c4 that is part of pull request 7084. When that commit is reverted, the problem is resolved.

          I think that it is safer to revert that commit than to backport the Tippy.js changes into 2.401. I'll submit a pull request proposing to revert that change from stable-2.401

          Mark Waite added a comment - - edited The problem seems to first be visible in commit 291f5edcc5942c4 that is part of pull request 7084 . When that commit is reverted, the problem is resolved. I think that it is safer to revert that commit than to backport the Tippy.js changes into 2.401. I'll submit a pull request proposing to revert that change from stable-2.401

          Mark Waite added a comment -

          I've submitted PR-8052 to the stable-2.401 branch proposing to revert the commit

          Mark Waite added a comment - I've submitted PR-8052 to the stable-2.401 branch proposing to revert the commit

            markewaite Mark Waite
            cchan Cathy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: