[JIRA] [template-project] (JENKINS-18471) Trend graph for Findbugs, CPD, PMD etc. results are not shown from job summary if used via use publishers from other project
Andreas Schmid created JENKINS-18471 Trend graph for Findbugs, CPD, PMD etc. results are not shown from job summary if used via use publishers from other project Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: template-project Created: 24/Jun/13 10:22 AM Description: All trend graphs are just shown if they are configurated as "Post build actions". If the results e.g. for Findbugs, CPD, PMD etc. are collected via "use publishers from other project" and template project plugin the trend graphs are not shown as well. Is it possible to fix this or is it dependent on the used plugin, e.g. Findbugs, etc.? Would be great if that would work because most of our projects use these tools for almost every module and using a parent build script the configuration is always the same ... Project: Jenkins Priority: Major Reporter: Andreas Schmid 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-17815) Build Flow Plugin does not restrict node
Andreas Schmid commented on JENKINS-17815 Build Flow Plugin does not restrict node Even better would be to make it configurable at which node the jobs are executed (+ an option for "same node"). Thanks in advance 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-17815) Build Flow Plugin does not restrict node
Andreas Schmid edited a comment on JENKINS-17815 Build Flow Plugin does not restrict node There is an easy workaround if one uses https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin, configures a "node parameter" and sets it's value to the node on which the job should run accordingly. 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/groups/opt_out.
[JIRA] (JENKINS-16108) Option to use last unstable as fallback for Upstream build which trigger instead of only last successful
Andreas Schmid created JENKINS-16108 Option to use last unstable as fallback for Upstream build which trigger instead of only last successful Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 12/Dec/12 1:26 PM Description: If one chooses "Upstream build which trigger" as option for copying artifacts there is only the possibility to get "last successful as fallback" and not "last unstable" which I would like to have as well. However the wording for last successful is inconsistent in my opinion because if you just choose copying from "Lastest succesfull build" also unstable builds are considered. If you look at JENKINS-11828 and the merge of pull request #7 you see the place which my feature could be implemented. (see return isFallbackToLastSucessful() run.getResult().isBetterOrEqualTo(Result.SUCCESS); Thank you! Environment: WinXP Project: Jenkins Priority: Major Reporter: Andreas Schmid 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
