Pipeline: Doesn't always get commit authors in emailextrecipients

[Sverre Moe]

There seems to be a lottery of some sort what I get from emailextrecipients

I expect to get the authors from the commits it is building, but most of the times emailextrecipients gives me nothing.

/**
 * Notify developers of failed build
 */
void notifyFailedBuild() {
    final def projectName = packageInfo.getProjectName()
    final def repositoryOwners = getRepositoryOwners(projectName)

    final def RECIPIENTS = emailextrecipients([
        [$class: 'DevelopersRecipientProvider'],
        [$class: 'CulpritsRecipientProvider'],
        [$class: 'UpstreamComitterRecipientProvider']
    ])

    final def SUBJECT = "${projectName} ${env.BRANCH_NAME} - Build #${env.BUILD_NUMBER} - FAILED!"
    final def CONTENT = "Check console output at ${env.BUILD_URL} to view the results."

    if (RECIPIENTS != null && !RECIPIENTS.isEmpty()) {
        mail to: RECIPIENTS, cc: repositoryOwners, bcc: "devops", replyTo: "donot...@company.com", subject: SUBJECT, body: CONTENT
    } else {
        mail to: repositoryOwners, bcc: "devops", replyTo: "donot...@company.com", subject: SUBJECT, body: CONTENT
    }
}

[Slide]

mail is using the mailer plugin, if you want to use email-ext, you need to use emailext (see https://jenkins.io/doc/pipeline/steps/email-ext/).

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f19567ce-1322-40ee-b9e3-822073762bc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sverre Moe]

I followed the Pipeline examples for the email-ext plugin:

https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin#Email-extplugin-PipelineExamples

There are 3 examples how to use emailextrecipients

Problem is only mail allows me to set the cc and bcc.

[Sverre Moe]

It would seem that the step emailextrecipients would give a list of recipients so using Mailer should work.

final def RECIPIENTS = emailextrecipients([
    [$class: 'DevelopersRecipientProvider'],
    [$class: 'CulpritsRecipientProvider'],
    [$class: 'UpstreamComitterRecipientProvider']
])

step([$class: 'Mailer', notifyEveryUnstableBuild: true,  recipients: RECIPIENTS])

emailext body: CONTENT, recipientProviders: [[$class: 'CulpritsRecipientProvider'], [$class: 'DevelopersRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider']], subject: SUBJECT

mail to: RECIPIENTS, cc: repositoryOwners, bcc: "devops", subject: SUBJECT, body: CONTENT

However I do not always get anything out of emailextrecipients.

[Sverre Moe]

It looks like email-ext has support for CC and BCC

https://github.com/jenkinsci/email-ext-plugin/commit/4aacabf9b9fa9be326ebc362519e2f5d1bbb43fb

However it is not present in the Pipeline syntax.

[Sverre Moe]

Must run emailext within a heavyweight executor.

node {
    emailext subject: SUBJECT, body: CONTENT, cc: "devops", recipientProviders: [[$class: 'CulpritsRecipientProvider'], [$class: 'DevelopersRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider']]
}

While the standard mail can run on a flyweight executor:

I have a theory:

In order to get a list of recipients email-ext needs the git repository available on a heavyweight executor in order to get developers, culprits and commiters from each commit in the build.

That is probably why emailextrecipients does not give me any recipients running on a flyweight executor.

[Sverre Moe]

I tried to test that theory by getting emailextrecipients right after checkout scm within my Checkout stage.

However it gives me no recipients.

[Pipeline] emailextrecipients
[Pipeline] emailext
Job type does not allow token replacement.
Job type does not allow token replacement.
Job type does not allow token replacement.
An attempt to send an e-mail to empty list of recipients, ignored.

Also seems it has some problems with ${PARAM} within the variables for SUBJECT and BODY.

[Slide]

You can set cc and bcc in emailext using prefixes cc:som...@something.com, bcc:someo...@something.com

On Tue, Sep 6, 2016 at 9:16 AM Sverre Moe <sverr...@gmail.com> wrote:

I followed the Pipeline examples for the email-ext plugin:

https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin#Email-extplugin-PipelineExamples

There are 3 examples how to use emailextrecipients

Problem is only mail allows me to set the cc and bcc.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7b18848-9280-4780-a246-a8cfe97ddfe5%40googlegroups.com.

[Sverre Moe]

In what parameter, to or recipientProviders?


tirsdag 6. september 2016 19.07.42 UTC+2 skrev slide følgende:

You can set cc and bcc in emailext using prefixes cc:som...@something.com, bcc:som...@something.com

On another matter: Not sure why, Every time I try to reply on this discussion, the post gets deleted. 

[Slide]

On Thu, Sep 8, 2016 at 11:25 PM Sverre Moe <sverr...@gmail.com> wrote:

In what parameter, to or recipientProviders?

In the "to" parameter. The recipient providers always use the "to" and don't provide a way to do cc or bcc.

 

tirsdag 6. september 2016 19.07.42 UTC+2 skrev slide følgende:

You can set cc and bcc in emailext using prefixes cc:som...@something.com, bcc:som...@something.com

On another matter: Not sure why, Every time I try to reply on this discussion, the post gets deleted.

Are you a member of the google group? If not, perhaps some moderating is happening.

 

 

--
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-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/66c4402f-b48e-4713-8ef6-24c774e42269%40googlegroups.com.

[Sverre Moe]

fredag 9. september 2016 14.44.33 UTC+2 skrev slide følgende:

On Thu, Sep 8, 2016 at 11:25 PM Sverre Moe <sverr...@gmail.com> wrote:

In what parameter, to or recipientProviders?

In the "to" parameter. The recipient providers always use the "to" and don't provide a way to do cc or bcc.

Ok. Shall try it. 

tirsdag 6. september 2016 19.07.42 UTC+2 skrev slide følgende:

You can set cc and bcc in emailext using prefixes cc:som...@something.com, bcc:som...@something.com

On another matter: Not sure why, Every time I try to reply on this discussion, the post gets deleted.

Are you a member of the google group? If not, perhaps some moderating is happening.

 

 

Must be some moderating. I am a member of the group. Never had any trouble before.

 

[Sverre Moe]

Anyhow. Why does something return nothing?

final def RECIPIENTS = emailextrecipients([
        [$class: 'DevelopersRecipientProvider'],
        [$class: 'CulpritsRecipientProvider'],

        [$class: 'UpstreamComitterRecipientProvider'],
        [$class: 'FirstFailingBuildSuspectsRecipientProvider'],
        [$class: 'FailingTestSuspectsRecipientProvider']
    ])

node("master") {
    emailext body: CONTENT, recipientProviders: [[$class: 'CulpritsRecipientProvider'], [$class: 'DevelopersRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider'], [$class: 'FirstFailingBuildSuspectsRecipientProvider'], [$class: 'FailingTestSuspectsRecipientProvider']], subject: SUBJECT, to: "cc:${CC},bcc:${BCC}"
}

Could anyone confirm that emailext needs access to the source code git repository in the workspace?

Perhaps I should include ALL the recipient providers, just in case.

What I want is to notify the commit authors of failed build. Using only the 3 first recipient providers, something recipients are empty.