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

Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history

      If Gerrit triggers create a queue in the Pending Jobs column in the project page, it will insert build parameters/metadata about the trigger: GERRIT_EVENT_TYPE, GERRIT_EVENT_HASH, etc.

      If this metadata is long, it will distort the project page to be visually unusable.

      Would like a way to either turn of or truncate this display of Gerrit metadata.

          [JENKINS-22311] Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history

          Eric Griswold created issue -
          rin_ne made changes -
          Assignee Original: rsandell [ rsandell ] New: Eric Griswold [ eric_griswold ]
          Eric Griswold made changes -
          Attachment New: eric.griswold-shot-window-0x1c25fe5.png [ 25606 ]
          Eric Griswold made changes -
          Component/s New: core [ 15593 ]
          Assignee Original: Eric Griswold [ eric_griswold ] New: rsandell [ rsandell ]
          rsandell made changes -
          Component/s Original: gerrit-trigger [ 15731 ]
          Assignee Original: rsandell [ rsandell ]
          Jakub Czaplicki made changes -
          Labels New: build-history build-queue jenkins parameterized-trigger parameters ui ux
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-23064 [ JENKINS-23064 ]
          Jakub Czaplicki made changes -
          Description Original: If Gerrit triggers create a queue in the Pending Jobs column in the project page, it will insert metadata about the trigger: GERRIT_EVENT_TYPE, GERRIT_EVENT_HASH, etc.

          If this metadata is long, it will distort the project page to be visually unusable.

          Would like a way to either turn of of truncate this display of Gerrit metadata.
          New: If Gerrit triggers create a queue in the Pending Jobs column in the project page, it will insert build parameters/metadata about the trigger: GERRIT_EVENT_TYPE, GERRIT_EVENT_HASH, etc.

          If this metadata is long, it will distort the project page to be visually unusable.

          Would like a way to either turn of or truncate this display of Gerrit metadata.
          Environment Original: centos 6
          Jenkins 1.532.2
          Gerrit Trigger 2.11.0
          New: centos 6
          Jenkins 1.532.2 - 1.555 - 1.563
          Gerrit Trigger 2.11.0
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Summary Original: gerrit trigger can cause unwieldy build history when there are pending jobs New: Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
          Daniel Beck made changes -
          Component/s New: gerrit-trigger [ 15731 ]
          Component/s Original: core [ 15593 ]
          rin_ne made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: gerrit-trigger [ 15731 ]
          rin_ne made changes -
          Link New: This issue is blocking JENKINS-23421 [ JENKINS-23421 ]

            danielbeck Daniel Beck
            eric_griswold Eric Griswold
            Votes:
            9 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: