Can you identify which plugin release was the last version you used which did not truncate?

I see the truncation, but rather assume it has been that way for a long time.

I think that truncation is not unreasonable, considering the recommendation for 50/72 formatting on stackoverflow, linux kernel recommendations, Chris Beams blog, Tim Pope's blog, and Caleb Thompson. I'm not aware of a change which intentionally truncated the commit message for display, but I see the truncation is happening.

Thanks for the comment Mark. As you can see from the screenshot the truncation has been introduced recently (sometime this year, took me a while to notice).

I have tried a few versions back to 2.2.6 but it still happens there. I will try and ask the Apache folks which versions they are running.

I'm not persuaded that it happened in the last year, since 2.2.6 was released Sep 2014 and you indicate that it is already there in 2.2.6. My initial suspicion is that the version which does not truncate is from the 1.x release series from a long time ago. However, I'm open to being proven wrong on that.

You could very well be correct, yes. Next chance I get I'll try to downgrade to a 1.x version.

I've tried 1.5 and you're correct: That does not truncate.

So I have a workaround for now but to me this still seems undesirable and like a bug. If you do agree - and I'm not sure about that - I'm happy to take a look at the code to see if I can find what's going on.

I prefer the current behavior of only showing a reasonable subset of the commit message in the UI presentation. My rationale is captured in my earlier comment on this bug. Other maintainers may have a different opinion, but for me, I prefer the truncation that was implemented in the 2.0 plugin rather than returning to the 1.0 unlimited length string behavior.

Thanks Mark. Shall I close the issue then?

(It seems as if 1.5 doesn't always work as it used to either, so I'll have to find alternatives to Jenkins anyway)

I think you should close the issue. If you're passionate about not truncating and willing to invest some effort in the plugin, you could consider creating a separate plugin (to add the behavior for those users who want it) or an optional extension of the current plugin which would modify the behavior to never truncate the change log message.