[JIRA] (JENKINS-16108) Option to use "last unstable" as fallback for "Upstream build which trigger" instead of only "last successful"
Title: Message Title Craig Ringer commented on JENKINS-16108 Re: Option to use "last unstable" as fallback for "Upstream build which trigger" instead of only "last successful" This is possible with the copyArtifacts plugin now, it's just less than clear in the docs. copyArtifacts( projectName: "blah" selector: lastSuccessful(stable: false), ... ) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.146912.1355318803000.9703.1558592820307%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16108) Option to use "last unstable" as fallback for "Upstream build which trigger" instead of only "last successful"
Title: Message Title Thorsten Meinl commented on JENKINS-16108 Re: Option to use "last unstable" as fallback for "Upstream build which trigger" instead of only "last successful" Any estimate when this will be fixed? In my opinion this is even a bug, because in Jenkins terms "successful" means stable or unstable (but not failed). However, the plug-in will only copy from the last stable job which may lead to unexpected results. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (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
