Need lots more information. This works for me in my setup at work. Need the config.xml for the job and the global xml for email-ext from JENKINS_HOME

Can you also provide a build log?

Hi Alex,

Below is the build log content.

Started by user anonymous
RHODESVERSION 5.0
Finished: SUCCESS

Regards,
Manoj

Can you enable debug mode in the global config for email-ext and run again?

No change in build log after enabling debug mode.
It's same
Started by user anonymous
RHODESVERSION 5.0
Finished: SUCCESS

Regards,
Manoj

Then it looks like the email-ext plugin is not being called.

Hi Alex,

I don't know what does it mean email-ext plugin is not being called.
I'm sure you might have gone through the project config.xml i have attached earlier.
and it is clearly shows email-ext plugin is configured with equird fiels.

If you still feel I have missed something in configuration please let me know.
Appreciated if you let me know atleast how to call email-ext.

Regards,
Manoj

Hi Alex,

One small observation.
The email-ext works fine for different free-style project on same Jenkins.

Regards,
Manoj

Sounds like the build flow job type is not running the publishers.

Anything additional plugin or any setup configuration to be done?

I'm not familiar with build flow, so I'm not sure.

np. thanks.

Regards,
Manoj

Hi Alex,

if possible can you please assign it some one who can help me on Build flow..

Thanks
Manoj

I already did

Thanks.

Hi Alex,

If you cannot provide solution, never mind.
Please don't alter the issue i have logged.

If at all you want to modify at least assign it to proper components category.

Regards,
Manoj

I removed the email-ext component since the issue is not with email-ext. This is a common practice.

Not sure how this will effect. But my earlier problem was on Email-ext plugin + Bluid flow plugin.
The Buildflow project was not sending mails after build completion.

Regards,
Manoj

Based on the build log you provided, the build flow plugin is not initiating the email-ext plugin.

Not sure, but try enabling the workspace.
<buildNeedsWorkspace>false</buildNeedsWorkspace>

I see the same for Build other projects and even trigger parameterized build plugin in post build actions. Does this mean, none of the post build actions are triggered when using a Build flow job type?

I have never tried build-flow + other things in post build since all the parameterized triggering and so forth is done in the DSL for me.

I have tested "Build other projects" and at least that is not executed unless "Flow run needs a workspace" is checked. And this seem to be the case for all post build actions.

It seems that Flow run needs a workspace should be turned on automatically if there are any publisher to avoid this confusion.

I agree with Oliver. After update, jobs with post build steps stopped working and it took some time to realize it - because build did not fail. User should be at least warned because there is no sense to have post-build steps without "Flow run needs a workspace".

I confirm that Flow run needs a workspace solve the issue!
It's quite annoying as bug