[JIRA] [job-dsl-plugin] (JENKINS-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title
Tom Reichelt commented on JENKINS-34367
Re: Add support for empty sendTo field for extendedEmail plugin
Hi Edgar,
thanks for your response. We have used an external script as described here (http://stackoverflow.com/questions/14541617/how-can-jenkins-downstream-job-send-email-notification-to-upstream-git-committer) to address commiters.
In our job configuration we've added this script in the recipients block and removed the sendTo field.
While migrating to JobDSL I've tried to rebuild this behavior via extendedMailPublisher: ctx.sendTo{} ctx.recipientList('$ {SCRIPT, script="committers.goovy"}
')
but sendTo can't be removed via JobDSL. Skipping this field will generate default. Using '' or null isn't allowed or does not give the expected result so I've implemented this via configure block (see attachment).
In the meantime we've refactored the jobs to use JobDSLs behavior: developers() in first job and upstreamCommitters in downstream jobs which is working fine. It's not possible to rebuild the job configured in UI in JobDSL, but as this isn't a normal use case please feel free to mark ticket as won't fix.
Thanks and kind regards, Tom
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Tom Reichelt updated an issue Jenkins / JENKINS-34367 Add support for empty sendTo field for extendedEmail plugin Change By: Tom Reichelt Attachment: configure-block.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Edgar Yu assigned an issue to Edgar Yu Jenkins / JENKINS-34367 Add support for empty sendTo field for extendedEmail plugin Change By: Edgar Yu Assignee: Daniel Spilker Edgar Yu Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Edgar Yu started work on JENKINS-34367 Change By: Edgar Yu Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Edgar Yu updated an issue Jenkins / JENKINS-34367 Add support for empty sendTo field for extendedEmail plugin Change By: Edgar Yu In the front end it's possible to delete the default for the extendedEmailPublisher-Plugin: Editable Email Notification > Advanced Settings > Triggers > any > "Send To" The recipients of "send To" can be deleted so it's possible to add custom recipients in recipient list.Using jobdsl plugin leaving sendTo empty or setting to "null" outputs custom behavior recipients list which is not the desired behavior.An empty String is not allowed.The configure block to achieve the desired output for 4 different triggers is quite ugly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Edgar Yu commented on JENKINS-34367 Re: Add support for empty sendTo field for extendedEmail plugin Hi, Tom Can you use the DSL script to explain what you want? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title Tom Reichelt created an issue Jenkins / JENKINS-34367 Add support for empty sendTo field for extendedEmail plugin Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Apr/21 9:10 AM Priority: Minor Reporter: Tom Reichelt In the front end it's possible to delete the default for the extendedEmailPublisher-Plugin: Editable Email Notification > Advanced Settings > Triggers > any > "Send To" The recipients of "send To" can be deleted so it's possible to add custom recipients in recipient list. Using jobdsl plugin leaving sendTo empty or setting to "null" outputs custom behavior recipients list which is not the desired behavior. An empty String is not allowed. The configure block to achieve the desired output for 4 different triggers is quite ugly. Add Comment
