|
||||||||
|
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.
I expect that some installs aren't allowed through proxies. As we probably want to reserve these notifications for The Really Important Stuff, it should also reach users of those installs.
So my suggestion is to have a small(ish) JS in Jenkins that directs the user's browser to query subdomain.jenkins-ci.org and download the current project notifications, which are then shown somewhere on the UI. Similar to browser-based UC, with the difference that this cannot really break Jenkins, as there's no need to POST this back to Jenkins. It can all be done client-side.