On 2012-07-05 08:54, Thomas Sondergaard wrote:
I have a jenkins job that is not sending emails to the individuals that
broke the build. I've attached the config.xml for the job.
Looking at a particular build (build #65) where jenkins failed to send
emails, I get some conflicting and surprising information. Jenkins tells
me the job was triggered by an SCM change (see attached pollinglog.txt).
At the same time the changelog section for build #65 tells me "no changes."
The job is a multi-config job and the failing job reports: "An attempt
to send an e-mail to empty list of recipients, ignored"
So in a way the "no changes" is consistent with not sending any emails,
but there were changes as correctly noted by the SCM polling that caused
the job to be triggered.
I'd like to get to the bottom of this. Help, suggestions, insights are
greatly appreciated.
Thanks,
Thomas
Just replying to my own post here :-)
I got to thinking about how the git-plugin detects changes. In my case
the branches that are built are typically new, so if the git-plugin is
checking against what it has built on that branch earlier, that wont
work. I am using the git-plugin in "merge to target branch" mode and the
stuff that should be considered changes are the commits that are merged
to the target branch.
Perhaps someone can tell me how the git-plugin detects changes (for new
branches)?
Thanks,
Thomas
