[JIRA] [parameterized-trigger-plugin] (JENKINS-28908) Subjob completion not detected
Title: Message Title Milijan Mudrinic commented on JENKINS-28908 Re: Subjob completion not detected Thanks for the update Bernd Spickers. I seem to have fixed the issue by manually deleting the javadoc.jpi.disabled and maven-plugin.jpi.disabled files in the jenkins Plugin folder. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [parameterized-trigger-plugin] (JENKINS-28908) Subjob completion not detected
Title: Message Title Milijan Mudrinic commented on JENKINS-28908 Re: Subjob completion not detected I have the same issue but I am unable to enable the Maven Integration plugin which I presume is what you mean. The pop-up message suggest that the Javadoc Plugin plugin in disabled, which I can also confirm but I don't have an option to enable it as it is greyed out. I am running 1.655 jenkins with quite a lot of other plugins (inc those mentioned in this bug report). I'd like to get the warning pluging working so any suggestions would be much appreciated. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [htmlpublisher] (JENKINS-16090) Cannot access published results page via links in prior builds
Milijan Mudrinic edited a comment on JENKINS-16090 Cannot access published results page via links in prior builds Note sure if it'll help anyone but I find that if I use a literal in the "page to index" field (e.g. test.log) instead of a wild card (e.g. *.log) it fixes the issue... Unfortunately it doesn't help me. This works: http://localhost:8080/job/Test/10/HTML_Report/test.log This doesn't and generates Error 500: http://localhost:8080/job/Test/10/HTML_Report/*.log Now that I have the dev environment running, I'll try to figure out the issue but I doubt it'll be quick since I don't know much. sight 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/groups/opt_out.
[JIRA] [htmlpublisher] (JENKINS-16090) Cannot access published results page via links in prior builds
Milijan Mudrinic edited a comment on JENKINS-16090 Cannot access published results page via links in prior builds Note sure if it'll help anyone but I find that if I use a literal in the "page to index" field (e.g. test.log) instead of a wild card (e.g. *.log) it fixes the issue... Unfortunately it doesn't help me. This works: http://localhost:8080/job/Test/10/HTML_Report/test.log as well as http://localhost:8080/job/Test/HTML_Report/*.log This doesn't and generates Error 500: http://localhost:8080/job/Test/10/HTML_Report/*.log Now that I have the dev environment running, I'll try to figure out the issue but I doubt it'll be quick since I don't know much. sight 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/groups/opt_out.
