On Tuesday, August 5, 2014 at 3:14:13 AM UTC+12, James Chao wrote: > > Hm, yeah this is really strange. $CHANGES is definitely totally > empty...this is even for an existing branch (where I just pushed additional > changes...). >
Sorry to awaken an old thread. I'm looking into a way for Jenkins to generate emails when a Pull Request job created by the GitHub Pull Request Builder fails. My understanding is that when a pull request is created on github, the changes are put on a *brand new branch*, even if the target of the PR is an existing branch. If at least two commits are required to determine CHANGES, could this explain why emails are not generated for contributors who "broke the build"? I'm looking for suggestions of an alternative way for Jenkins to notify contributors in this circumstance, short of putting their email addresses in the default mailing list. -- David. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cd45d1da-ec37-4889-95cf-35509c2212b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
