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

Form Too Large error when changing view options

    Details

    • Similar Issues:

      Description

      While testing the latest LTS edition (v1.596.3) for potential rollout on our build farm I discovered a bug that prevents the modification of Sectioned Views. In the use cases described below, attempting to make any modification to a Sectioned View, no matter how trivial, results in a "Form Too Large" error being thrown by Jenkins. This effectively prevents users from making any modifications to the affected views.

      From what I can tell there are 2 specific factors that cause this error to occur:
      1. the number of jobs in total managed by the Jenkins instance (in our case, we have > 1200 jobs)
      2. the number of sub-sections on the view of type "list view" (in our test cases, views with just one or two list view subsections seem to work fine, but ones with 5-10 subsections of this type don't)

        Attachments

          Issue Links

            Activity

            Hide
            leedega Kevin Phillips added a comment -

            This bug seems to be a symptom of the same problem described here. From what I can tell views of other types, and job configurations, no longer suffer from this issue so the problem appears to be isolated to just the Sectioned View. Hence the reason I created a new defect for it.

            Show
            leedega Kevin Phillips added a comment - This bug seems to be a symptom of the same problem described here . From what I can tell views of other types, and job configurations, no longer suffer from this issue so the problem appears to be isolated to just the Sectioned View. Hence the reason I created a new defect for it.
            Hide
            leedega Kevin Phillips added a comment -

            NOTE: Anyone who may be experiencing this problem in a production environment may be interested to know there is a workaround described on JENKINS-20327 that may be of interest:

            https://issues.jenkins-ci.org/browse/JENKINS-20327?focusedCommentId=190285&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-190285

            This workaround worked for us in our case as well.

            Show
            leedega Kevin Phillips added a comment - NOTE: Anyone who may be experiencing this problem in a production environment may be interested to know there is a workaround described on JENKINS-20327 that may be of interest: https://issues.jenkins-ci.org/browse/JENKINS-20327?focusedCommentId=190285&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-190285 This workaround worked for us in our case as well.
            Hide
            danielbeck Daniel Beck added a comment -

            Non-bundled plugin issues don't need the lts-candidate label.

            Show
            danielbeck Daniel Beck added a comment - Non-bundled plugin issues don't need the lts-candidate label.

              People

              • Assignee:
                tbingaman Timothy Bingaman
                Reporter:
                leedega Kevin Phillips
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: