Executing Jenkins email-ext plugin not as last post-build action

Question

I am using the email-ext plugin v.2.38.1 (post-build action "Editable Email Notification") on Jenkins v.1.566 to send e-mails after the build when certain conditions are met.

When using multiple post-build actions, I got the impression that the email-ext plugin always comes last and is executed after all other actions, no matter how I put the order of actions in the configuration. Other plugins respect the order and are executed accordingly as described in this issue.

Is there any possibility to execute another post-build action after sending the e-mails? In my case, I would like to run a shell script doing some clean-up in the workspace which cannot run before because it will delete a file that is part of the e-mail body.

One could work around this by defining an extra clean-up job which is triggered after the main job is completed, however, I would prefer having everything defined in one job only.

Answer 1

The emailing is a publishing action which occures always after build and post build actions ..

Additionally I think you should clean something before running the job (at startup eventually) but never at the end.

How can you study your issues if you destroy all materials that should enable you to do so ?

Answer 2

Editable Email Notification步骤始终在构建后操作中最后执行，但您可以使用Editable Email Notification Templates步骤，该步骤可以按照您在构建后操作中指定的顺序执行