Re: Adopt email-ext plugin

; on behalf of Verachten Bruno >>> *Sent:* 29 March 2024 00:58 >>> *To:* jenkinsci-dev@googlegroups.com >>> *Subject:* Re: Adopt email-ext plugin >>> >>> +1 from me. >>> >>> On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins De

Re: Adopt email-ext plugin

Bruno >>> mailto:gount...@gmail.com>> >>> Sent: 29 March 2024 00:58 >>> To: jenkinsci-dev@googlegroups.com <mailto:jenkinsci-dev@googlegroups.com> >>> mailto:jenkinsci-dev@googlegroups.com>> >>> Subject: Re: Adopt email-ext plugin >>>

Re: Adopt email-ext plugin

Verachten Bruno >> *Sent:* 29 March 2024 00:58 >> *To:* jenkinsci-dev@googlegroups.com >> *Subject:* Re: Adopt email-ext plugin >> >> +1 from me. >> >> On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins Developers < >> jenkinsci-dev@googlegroups

Re: Adopt email-ext plugin

achten Bruno > *Sent:* 29 March 2024 00:58 > *To:* jenkinsci-dev@googlegroups.com > *Subject:* Re: Adopt email-ext plugin > > +1 from me. > > On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > > +1 from me

Re: Adopt email-ext plugin

+1 From: jenkinsci-dev@googlegroups.com on behalf of Verachten Bruno Sent: 29 March 2024 00:58 To: jenkinsci-dev@googlegroups.com Subject: Re: Adopt email-ext plugin +1 from me. On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins Developers

Re: Adopt email-ext plugin

+1 from me. On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > +1 from me! > > On Thu, Mar 28, 2024 at 11:58 AM Alex Earl wrote: > >> Howdy, >> >> The email-ext plugin is up for adoption. I'd like to

Re: Adopt email-ext plugin

+1 from me! On Thu, Mar 28, 2024 at 11:58 AM Alex Earl wrote: > Howdy, > > The email-ext plugin is up for adoption. I'd like to re-adopt it (been a > few years so I may be a little rusty :) ) > > RPU pull request: > https://github.com/jenkins-infra/repository-permissi

Re: Adopt email-ext plugin

+1 from me On Thu, Mar 28, 2024 at 9:59 AM Alex Earl wrote: > Howdy, > > The email-ext plugin is up for adoption. I'd like to re-adopt it (been a > few years so I may be a little rusty :) ) > > RPU pull request: > https://github.com/jenkins-infra/repository-permissi

Adopt email-ext plugin

Howdy, The email-ext plugin is up for adoption. I'd like to re-adopt it (been a few years so I may be a little rusty :) ) RPU pull request: https://github.com/jenkins-infra/repository-permissions-updater/pull/3851 <https://github.com/jenkins-infra/repository-permissions-updater/pull/3

Re: email-ext plugin adoption

Hi, On Wed, Oct 10, 2018 at 07:21:53PM +1030, David van Laatum wrote: > The next thing I was planning to do was rip a bunch of stuff out and > put it into a ext-notification plugin that is extendable to allow > multiple backend drivers ie email and slack. As I see most > notification style

Re: email-ext plugin adoption

On Wed, Oct 10, 2018 at 4:52 AM David van Laatum wrote: > most notification style plugins basically implementing the same thing and are > often quite limited unless you use pipelines My (old) thoughts in this area FWIW: https://github.com/jenkinsci/email-ext-plugin/pull/97#issuec

Re: email-ext plugin adoption

unless you use pipelines Sent from my iPad > On 9 Oct 2018, at 6:50 am, Matt Sicker wrote: > > I'd be interested in being a co-maintainer. > >> On Mon, Oct 8, 2018 at 3:07 PM Slide wrote: >> The email-ext plugin is currently up for adoption, looking for &

Re: email-ext plugin adoption

I'd be interested in being a co-maintainer. On Mon, Oct 8, 2018 at 3:07 PM Slide wrote: > The email-ext plugin is currently up for adoption, looking for > co-maintainers. I used to be maintainer of this plugin and would like to > help again. I already have access to release in the r

email-ext plugin adoption

The email-ext plugin is currently up for adoption, looking for co-maintainers. I used to be maintainer of this plugin and would like to help again. I already have access to release in the repository permissions stuff, and I am already part of the permissions groups on GitHub, but I wanted

Re: Email-ext plugin conflicting with token-macro plugin

> On 16.02.2017, at 20:56, Pino Alu wrote: > > Using Jenkins core v 1.625.3 Jenkins 2.16 and up tell you when your plugin configuration is invalid and refuse to load plugins with unsatisfied dependencies. I recommend you upgrade to a recent release. Also, please ask

Re: Email-ext plugin conflicting with token-macro plugin

ror>: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/Run;Lhudson/FilePath;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String; On Thursday, February 16, 2017 at 9:44:08 AM UTC-6, Pino Alu wrote: I am trying to locate which version of Email-ext goes with token-macro > plugin? Currentl

Re: Email-ext plugin conflicting with token-macro plugin

Yes, I installed from plugin manager. Where is the email-ext pom.xml located as I would need another team member to locate it and send to me? On Thursday, February 16, 2017 at 10:23:03 AM UTC-6, slide wrote: > > Did you install via the plugin manager? If so, then the correct version of &

Re: Email-ext plugin conflicting with token-macro plugin

Did you install via the plugin manager? If so, then the correct version of token macro should have been installed. If not, then you need to check the pom file for email-ext and determine from there what version is needed for each dependency. On Thu, Feb 16, 2017, 09:01 Pino Alu <pt

Re: Email-ext plugin conflicting with token-macro plugin

Using Jenkins core v 1.625.3 On Thursday, February 16, 2017 at 9:44:08 AM UTC-6, Pino Alu wrote: > > I am trying to locate which version of Email-ext goes with token-macro > plugin? Currently we have *Email-Ext v2.55* installed and *token-macro > v1.12.1* installed and Email-ext is

Email-ext plugin conflicting with token-macro plugin

I am trying to locate which version of Email-ext goes with token-macro plugin? Currently we have *Email-Ext v2.55* installed and *token-macro v1.12.1* installed and Email-ext is not sending email but the Jenkins mail plugin is configured and works. We receive this error and I feel

Accessing implicit objects in email-ext plugin

Hello! I am writing a plugin that is simply a few classes that I want to be able to access from the pre-send script of the email-ext plugin . . . It's all working pretty well, except that I can't figure out how to access the build, logger, msg & cancel implicit vars from within my own obj

Re: email-ext

e to help with a review of the fix > for since I have history on email-ext, but in general, I am no longer > actively developing on email-ext. > > On Tue, May 31, 2016 at 9:21 PM David van Laatum <da...@vanlaatum.id.au > > wrote: > >> https://issues.jenkins-ci.org/secu

Re: email-ext

Ok, it worked that time. You should be setup to commit and handle issues. There is one issue that I will continue to help with a review of the fix for since I have history on email-ext, but in general, I am no longer actively developing on email-ext. On Tue, May 31, 2016 at 9:21 PM David van

Re: email-ext

t;> Hi All, >>> >>> I've reached a point where I just don't really have the time to continue >>> working on email-ext as much I would like. I am planning on putting it up >>> for adoption on the wiki, but wanted to send a note out to the dev list

Re: email-ext

nday, May 30, 2016 at 5:00:24 AM UTC+9:30, slide wrote: >> >> Hi All, >> >> I've reached a point where I just don't really have the time to continue >> working on email-ext as much I would like. I am planning on putting it up >> for adoption on the wiki, b

Re: email-ext

I will take over unless anyone else really wants to. davidvanlaatum is my userid On Monday, May 30, 2016 at 5:00:24 AM UTC+9:30, slide wrote: > > Hi All, > > I've reached a point where I just don't really have the time to continue > working on email-ext as much I would like

email-ext

Hi All, I've reached a point where I just don't really have the time to continue working on email-ext as much I would like. I am planning on putting it up for adoption on the wiki, but wanted to send a note out to the dev list to see if anyone would like to take it over. If I don't hear anything

Re: Email-ext-hpi plugin upload issue

ce) >> at java.util.concurrent.FutureTask.run(Unknown Source) >> at >> hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) >> at java.lang.Thread.run(Unknown Source) >> Caused by: java.io.IOException: Failed to install em

Re: Email-ext-hpi plugin upload issue

110) > at java.lang.Thread.run(Unknown Source) > Caused by: java.io.IOException: Failed to install email-ext plugin > at hudson.PluginManager.dynamicLoad(PluginManager.java:487) > at > hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1324) >

Email-ext-hpi plugin upload issue

) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Failed to install email-ext plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:487) at hudson.model.UpdateCenter$InstallationJob._run

Groovy template for subject in email-ext plugin

I need help in creating a groovy template for subject in email-ext plugin. I have configured email-ext plugin to send emails on every build failure. I want to check my build log and if it contains text 'abc' then it should set subject to 'ProjectName - failed due to abc' and if it doesn't

Re: email-ext option suggestion

the mail address resolution through all the address resolvers is to add an email address to the user in Jenkins. On Tue, Sep 30, 2014 at 8:40 AM, Venkat Prasad venkat@gmail.com wrote: Hi Slide, We have come across that your email-ext plugin resolves users email address from LDAP

Re: email-ext option suggestion

through all the address resolvers is to add an email address to the user in Jenkins. On Tue, Sep 30, 2014 at 8:40 AM, Venkat Prasad venkat@gmail.com javascript: wrote: Hi Slide, We have come across that your email-ext plugin resolves users email address from LDAP. its takes the lot

Re: email-ext option suggestion

in Jenkins. On Tue, Sep 30, 2014 at 8:40 AM, Venkat Prasad venkat@gmail.com wrote: Hi Slide, We have come across that your email-ext plugin resolves users email address from LDAP. its takes the lot of time to complete job if in case of more recipients. Can you please provide an option

email-ext option suggestion

Hi Slide, We have come across that your email-ext plugin resolves users email address from LDAP. its takes the lot of time to complete job if in case of more recipients. Can you please provide an option not to resolve from LDAP that just appends defaultSuffix? https://github.com/jenkinsci

Re: Custom email-ext triggers for non build-result activities

email-ext has finished its normal process) but we would like be able to send emails based on this event. Just like any other build-failure related item, I foresee each team will have different desires here so it makes sense to use email-ext which excels at this... -- You received

Re: Custom email-ext triggers for non build-result activities

build. That Action is displayed on the results page where users can click to claim or blame ownership of a build break. This will occur at a random time after the build completes (i.e. long after email-ext has finished its normal process) but we would like be able to send emails based

Re: Custom email-ext triggers for non build-result activities

Could email-ext be upgraded to also listen to the post-completion build results pages of anything with an email-ext action then rescan triggers appropriately upon change (understanding there's a lot more details involved than this one-liner)? Is that sensible within the existing framework

Re: Custom email-ext triggers for non build-result activities

As I thought - current functionality cannot react to a build result being further updated post-completion. Is there an extension point whereby email-ext can listen for such post-completion events and then rescan (some?) triggers again (ensuring existing completion-triggers ones don't

Re: Custom email-ext triggers for non build-result activities

No, there is no current extension point for anything like that. email-ext is a Publisher, so it runs after a job completes (or before a job begins), that is all. On Fri, Jun 27, 2014 at 10:01 AM, Marc Carter drekb...@gmail.com wrote: As I thought - current functionality cannot react to a build

Custom email-ext triggers for non build-result activities

-related but can happen literally any time. It might make things simpler to know that email-ext wouldn't *have* to listen for anything. With a suitable entry point - claim could directly invoke the trigger. This isn't very pretty though as it is directly opposed to how the code appears to handle

Re: Custom email-ext triggers for non build-result activities

Triggers are currently only checked after the build completes. They are not triggers in the sens that they can themselves cause an email to be sent. The email-ext publisher basically loops over all the configured triggers, checks if they are triggered and if so sends an email based on the trigger

Re: New maintainer for email-ext

the email-ext plugin anymore. Is there anyone who would be will to take it over and give it the love and attention it needs? Thanks, Slide -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop

Re: New maintainer for email-ext

, June 21, 2014 12:51:11 AM UTC+2, slide wrote: My fifth child was born a couple of weeks ago and I am finding I have no time for maintaining the email-ext plugin anymore. Is there anyone who would be will to take it over and give it the love and attention it needs? Thanks, Slide -- You

Re: New maintainer for email-ext

On Sun, Jun 22, 2014 at 3:56 AM, Jeff MAURY jeffma...@jeffmaury.com wrote: I'm volonteering for helping the email-ext plugin continue its exiting life Jeff On Sun, Jun 22, 2014 at 2:48 AM, Richard Bywater rich...@byh2o.com wrote: First of all congratulations on the new addition. I've

Re: New maintainer for email-ext

Here you go. https://jenkins.ci.cloudbees.com/job/plugins/job/email-ext-plugin/ On Mon, Jun 23, 2014 at 8:37 AM, Jeff MAURY jeffma...@jeffmaury.com wrote: Slide, thank you. I tried to build it both on Windows (files locked) and Linux but both build failed. Is there a public CI server

Re: New maintainer for email-ext

Thanks On Mon, Jun 23, 2014 at 6:06 PM, Slide slide.o@gmail.com wrote: Here you go. https://jenkins.ci.cloudbees.com/job/plugins/job/email-ext-plugin/ On Mon, Jun 23, 2014 at 8:37 AM, Jeff MAURY jeffma...@jeffmaury.com wrote: Slide, thank you. I tried to build it both

Re: New maintainer for email-ext

I'm volonteering for helping the email-ext plugin continue its exiting life Jeff On Sun, Jun 22, 2014 at 2:48 AM, Richard Bywater rich...@byh2o.com wrote: First of all congratulations on the new addition. I've got two and find trouble getting enough time to do things so can't imagine what

Re: New maintainer for email-ext

a maintainer for a Jenkins plugin? (Eg what's a day in the life of a maintainer look like) Richard. On Saturday, June 21, 2014, Slide slide.o@gmail.com wrote: My fifth child was born a couple of weeks ago and I am finding I have no time for maintaining the email-ext plugin anymore

Re: New maintainer for email-ext

Hi Jeff, Do you have commit access already? Thanks, slide On Sun, Jun 22, 2014 at 3:56 AM, Jeff MAURY jeffma...@jeffmaury.com wrote: I'm volonteering for helping the email-ext plugin continue its exiting life Jeff On Sun, Jun 22, 2014 at 2:48 AM, Richard Bywater rich...@byh2o.com

Re: New maintainer for email-ext

for helping the email-ext plugin continue its exiting life Jeff On Sun, Jun 22, 2014 at 2:48 AM, Richard Bywater rich...@byh2o.com wrote: First of all congratulations on the new addition. I've got two and find trouble getting enough time to do things so can't imagine what it's like with 5

Re: New maintainer for email-ext

already? Thanks, slide On Sun, Jun 22, 2014 at 3:56 AM, Jeff MAURY jeffma...@jeffmaury.com wrote: I'm volonteering for helping the email-ext plugin continue its exiting life Jeff On Sun, Jun 22, 2014 at 2:48 AM, Richard Bywater rich...@byh2o.com wrote: First of all

Re: New maintainer for email-ext

. On Saturday, June 21, 2014, Slide slide.o@gmail.com wrote: My fifth child was born a couple of weeks ago and I am finding I have no time for maintaining the email-ext plugin anymore. Is there anyone who would be will to take it over and give it the love and attention it needs? Thanks, Slide

New maintainer for email-ext

My fifth child was born a couple of weeks ago and I am finding I have no time for maintaining the email-ext plugin anymore. Is there anyone who would be will to take it over and give it the love and attention it needs? Thanks, Slide -- You received this message because you are subscribed

Re: Inputting variables into email-ext Default Content to access in Groovy script

I may have answered my own question. Don't use a template. I have instead created a Groovy class and I call it from the Pre-send Script area using the GroovyClassLoader. This allows me to use it with other scripts and creates an incredibly dynamic tool. I can now post to Jive systems via

Inputting variables into email-ext Default Content to access in Groovy script

I have successfully written a well-functioning Groovy script to format my email content for a Jive type social site after the great help from this group. Now, I want others to be able to add or remove parts based on adding a Set of regex patterns that will be applied to the log to eliminate or

How can I replace text in my log using Jenkins email-ext

At work, we use a social networking system based on Jive. We have the ability to email to the service, but it has sever limitations on what characters can be included. We currently manipulate the output via the actual programs we are running, but we want a plugin type solution for Jenkins.

Re: How can I replace text in my log using Jenkins email-ext

Hi Dan, Why break out of the groovy code at that point? Why not just stay in groovy mode? % if(build.result==hudson.model.Result.SUCCESS) { % CONSOLE OUTPUT % build.getLog(1000).each() { line - formatLine(line) }% Does that not work? Thanks, slide On Wed, Nov

Re: How can I replace text in my log using Jenkins email-ext

On 27.11.2013, at 22:30, Slide slide.o@gmail.com wrote: formatLine(line) Missing println probably. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send

Re: How can I replace text in my log using Jenkins email-ext

I think that's basically what the syntax you are using now will do. It outputs the value of the evaluation, so if you are just calling the method, you aren't printing anything, just evaluating and throwing away the result. By ending the groovy context and starting an output/text context, you are

Re: How can I replace text in my log using Jenkins email-ext

I think it all just clicked today how this syntax works. The syntax was a bit confusing at first, and it didn't help that I bounced between Jelly and Groovy for awhile trying to learn both enough to make a determination as to which is better. Groovy seems to be better from what I have learned. I

Re: How can I replace text in my log using Jenkins email-ext

Honestly, I wish Jelly would die a horrible death. I've debugged so many issues trying to do stuff in Jelly, I really wish I could just rip it out of email-ext. I've been pondering writing a converter that converts Jelly templates to Groovy templates and doing just that, but only in my most

Re: How can I replace text in my log using Jenkins email-ext

Jelly would die a horrible death. I've debugged so many issues trying to do stuff in Jelly, I really wish I could just rip it out of email-ext. I've been pondering writing a converter that converts Jelly templates to Groovy templates and doing just that, but only in my most frustrated of times

Enhancement to the email-ext plugin

This is my first post to this group so apologies if I'm not following the usual process for this request. I implemented a new custom (and very simple) trigger for the email-ext plugin and was wondering if it was possible to integrate this into the official plugin. The new trigger is named

Re: Enhancement to the email-ext plugin

: This is my first post to this group so apologies if I'm not following the usual process for this request. I implemented a new custom (and very simple) trigger for the email-ext plugin and was wondering if it was possible to integrate this into the official plugin. The new trigger is named Status

Re: Enhancement to the email-ext plugin

Thanks for the quick reply. I forked the project, committed my changes and issued a pull requested as suggested. Cheers -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it,

Re: Email-Ext plugin throwing junk content

.us/pluginManager/plugin/email-ext/thirdPartyLicenses Below is the log snippet for jenkins log. SEVERE: null hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:494) at hudson.remoting.Request.call(Request.java:129

Re: Email-Ext plugin throwing junk content

Any messages in the Jenkins logs? Also, what versions of email-ext and token-macro do you have? Also, what version of Jenkins? On Wed, Sep 25, 2013 at 2:00 PM, Maneesh M P maneesh.po...@gmail.comwrote: Our jenkins server got reboot today for some reason, after that we started getting mails

Re: Email-Ext plugin throwing junk content

using the version : 2.34http://jenkins.hp10.us/pluginManager/plugin/email-ext/thirdPartyLicenses Below is the log snippet for jenkins log. SEVERE: null hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:494

Re: Email-Ext plugin throwing junk content

Looks like that's why the tokens are not getting replaced. You need to figure out why you're getting that exception. On Wed, Sep 25, 2013 at 3:33 PM, Maneesh M P maneesh.po...@gmail.comwrote: I am using the version : 2.34http://jenkins.hp10.us/pluginManager/plugin/email-ext

Re: Email-Ext plugin throwing junk content

on this slave/master ? On Thu, Sep 26, 2013 at 12:33 AM, Maneesh M P manees...@gmail.comjavascript: wrote: I am using the version : 2.34http://jenkins.hp10.us/pluginManager/plugin/email-ext/thirdPartyLicenses Below is the log snippet for jenkins log. SEVERE: null

Re: Unable to select Triggers in Email-ext plugin

Downgrade to 2.32. https://issues.jenkins-ci.org/browse/JENKINS-19585 On 15.09.2013, at 01:37, Maneesh manees...@gmail.com wrote: Hello, I have the latest 2.33 Email-Ext plugin install. After enabling Editable Email Notification from my build configuration, I clicked on Advanced to add

Unable to select Triggers in Email-ext plugin

Hello, I have the latest 2.33 Email-Ext plugin install. After enabling Editable Email Notification from my build configuration, I clicked on Advanced to add Triggers. I tried clicking on all the triggers [Fixed, Failure, Success etc], but none of the options are appearing on the UI. What

Unable to select Triggers in Email-ext plugin

Hello, I have the latest 2.33 Email-Ext plugin install. After enabling Editable Email Notification from my build configuration, I clicked on Advanced to add Triggers. I tried clicking on all the triggers [Fixed, Failure, Success etc], but none of the options are appearing on the UI. What shall

Re: Unable to select Triggers in Email-ext plugin

I'm releasing an updated version with the fix as soon as the unit tests complete running. On Sat, Sep 14, 2013 at 4:35 PM, manees...@gmail.com wrote: Hello, I have the latest 2.33 Email-Ext plugin install. After enabling Editable Email Notification from my build configuration, I clicked

Email-Ext and Add Watch a la JIRA

I'm looking at implementing an Add Watch feature to the email-ext plugin similar to the Add Watch in JIRA in relation to [1]. The idea itself is not difficult to implement, what I want to get some feedback on is the security scope for this feature. What security level do people think should

Re: Email-Ext and Add Watch a la JIRA

exactly what is required here. Vincent 2013/8/8 Slide slide.o@gmail.com I'm looking at implementing an Add Watch feature to the email-ext plugin similar to the Add Watch in JIRA in relation to [1]. The idea itself is not difficult to implement, what I want to get some feedback

Re: Email-Ext and Add Watch a la JIRA

for all jobs, so anyone that wants to watch a given job just has to flag it as favorite. Otherwise, I think the 'read' permission covers exactly what is required here. Vincent 2013/8/8 Slide slide.o@gmail.com I'm looking at implementing an Add Watch feature to the email-ext plugin similar

Re: Email-Ext and Add Watch a la JIRA

exactly what is required here. Vincent 2013/8/8 Slide slide.o@gmail.com I'm looking at implementing an Add Watch feature to the email-ext plugin similar to the Add Watch in JIRA in relation to [1]. The idea itself is not difficult to implement, what I want to get some feedback

Re: Problem with exclusion list in Email-ext plugin, v2.30.2

connection is currently horrible. slide On Fri, Aug 2, 2013 at 11:06 AM, Ken kennet...@gmail.com javascript:wrote: Version 2.29 of the Email-ext plugin added a global user exclusion list (issue #17503) -- very useful! Even using this list though, I'm still getting email sent to a build pc

Problem with exclusion list in Email-ext plugin, v2.30.2

Version 2.29 of the Email-ext plugin added a global user exclusion list (issue #17503) -- very useful! Even using this list though, I'm still getting email sent to a build pc that shouldn't receive email. I've tried both forms of buil...@domain.com and buildpc in the Excluded Committers area

Re: Problem with exclusion list in Email-ext plugin, v2.30.2

of the Email-ext plugin added a global user exclusion list (issue #17503) -- very useful! Even using this list though, I'm still getting email sent to a build pc that shouldn't receive email. I've tried both forms of buil...@domain.com and buildpc in the Excluded Committers area but no luck

email-ext plugin script not found

Hi, I have a plugin that uses the email-ext plugin and has it as dependency. In my test class i want to get the global configuration page of jenkins with this line of code: final HtmlPage page = new WebClient().goTo(configure); but everytime I get: testProjectAction(org.jenkinsci.plugins.Test

RE: email-ext plugin script not found

That file is provided by email-ext, so it should just be there. Sent from my Windows Phone -- From: Iordan Boev Sent: 3/25/2013 5:23 To: jenkinsci-dev@googlegroups.com Subject: email-ext plugin script not found Hi, I have a plugin that uses the email-ext plugin

Re: Using formatted BUILD_ID in email ext plugin

Hi, I guess it uses the java like timestamp e.g. mmdd-hhmm,etc I am not sure from the code perspective, but, thats how i do it on the jenkins job page. Is there a way to format the build id in the content of the email ext plugin ? Thanks, Alok On Fri, Feb 22, 2013 at 10:48 AM, Slide slide.o

RE: Using formatted BUILD_ID in email ext plugin

Not really, the token does exactly what I said below. Sent from my Windows Phone -- From: alok kumar Sent: 2/22/2013 7:16 To: jenkinsci-dev@googlegroups.com Subject: Re: Using formatted BUILD_ID in email ext plugin Hi, I guess it uses the java like timestamp e.g

Using formatted BUILD_ID in email ext plugin

Hi All, I am trying to use the formatted BUILD_ID in the content of the email-ext plugin, but, it is not able to resolve it. It instead just resolves it to the default format of BUILD_ID, whereas I have changed its format using the zentimestamp plugin. Can someone please help me in getting

Re: Using formatted BUILD_ID in email ext plugin

email-ext uses the following to get the BUILD_ID: build.getId(); How does the zentimestamp plugin modify the build id? On Thu, Feb 21, 2013 at 10:14 PM, alok kumar alok.kuma...@gmail.com wrote: Hi All, I am trying to use the formatted BUILD_ID in the content of the email-ext plugin

Re: Email ext

') On Friday, July 27, 2012 1:00:56 AM UTC+3, aviad lich wrote: Hi All I have written a HelloWorld extension And i want to use the email-ext action to send me data from this HelloWorld action I would like to understand better the entrance point of the jelly script And how can i use it to get my

Email ext

Hi All I have written a HelloWorld extension And i want to use the email-ext action to send me data from this HelloWorld action I would like to understand better the entrance point of the jelly script And how can i use it to get my specific action Thanks

Re: Getting the other publishers are enabled or not in Email ext

have placed my jelly templates in emai-templates folder in Jenkins home..but can't able to access the variables from the java code in email ext plugin...anyone have any idea how to do that Thanks Diptiman -- View this message in context: http://jenkins.361315.n4.nabble.com/Getting-the-other

Re: Getting the other publishers are enabled or not in Email ext

and if that plugin is enabled then the variable value will b true...but I want to access the variable from the jelly template.I am stuck here...I have placed my jelly templates in emai-templates folder in Jenkins home..but can't able to access the variables from the java code in email ext plugin...anyone have