[JIRA] [gerrit-trigger] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
Eric Griswold created JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 22/Mar/14 12:40 AM Description: 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. Environment: centos 6 Jenkins 1.532.2 Gerrit Trigger 2.11.0 Project: Jenkins Priority: Minor Reporter: Eric Griswold This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
rin_ne commented on JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs "metadata is long" means that a parameter has long value? If so, I think this is mainly jenkins issue. AFAIK, it is GERRIT_CHANGE_COMMIT_MESSAGE only. Because this is multi-line text, others are single-line. So StringParameterValue class should be replaced to TextParameterValue. But it would not be solved. ParameterValue which is extended by both StringParameterValue and TextParameterValue has 2 methods for description. In Javadoc, getShortDescription() requires one-line string as return value. I think this is truncation spec you mentioned. http://javadoc.jenkins-ci.org/hudson/model/ParameterValue.html#getShortDescription() But, as of now, TextParameterValue which extends StringParameterValue does not have any overrided methods for getShortDescription(). https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/TextParameterValue.java It means that TextParameterValue#getShortDescription returns the same value as StringParameterValue's one. So, unfortunately, it is hard to solve this issue only by plugin fixes. If "metadata is long" means a lot of parameters, it is also Jenkins issue. Jenkins does not have the way to reduce the display number of parameters from plugin side. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
rin_ne updated JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs Change By: rin_ne (24/Mar/14 8:15 AM) Assignee: rsandell Eric Griswold This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
Eric Griswold updated JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs Here's a screenshot. Change By: Eric Griswold (24/Mar/14 5:44 PM) Attachment: eric.griswold-shot-window-0x1c25fe5.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
