You can use the PROJECT_DEFAULT_CONTENT in the triggers for them to use the
same content as you specified in the main area for the content.
On Tue, Mar 27, 2012 at 1:48 PM, dpreilan wrote:
> Create your groovy script and place in under your $JENKINS_HOME/email-
> templates. Create the email-temp
Create your groovy script and place in under your $JENKINS_HOME/email-
templates. Create the email-templates directory if needed.
Say you call it foo.template.
In your jenkins job(s), configure your "Editable Email Notification"
Content area, like:
${SCRIPT,template="foo.template"}
Make sure you
On 24/03/2012 00:48, Slide wrote:
I use something like this in my groovy template
// the goal is to find the top level job which should contain the changelist
def upstreamBuild = null
def cause = build.causes.find {
if(it instanceof hudson.model.Cause.UpstreamCause) {
return true
I use something like this in my groovy template
// the goal is to find the top level job which should contain the changelist
def upstreamBuild = null
def cause = build.causes.find {
if(it instanceof hudson.model.Cause.UpstreamCause) {
return true
}
return false
}
while(cause !
On 19/03/2012 15:26, Slide wrote:
This is awesome. Thanks for sharing! I've heard of several people who
would like to do something like this. I'll try and add it to the wiki
for email-ext.
Sorry for topic hijacking, but I tried asking this before and got no
response, yet this topic seems simil
