|
||||||||
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 |
[JIRA] (JENKINS-15307) Trigger badge images broken when Jenkins is installed at non-root context
ke...@vervewireless.com (JIRA) Wed, 26 Sep 2012 11:07:52 -0700
- [JIRA] (JENKINS-15307) Trigger badge images... ke...@vervewireless.com (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... bat...@batmat.net (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... bat...@batmat.net (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... ke...@vervewireless.com (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... bat...@batmat.net (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... bat...@batmat.net (JIRA)
- [JIRA] (JENKINS-15307) Trigger badge i... bat...@batmat.net (JIRA)
Tomcat 7, but as you're no doubt aware, would probably happen with any container. As a temporary workaround, I created a small webapp comprised solely of badge images and deployed it to the root context (which is testimony to how handy I think your plugin is!).
The "Green Ball" plugin had the same defect in its early days. While I doubt the fix is all that complicated, if I'm mistaken, perhaps you can use that as a reference.