Apologies in resurrecting this thread again, just to close off the last point I raised an issue on JIRA for token macro integration for mail-ext.
Regarding the Warnings plugin - is there anyway I can access warning information for the current build from a mail-ext groovy template by using the hudson/jenkins model API? Or would I use the token macro expansion plugin in some way? I was wondering if there was a documented way of gaining access to the WarningsResult and WarningsResultAction so I could access the getSummary method from within the mail template (or iterate over other information if necessary)? On 27 January 2012 13:00, Slide <[email protected]> wrote: > I am kind of the maintainer for email-ext, it currently does not support the > token macro plugin, please file an issue in JIRA. > > On Jan 27, 2012 4:19 AM, "Ulli Hafner" <[email protected]> wrote: >> >> On 01/27/2012 11:32 AM, Darren Syzling wrote: >> >> On 27 January 2012 10:19, Ulli Hafner <[email protected]> wrote: >>> >>> I'm not sure if (and how) the email-ext plug-in can read the tokens from >>> the token macro plug-in. Are the other tokens from the token maco plug-in >>> working in email-ext? >>> >>> Ulli >>> >> >> To be honest I hadn't checked any other tokens from the token macro >> plugin. The warnings plugin suggested that it needed token macro to work and >> I'd assumed that internally Jenkins had a way of describing tokens that all >> plugins and the build system could use and mail-ext was using this common >> mechanism. >> >> I'd envisaged a common publishing mechanism whereby any plugin could >> publish tokens (err ignoring namespace/name clashing issues) that could be >> used from the build information and mail-ext could just include this >> information within the mail template. >> >> May be my assumption is completely wrong and hence why it doesn't work. I >> really wanted any build warnings to be highlighted as part of the CI email - >> rather than having to check the build information through the web dashboard. >> >> >> Darren >> >> >> Well, I'm not sure if that is already working in that way with the >> email-ext plug-in. When I provided support for tokens in my warnings plug-in >> I asked about support in the email-ext plug-in but got no response so far: >> >> http://jenkins.361315.n4.nabble.com/Are-there-consumers-of-the-token-macro-plug-in-td3449023.html >> >> The email ext plug-in is also not yet listed as consumer on >> https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin >> >> BTW: I'm not sure if the email-ext plug-in has a maintainer in the moment, >> I remember some discussions quite some time ago. >> >> Ulli >> >> > -- Regards Darren
