|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Great. Thanks for the feedback!
Maybe, but it would be a nice-to-have. I know how reliable the Jenkins community is at remembering to do things on time...![]()
Sure, that definitely sounds reasonable. I hadn't seen your plugin before; it makes sense.
I'm not sure I fully understand what you mean. I was thinking that Jenkins would periodically fetch the messages.json (or whatever) file, like it does with update-center.json. Jenkins would determine which notifications must be shown (if any) and would then render them to the page, for admin users. i.e. Most stuff happens server-side, though with some client-side JS to make notifications look nice / be dismissable.
If you don't ever allow Jenkins online, we can't really download timely notifications (like security advisories) from the server. Or do you mean that these messages should reach Jenkins via the browser-proxy method? Or something else?![]()