Can you explain why you think it would be better to poll since the last successful build rather than the current behavior?
The current behavior is consistent with the other Jenkins SCM plugins, so seems like the preferred technique. If the last change left the build broken, then it seems like it is best to poll for the next change so that the problem can be fixed immediately. If the last change left the build in good condition, then it seems like it is best to poll for the next change so that new problems can be detected immediately. In both cases, polling changes since the last build seems like the preferred technique to quickly detect and resolve problems. Mark Waite >________________________________ > From: Josh Robinson <joshtrob...@gmail.com> >To: jenkinsci-users@googlegroups.com >Sent: Tuesday, January 29, 2013 12:57 PM >Subject: ClearCase Polling Since Last SUCCESSFUL Build > > >Hey all, > >Jenkins ClearCase plugin is polling changes since the last build, instead of >the last successful build. Anyone know how to change this? I don't see an >option anywhere for this. Is this expected behavior? I would expect the >default use case would be from the last successful build time. > >Any ideas? > >Thanks >-- >You received this message because you are subscribed to the Google Groups >"Jenkins Users" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to jenkinsci-users+unsubscr...@googlegroups.com. >For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
