If you can figure out how to change the Jenkins bot emoji to the given
ones, I'd love to improve it. I wasn't able to get any emojiIcon
parameter to work, but perhaps you need to create a custom Slack bot
token rather than using the default one.

On Sat, 11 Apr 2020 at 11:15, Michael Shuler <[email protected]> wrote:
>
> Bravo for the Simpsons emoji usage in slack messages. I think we should
> steal this, Mick :)
>
> Warm regards,
> Michael
>
> On 4/11/20 10:23 AM, Matt Sicker wrote:
> > To elaborate further, if you look through the global variables available,
> > you should be able to obtain all the info you’d use in a Jelly template
> > without the maintenance hassle.
> >
> > On Sat, Apr 11, 2020 at 10:21 Matt Sicker <[email protected]> wrote:
> >
> >> If you use a pipeline, you can make it say whatever you want. Example:
> >> https://github.com/apache/logging-log4j2/blob/master/Jenkinsfile
> >>
> >> On Sat, Apr 11, 2020 at 07:40 Mick Semb Wever <[email protected]> wrote:
> >>
> >>> Have any other projects customised the format of the email body that
> >>> jenkins sends?
> >>>
> >>> Using the emailext plugin, the email content can be defined by a jelly
> >>> script, and there's a few from that plugin to pick from.
> >>>
> >>> See for example
> >>> https://github.com/apache/cassandra/blob/trunk/.jenkins/Jenkinsfile#L354
> >>>
> >>> I'd like to fix and improve a few things in the default text.jelly
> >>> template. The builds emails for the Cassandra pipeline are pretty
> >>> messy, an example
> >>>
> >>> https://lists.apache.org/thread.html/r137dce26f7623146c0c19cc6d5bcc1c801e3e4ba8a5098ffcd3eec4a%40%3Cbuilds.cassandra.apache.org%3E
> >>>
> >>> According to the instructions at https://plugins.jenkins.io/email-ext/
> >>> I need to provide the customised template (jelly or groovy) to the
> >>> jenkins administrator to be placed under
> >>> `$JENKINS_HOME/email-templates/`
> >>>
> >>> Is this approach a possibility? Is there any other solution that's been
> >>> used?
> >>>
> >>> regards,
> >>> Mick
> >>>
> >> --
> >> Matt Sicker <[email protected]>
> >>



-- 
Matt Sicker <[email protected]>

Reply via email to