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

Plugin config disappearing from job config UI

    XMLWordPrintable

Details

    • Jenkins 2.263.1

    Description

      It's really hard to describe, so just watch the video. Presume it's related to table to divs but surprised not reported previously given plugin popularity.

      Create an empty Freestyle job, scroll down, buttons disappear, reappear, decorations display but dialog does not, radio buttons shift slightly.

       

      Attachments

        Issue Links

          Activity

            markewaite Mark Waite added a comment - - edited

            Since the tables to divs changes were not introduced until Jenkins 2.264 and you're running Jenkins 2.249.x in the video, I don't think this is related to the table to div changes. I've removed the tables to divs regression label based on the version you're running.

            There were known issues (JENKINS-64136 & JENKINS-64040) in Jenkins weekly 2.258 through 2.263 that caused buttons to appear in the wrong locations. However, that problem was not introduced until 2.258 and you're running 2.249.x. You may want to try Jenkins 2.263.1 to see if the problem is resolved in 2.263.1.

            The plugins-git-issue.txt file appears to be something like a list of plugins, but contains extra information. One item of extra information is a reference to the TFS plugin. JENKINS-64241 suggests there are issues with the TFS plugin when saving forms. Have you tried removing the TFS plugin?

            I can't duplicate the problem on Jenkins 2.263.1 with git plugin 4.5.0. I also did not see the problem with previous versions of git plugin on Jenkins 2.249.3.

            markewaite Mark Waite added a comment - - edited Since the tables to divs changes were not introduced until Jenkins 2.264 and you're running Jenkins 2.249.x in the video, I don't think this is related to the table to div changes. I've removed the tables to divs regression label based on the version you're running. There were known issues ( JENKINS-64136 & JENKINS-64040 ) in Jenkins weekly 2.258 through 2.263 that caused buttons to appear in the wrong locations. However, that problem was not introduced until 2.258 and you're running 2.249.x. You may want to try Jenkins 2.263.1 to see if the problem is resolved in 2.263.1. The plugins-git-issue.txt file appears to be something like a list of plugins, but contains extra information. One item of extra information is a reference to the TFS plugin. JENKINS-64241 suggests there are issues with the TFS plugin when saving forms. Have you tried removing the TFS plugin? I can't duplicate the problem on Jenkins 2.263.1 with git plugin 4.5.0. I also did not see the problem with previous versions of git plugin on Jenkins 2.249.3.
            ianw Ian Williams added a comment -

            Thanks for the prompt response, Mark. The behavior is so bizarre I did not know where to start investigating other than to share.

            This instance was set up last week prior to 2.263.1 GA. I actually have not installed the TFS plugin yet as it's no longer in the plugins site. We feed that list into a modified install-plugins.sh (to avoid comments) and it resolves the complete list (as listed in System Info, now attached). I had git:4.4.5 installed when I first saw the issue, then pulled the latest to retest before submitting.

            I will conduct further testing on this side as well. I recall reading another ticket where plugin A affected the presentation of plugin B but can't recall which now. Maybe happening here?

            ianw Ian Williams added a comment - Thanks for the prompt response, Mark. The behavior is so bizarre I did not know where to start investigating other than to share. This instance was set up last week prior to 2.263.1 GA. I actually have not installed the TFS plugin yet as it's no longer in the plugins site. We feed that list into a modified install-plugins.sh (to avoid comments) and it resolves the complete list (as listed in System Info, now attached). I had git:4.4.5 installed when I first saw the issue, then pulled the latest to retest before submitting. I will conduct further testing on this side as well. I recall reading another ticket where plugin A affected the presentation of plugin B but can't recall which now. Maybe happening here?
            markewaite Mark Waite added a comment -

            I think I can explain what you're seeing. Jenkins 2.249.3 included a fix for JENKINS-63332. However, that introduced the regression described in JENKINS-64040. The JENKINS-64040 regression was fixed in Jenkins 2.263.1. You can either roll back to Jenkins 2.249.2 or update to Jenkins 2.263.1.

            I'm resolving this as a duplicate of JENKINS-64040.

            markewaite Mark Waite added a comment - I think I can explain what you're seeing. Jenkins 2.249.3 included a fix for JENKINS-63332 . However, that introduced the regression described in JENKINS-64040 . The JENKINS-64040 regression was fixed in Jenkins 2.263.1 . You can either roll back to Jenkins 2.249.2 or update to Jenkins 2.263.1. I'm resolving this as a duplicate of JENKINS-64040 .
            markewaite Mark Waite added a comment -

            Regression introduced in Jenkins 2.249.3 and resolved in Jenkins 2.263.1

            markewaite Mark Waite added a comment - Regression introduced in Jenkins 2.249.3 and resolved in Jenkins 2.263.1
            ianw Ian Williams added a comment -

            Can confirm 2.263.1 appears to resolve the issue. I guess there will be no 2.249.4, so that's the path forward.. Thx.

            ianw Ian Williams added a comment - Can confirm 2.263.1 appears to resolve the issue. I guess there will be no 2.249.4, so that's the path forward.. Thx.

            People

              Unassigned Unassigned
              ianw Ian Williams
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: