Yes, that looks correct. In your email templates, are you adding the change
information? If so, does it come out correct?


On Thu, Jul 31, 2014 at 6:19 PM, James Chao <[email protected]> wrote:

> Hi slide,
>
> I do see this scm section in the config.xml file. Does this look right?
>
>   <scm class="hudson.plugins.git.GitSCM" plugin="[email protected]">
>     <configVersion>2</configVersion>
>     <userRemoteConfigs>
>       <hudson.plugins.git.UserRemoteConfig>
>         <refspec>+refs/pull/*:refs/remotes/origin/pr/*</refspec>
>         <url>[email protected]:[MY REPO NAME].git</url>
>         <credentialsId>[MY CREDENTIALS]</credentialsId>
>       </hudson.plugins.git.UserRemoteConfig>
>     </userRemoteConfigs>
>     <branches>
>       <hudson.plugins.git.BranchSpec>
>         <name>${sha1}</name>
>       </hudson.plugins.git.BranchSpec>
>     </branches>
>
> <doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations>
>     <browser
> class="hudson.plugins.git.browser.FisheyeGitRepositoryBrowser">
>       <url></url>
>     </browser>
>     <submoduleCfg class="list"/>
>     <extensions>
>       <hudson.plugins.git.extensions.impl.WipeWorkspace/>
>       <hudson.plugins.git.extensions.impl.RelativeTargetDirectory>
>         <relativeTargetDir>[MY DIR NAME]</relativeTargetDir>
>       </hudson.plugins.git.extensions.impl.RelativeTargetDirectory>
>       <hudson.plugins.git.extensions.impl.SubmoduleOption>
>         <disableSubmodules>false</disableSubmodules>
>         <recursiveSubmodules>true</recursiveSubmodules>
>         <trackingSubmodules>false</trackingSubmodules>
>       </hudson.plugins.git.extensions.impl.SubmoduleOption>
>     </extensions>
>   </scm>
>
> On Thursday, July 31, 2014 6:18:39 PM UTC-5, slide wrote:
>
>> I'm not familiar with the GitHub Pull Request Builder plugin, does it
>> integrate with the Git plugin at all? If you look in the config.xml for the
>> job, is there anything in the SCM section? The email-ext plugin uses the
>> SCM for the build to determine the developers.
>>
>>
>> On Thu, Jul 31, 2014 at 3:53 PM, James Chao <[email protected]> wrote:
>>
>>> Hi slide,
>>>
>>> This is kicked off by the Github pull request builder in this job.
>>>
>>> Here's the output. Thanks.
>>>
>>> FAILURE: At least one test failed.
>>> Build step 'Execute shell' marked build as failure
>>> Checking for post-build
>>> Performing post-build step
>>> Checking if email needs to be generated
>>> Email was triggered for: Always
>>> Email was triggered for: Failure - Any
>>> Sending email for trigger: Failure - Any
>>> NOT overriding default server settings, using Mailer to create session
>>> messageContentType = text/html; charset=UTF-8
>>>
>>> Request made to attach build log
>>> Adding recipients from project recipient list
>>> Adding recipients from trigger recipient list
>>> Setting In-Reply-To since last build was not successful
>>> Successfully created MimeMessage
>>> Sending email for trigger: Always
>>> NOT overriding default server settings, using Mailer to create session
>>> messageContentType = text/html; charset=UTF-8
>>> Request made to attach build log
>>> Adding recipients from trigger recipient list
>>> Setting In-Reply-To since last build was not successful
>>> Successfully created MimeMessage
>>> An attempt to send an e-mail to empty list of recipients, ignored.
>>> Some error occured trying to send the email...check the Jenkins log
>>> Finished: FAILURE
>>>
>>>
>>> On Thursday, July 31, 2014 5:45:06 PM UTC-5, slide wrote:
>>>
>>>> Can you provide a build log with debug mode enabled in the global
>>>> config for email-ext? Culprits uses Jenkins core to determine who did what,
>>>> but uses its own stuff for determining developers (looks at the changelist
>>>> from the SCM for the job). Is this job kicked off by another job that does
>>>> the SCM stuff, or is the SCM part of this job?
>>>>
>>>>
>>>> On Thu, Jul 31, 2014 at 3:43 PM, James Chao <[email protected]> wrote:
>>>>
>>>>>  Hi,
>>>>>
>>>>> I'm currently using the GitHub Pull Request Builder plugin together
>>>>> with the Email-ext plugin.
>>>>>
>>>>> For my post-build email, I'm not able to get emails to be sent to
>>>>> "developers" and "culprits". "Requestor" and "Recipient List" (the project
>>>>> default) do work though...
>>>>>
>>>>> Has anyone else run into this?
>>>>>
>>>>> ====================
>>>>>
>>>>> Here are the versions of the relevant plugins:
>>>>>
>>>>>    - GIT client plugin: 1.10.1
>>>>>    - GIT plugin: 2.2.3
>>>>>    - GitHub API Plugin: 1.55
>>>>>    - GitHub plugin: 1.9.1
>>>>>    - GitHub Pull Request Builder: 1.12
>>>>>    - Email Extension Plugin: 2.38.1
>>>>>
>>>>> Here is my post-build notification set up:
>>>>>
>>>>>
>>>>> <https://lh3.googleusercontent.com/-uZi_YtV6M7s/U9rGV4wdVpI/AAAAAAAAsVE/UuxnDVE2Qzo/s1600/Screen+Shot+2014-07-31+at+5.42.03+PM.png>
>>>>>
>>>>>
>>>>>
>>>>>  --
>>>>> 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 [email protected].
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Website: http://earl-of-code.com
>>>>
>>>  --
>>> 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 [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>  --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Website: http://earl-of-code.com

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to