BTW, it looks like this PR:
https://github.com/jenkinsci/build-flow-plugin/pull/53 will fix this
properly so no more hacky scripts will be needed
On Saturday, 1 November 2014 00:21:02 UTC-7, Nick Dierauf wrote:
>
> Thanks Stuart!
> Nick.
>
> On Wednesday, October 29, 2014 12:43:56 PM UTC-7, Stua
Thanks Stuart!
Nick.
On Wednesday, October 29, 2014 12:43:56 PM UTC-7, Stuart Rowe wrote:
>
> Here you go :)
>
>
> import javax.mail.Message
> import hudson.model.*
> import com.cloudbees.plugins.flow.*
> import hudson.tasks.MailAddressResolver
>
> def getUpstreamBuild(AbstractBuild curBuild)
> {
Here you go :)
import javax.mail.Message
import hudson.model.*
import com.cloudbees.plugins.flow.*
import hudson.tasks.MailAddressResolver
def getUpstreamBuild(AbstractBuild curBuild)
{
upStreamBuild = null
if(curBuild != null)
{
// find a cause that will lead to an upstream
Stuart, can you post the groovy script that you use to determine the email
address (ie, "myscript.groovy")?
Thanks!
Nick.
On Tuesday, March 11, 2014 11:24:37 AM UTC-7, Stuart Rowe wrote:
>
> Hi, does anyone know of a way to look up a user's email address from their
> user ID? I can't make the a
Perfect, thanks again.
On Tuesday, 11 March 2014 13:15:42 UTC-7, slide wrote:
>
> You don't need to resolve the addresses yourself if you are using a SCRIPT
> token, the email-ext plugin will resolve them after it replaces the tokens.
> Yes, you can have the $DEFAULT_RECIPIENTS and ${SCRIPT...}
You don't need to resolve the addresses yourself if you are using a SCRIPT
token, the email-ext plugin will resolve them after it replaces the tokens.
Yes, you can have the $DEFAULT_RECIPIENTS and ${SCRIPT...} tokens in the
edit box and it will work just fine.
On Tue, Mar 11, 2014 at 12:44 PM, St
I just found the MailAddressResolver class on my own and it's solved the
problem.
Currently I'm adding recipients by referencing a groovy script directly in
the project recipients edit box (e.g. ${SCRIPT, script="myscript.groovy"}
). The script recursively looks up the requesting userId from th
How are you planning, in your groovy script to add the users as recipients?
Just a curiosity. You could call the MailAddressResolver resolve method
yourself from the groovy script in each recipient, but you may not need to
do that depending on how you are adding the recipients.
On Mar 11, 2014 11:5
Sorry for the confusion:
If a user schedules a single project that has an email post build step than
the email address is resolved automatically by the Active Directory plugin.
I'm having problems with a more complicated build pipeline where the
requesting user isn't propagated to a down stream
You could use the mailmap-resolver-plugin, but I may be missing something
because there seems to be a discrepancy with what you are saying. First you
need to look up the user's email address from their user ID, but then you
say you are getting email addresses from Active Directory? Can you clarify.
Hi, does anyone know of a way to look up a user's email address from their
user ID? I can't make the assumption that the email is "use...@company.com"
because I know this isn't always the case.
We're using the Active Directory plugin for security which is where the
email addresses for users are
11 matches
Mail list logo
