Status: Open (View Workflow)
Jenkins 2.62 on Windows 7, 64bit. All plugins updated to latest versions (full systemInfo attached)
After a recent upgrade on Jenkins and all plugins the rich-text publisher behavior has changed.
A build page (i.e. /job/rich_text_test/) shows the text published from the last successful build, even if the last build failed.You have to go to a specific build page (i.e. /job/rich_text_test/14/) to see the actual text.
The text I'm publishing is the breakdown of the build results, so I need the text on the build page to always be that published by the last build.
I've tried every combination of the settings under 'Advanced' and it does the same, I've tested with a stripped down build with the same results.
It definitely did work previously, if the new behavior is deliberate then I'd like an option to have the old behavior enabled.
tarazed I'm sure it is a plug-in or configuration problem – sadly it's a minor problem I don't have time to go through the steps of enabling/disabling all our plugins. If I was going to do that I'd start by focusing on other post-build actions and the interaction there.
I had hoped it would work with a newer version (since it did definitely work with older versions) but I've upgraded everything recently and it's still the same.
I just found a "useLastStable" parameter in the [RichTextPortlet|https://javadoc.jenkins.io/plugin/rich-text-publisher-plugin/index.html?org/korosoft/jenkins/plugin/rtp/RichTextPortlet.html] class ，but as far as I know，this class is only used for "Dashboard View" plugin.
It seems like when it publishes text to the job page, it also behavors in the "useLastStable" mode，which is confusing.
We find a way to bypass this bug.
Using "Execute Shell" - "Advanced" - "Exit code to set build untable"，you can change a fail result to an unstable result.
In this condition, the text can be displayed on the job page.
tarazed – awesome! Thanks for sharing the workaround, that's really helpful for us.
I encounted the same problem, but it seems most people are not affected by this.
Is it possible that this plugin conflicted with some other plugin?