There is a need for separate "Shutdown" and "Restart" messages. When an update requires a restart, there is the this usual brutal and un-friendly "Shutdown" message scarring my users. Jenkins should be able to make a difference between "shutdown" and "restart".
Tried the Lenient plugin. But that does not solve the case with "native" Jenkins restart message when for instance a plugin update forces a restart. Lenient is YAWOR (yet another way of restarting), separated from the built in. Not integrated with. Still the brutal "Jenkins is is going to shutdown".
All of above. Wording, hardcoded somewhere. And also no distinction made between shutdown and restart. Only a shutdown message. My users got scared thinking I would end the service. When all I did was update plugins.
The worst part of the message is the "shutdown" part. I also got calls from users "why the Jenkins is shutting down" when this absolutely wasn't true...
To me the best solution would be a default message (maybe the shutdown one) being displayed as long as not specified otherwise and the ability to override this somehow.
The worst part of the message is the "shutdown" part. I also got calls from users "why the Jenkins is shutting down" when this absolutely wasn't true...
To me the best solution would be a default message (maybe the shutdown one) being displayed as long as not specified otherwise and the ability to override this somehow.
Maybe the menu item shouldn't even read "Prepare for shutdown" but "Cease all operation" instead?