[JIRA] [buildgraph-view-plugin] (JENKINS-35502) Build description misplaced on the same line with build status
Title: Message Title Sami Salonen created an issue Jenkins / JENKINS-35502 Build description misplaced on the same line with build status Issue Type: Bug Assignee: Unassigned Attachments: earlier.png, now.png Components: buildgraph-view-plugin Created: 2016/Jun/09 3:06 PM Environment: Build Graph View plugin 1.3.1 Jenkins 1.651.2 Latest versions of Firefox and Chrome Priority: Minor Reporter: Sami Salonen Build descriptions used to be on their own lines near the top of the build node of a build graph Version 1.3.1 (or 1.3) of the plugin changed the behavior such that build descriptions are on the same line with the build status information. This makes graphs vertically more compact, but compromise readability. I liked the old setup better. Please consider reverting back to old behavior unless this was a conscious design decision e.g. to gain more compact graphs.
[JIRA] [buildgraph-view-plugin] (JENKINS-35502) Build description misplaced on the same line with build status
Title: Message Title Sami Salonen updated an issue Jenkins / JENKINS-35502 Build description misplaced on the same line with build status Change By: Sami Salonen Build descriptions used to be on their own lines near the top of the build node of a build graph ! ( earlier.png |thumbnail! ). Version 1.3.1 (or 1.3) of the plugin changed the behavior such that build descriptions are on the same line with the build status information . ! ( now.png |thumbnail! ). This makes graphs vertically more compact, but compromise readability. I liked the old setup better. Please consider reverting back to old behavior unless this was a conscious design decision e.g. to gain more compact graphs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [audit-trail-plugin] (JENKINS-32679) Audit Trail plugin fails to track queue item api calls
Title: Message Title Sami Salonen created an issue Jenkins / JENKINS-32679 Audit Trail plugin fails to track queue item api calls Issue Type: Bug Assignee: Unassigned Components: audit-trail-plugin Created: 28/Jan/16 7:21 PM Environment: Audit Trail plugin version: 2.2 Jenkins version: 1.609.3 Priority: Minor Reporter: Sami Salonen Steps to reproduce using the Jenkins GUI: 1. Change Audit Trail configuration URL Patterns to Log in Jenkins global configuration from its default value: .*/(?:configSubmit|..|safeExit) to include also api calls: .*/(?:configSubmit|..|safeExit|api.*) 2. Trigger a build and check its queueId from JENKINS_HOST/job/project_name/lastBuild/api/xml 3. Query queue item using JENKINS_HOST/queue/item/queue-id-from-previous-step/api/xml 4. Jenkins should say "Oops!" with a devilish grin and dump a stack trace containing this: Caused by: java.lang.NoSuchMethodError: hudson.model.Queue.getItem(I)Lhudson/model/Queue$Item; at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:84)
[JIRA] [rebuild-plugin] (JENKINS-19673) Enable/Disable Rebuild Plugin per job
Title: Message Title Sami Salonen commented on JENKINS-19673 Re: Enable/Disable Rebuild Plugin per job This feature was introduced in version 1.25. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [urltrigger-plugin] (JENKINS-15843) URL Trigger Plugin: Display change in build summary page.
Title: Message Title Sami Salonen commented on JENKINS-15843 Re: URL Trigger Plugin: Display change in build summary page. I would find it useful if URLTrigger log would contain the diff between previous and current poll when build gets triggered by the URLTrigger. This feature should probably be configurable on project level with default being off to keep the backward compatibility. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
