[JIRA] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Kevin Bond commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server release 0.13.1 contains the fix. 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Kevin Stone commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server I got bit by this too. I was able to recover my Jenkins by copying the backup jpi and restarting Jenkins. cd /var/lib/jenkins/plugins sudo cp github-oauth.bak github-oauth.jpi sudo service jenkins restart 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Johno Crawford commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Until I have time to look into the problem I have reverted my last commit and created a new 0.13.1 release, please accept my apologies. 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Peter Miklosko commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server No, just organization golden account 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Johno Crawford commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Are you using GitHub Enterprise? 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Kræn Hansen commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server I can confirm this issue. It blocked me right after the upgrade. 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Bradley Wagner commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Yea, confirmed here too. Thanks for the quick steps to resolve, Mark Takacs! 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Mark Takacs edited a comment on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Good grief, this is terrible! as a workaround, i was able to go to http://updates.jenkins-ci.org/download/plugins/github-oauth/ download 0.12 service jenkins stop rm -rf ~/plugins/github-oauth* cp /tmp/github-oath-0.12.hpi ~/plugins/github-oauth.jpi ## converted from .hpi to .jpi service jenkins start To save unsuspecting users, maybe you could unpublish 0.13. or if that's not possible, publish 0.14 (renamed from 0.12) so anyone pulling down updates doesn't get a bad one. 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Mark Takacs edited a comment on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Good grief, this is terrible! as a workaround, i was able to go to http://updates.jenkins-ci.org/download/plugins/github-oauth/ download 0.12 service jenkins stop rm -rf ~/plugins/github-oauth* cp /tmp/github-oath-0.12.hpi ~/plugins/github-oauth.jpi ## converted from .hpi to .jpi service jenkins start 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Mark Takacs commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Good grief, this is terrible! 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Juan Basso commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server You can disable the authentication in the config, restart and re-configure to another auth system until the it get fixed. To disable the authentication, go in the box, jenkins folder, edit the jenkins.xml. Change the key "useSecurity" to false, and delete the key "authorizationStrategy" completely. Restart the jenkins and all users will be administrator, so go in manage and setup wherever you want, except github oauth Btw, don't forget to backup your configuration file (jenkins.xml) before change it. 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Kevin Bond commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Also having this issue, how can I revert the plugin? 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
James Smith commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Same here - I've just set up the github oauth plugin on a new server, and am having exactly the same error after github login. 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] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Juan Basso updated JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server I am having the same issue. I can't access the jenkins web interface at all. Change By: Juan Basso (28/Jan/13 2:56 PM) Priority: Major Blocker 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, send email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Peter Miklosko
created JENKINS-16492
Upgrade from 0.12 to 0.13 breaks server
Issue Type:
Bug
Affects Versions:
current
Assignee:
Michael O'Cleirigh
Components:
github-oauth
Created:
25/Jan/13 6:01 PM
Description:
Got 500 after upgrade from 0.12 to 0.13
Exception: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: java.io.StringReader@5e5e32a1; line: 1, column: 2]
Stacktrace:
org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: java.io.StringReader@5e5e32a1; line: 1, column: 2]
at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433)
at org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521)
at org.codehaus.jackson.impl.JsonParserMinimalBase._reportUnexpectedChar(JsonParserMinimalBase.java:442)
at org.codehaus.jackson.impl.ReaderBasedParser._handleUnexpectedValue(ReaderBasedParser.java:1198)
at org.codehaus.jackson.impl.ReaderBasedParser.nextToken(ReaderBasedParser.java:485)
at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2770)
at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)
at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)
at org.kohsuke.github.Requester.parse(Requester.java:300)
at org.kohsuke.github.Requester._to(Requester.java:173)
at org.kohsuke.github.Requester.to(Requester.java:139)
at org.kohsuke.github.GitHub.getMyself(GitHub.java:200)
at org.kohsuke.github.GitHub.(GitHub.java:102)
at org.kohsuke.github.GitHub.connectUsingOAuth(GitHub.java:149)
at org.jenkinsci.plugins.GithubAuthenticationToken.(GithubAuthenticationToken.java:68)
at org.jenkinsci.plugins.GithubSecurityRealm.doFinishLogin(GithubSecurityRealm.java:313)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.ChainedServletFilter$1.d
