github / maven-plugins

Official GitHub Maven Plugins
MIT License
584 stars 198 forks source link

blob 404 error againI #25

Closed malachid closed 11 years ago

malachid commented 11 years ago

It appears that v0.7 has the same problem as these:

https://github.com/github/maven-plugins/issues/10 https://github.com/github/maven-plugins/issues/12 https://github.com/github/maven-plugins/issues/13

It was deploying fine, then I merged everything to master. It failed. I deleted the directory in the gh-pages branch and tried redeploying. It has not been successful. It will usually push the parent documentation, and fail on the first submodule.

[INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.7:site (default-cli) on project api: Error creating blob: Not Found (404) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.github:site-maven-plugin:0.7:site (default-cli) on project api: Error creating blob: Not Found (404) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating blob: Not Found (404) at com.github.maven.plugins.site.SiteMojo.createBlob(SiteMojo.java:279) at com.github.maven.plugins.site.SiteMojo.execute(SiteMojo.java:337) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.eclipse.egit.github.core.client.RequestException: Not Found (404) at org.eclipse.egit.github.core.client.GitHubClient.createException(GitHubClient.java:516) at org.eclipse.egit.github.core.client.GitHubClient.sendJson(GitHubClient.java:600) at org.eclipse.egit.github.core.client.GitHubClient.post(GitHubClient.java:679) at org.eclipse.egit.github.core.service.DataService.createBlob(DataService.java:115) at com.github.maven.plugins.site.SiteMojo.createBlob(SiteMojo.java:275) ... 22 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :api Build step 'Invoke top-level Maven targets' marked build as failure Finished: FAILURE

kevinsawicki commented 11 years ago

Is this for a public repository and if so, can you share the URL to it and which branch you saw this error when trying to build?

It should show the exact repository being used if you run with the -X flag.

malachid commented 11 years ago

It's not public yet. I built and generated the site on master. Then when I did ghSite:site, it started to deploy and failed on the first module. Deleting the destination directory from gh-pages didn't fix it.

kevinsawicki commented 11 years ago

And you are seeing the expected repository being used with the -X flag logged and you are using credentials that have access to that repository?

malachid commented 11 years ago

Yesterday, it was publishing everything just fine -- parent and submodules.

After changing from the branch to master, it now pushes the parent fine, but the submodules get 404.

Nothing was changed in the pom or source -- just changed which branch Jenkins was told to build.

Since it does push the parent documentation, and it is only configured in one place...

kevinsawicki commented 11 years ago

There were server issues with the API yesterday as mentioned here.

Can you see if this is still an issue now that the API is fully operational again?

malachid commented 11 years ago

I can't access CI until Monday. I'll try it then.

malachid commented 11 years ago

Still not working.

[INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 44.605s [INFO] Finished at: Mon Dec 03 08:07:09 PST 2012 [INFO] Final Memory: 12M/554M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.7:site (default-cli) on project api: Error creating blob: Not Found (404) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :api Build step 'Invoke top-level Maven targets' marked build as failure ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.reflect.UndeclaredThrowableException at $Proxy41.getIOtriplet(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.(Launcher.java:851) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:798) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:866) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:616) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1460) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:127) at hudson.remoting.Channel.call(Channel.java:646) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) ... 16 more project=hudson.maven.MavenModuleSet@170a1d1[sdk-android-2] project.getModules()=[hudson.maven.MavenModule@1c03289[sdk-android-2/com.playhaven.android:api][sdk-android-2/com.playhaven.android:api][relativePath:api], hudson.maven.MavenModule@1c07a8d[sdk-android-2/com.playhaven.android:providers][sdk-android-2/com.playhaven.android:providers][relativePath:providers], hudson.maven.MavenModule@87325f[sdk-android-2/com.playhaven.android:sampleapp][sdk-android-2/com.playhaven.android:sampleapp][relativePath:sampleapp], hudson.maven.MavenModule@1b0fb8[sdk-android-2/com.playhaven.android:sdk][sdk-android-2/com.playhaven.android:sdk][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@1b0fb8[sdk-android-2/com.playhaven.android:sdk][sdk-android-2/com.playhaven.android:sdk][relativePath:] FATAL: null java.lang.reflect.UndeclaredThrowableException at $Proxy41.getIOtriplet(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.(Launcher.java:851) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:798) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:866) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:616) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1460) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:127) at hudson.remoting.Channel.call(Channel.java:646) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) ... 16 more

kevinsawicki commented 11 years ago

Can you share the output of the site-maven-plugin when running with the -X option?

kevinsawicki commented 11 years ago

Closing this out, the issue was the project name being used did'n't correspond to the right repository when the API calls were made.