• 3.20

      When I upgraded my Jenkins to 2.277.1, I noticed I couldn't save changes to one of my jobs anymore. Through process of elimination I found out it is caused by the performance-plugin, specifically by its reporting-configuration.

      Adding the reporting to a job works just fine, it's when trying to edit the job when problems arise: you can't remove the report anymore and saving/applying don't work either.

          [JENKINS-65109] Table to div regression in performance-plugin

          I have exactly the same symptoms. Reverting back to a prior LTS version because of this.

          Dima Korobskiy added a comment - I have exactly the same symptoms. Reverting back to a prior LTS version because of this.

          Basil Crow added a comment -

          artem_fedorov FYI the table to div layout migration is part of the most recent 2.277.1 LTS release.

          Basil Crow added a comment - artem_fedorov FYI the table to div layout migration is part of the most recent 2.277.1 LTS release.

          Edrick added a comment -

          We are also experiencing the same issue. We've just updated to 2.289.1 when we starting experiencing this issue. We even updated `Performance Plugin` to the latest version which is 3.19 and it is still displaying the same issue. I've attached an image of what the alignment looks like which is causing the saves to fail.

          Edrick added a comment - We are also experiencing the same issue. We've just updated to 2.289.1 when we starting experiencing this issue. We even updated `Performance Plugin` to the latest version which is 3.19 and it is still displaying the same issue. I've attached an image of what the alignment looks like which is causing the saves to fail.

          Niko Wittenbeck added a comment - - edited

          We are also having this issue quite some time. We are currently working around it by creating a new job in Jenkins, using a working job as template, copy & modify the config XML on disk and trigger https://jenkins/reload to make the changes effective. But it would of course be a great help if the plugin would simply work again.

          Niko Wittenbeck added a comment - - edited We are also having this issue quite some time. We are currently working around it by creating a new job in Jenkins, using a working job as template, copy & modify the config XML on disk and trigger https://jenkins/reload  to make the changes effective. But it would of course be a great help if the plugin would simply work again.

          Artem Fedorov added a comment -

          Released in 3.20

          Artem Fedorov added a comment - Released in 3.20

            artem_fedorov Artem Fedorov
            malice00 Roland Asmann
            Votes:
            10 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: