github / maven-plugins

Official GitHub Maven Plugins
MIT License
587 stars 197 forks source link

Error creating tree: Not Allowed (405) #114

Open awoods opened 8 years ago

awoods commented 8 years ago

When using the goal com.github.github:site-maven-plugin:0.12:site the following error is thrown:

[INFO] --- site-maven-plugin:0.12:site (github) @ fcrepo ---
[INFO] Creating 1,351 blobs
[INFO] Creating tree with 1,351 blob entries
[INFO] Merging with tree 0edd9e967bd10188e1d43d49ccc24ab15397ad44
...
[ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.12:site (github) on project fcrepo: Error creating tree: Not Allowed (405) -> [Help 1]

It appears that committing a tree with 1,351 blobs exceeds a GitHub limit. To resolve the issue, I used the following patch to break the large commit into smaller bundles (500 blobs per commit).

I would not be surprised if others also run into this issue. I would be happy to backport this patch to use Java5 and/or create a plugin configuration element that specifies the size of commit bundles. https://github.com/github/maven-plugins/pull/113

sheeper commented 7 years ago

Possibly the same problem here:

[INFO] Creating 976 blobs
[INFO] Creating tree with 976 blob entries
[INFO] Merging with tree 762123d977207b4486a9a31384ea1e6a3cb3b770
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 49:43 min
[INFO] Finished at: 2016-11-27T20:55:10+01:00
[INFO] Final Memory: 12M/166M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.12:site (default) on project cactus-site: Error creating tree: Not Allowed (405) -> [Help 1]

reran with username/password just in case the oauth token has not enough rights. Now the error is:

[INFO] --- site-maven-plugin:0.12:site (default) @ cactus-site ---
[INFO] Creating 976 blobs
[INFO] Creating tree with 976 blob entries
[INFO] Merging with tree 762123d977207b4486a9a31384ea1e6a3cb3b770
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 49:22 min
[INFO] Finished at: 2016-11-27T22:52:30+01:00
[INFO] Final Memory: 12M/178M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.12:site (default) on project cactus-site: Error creating commit: Invalid request.
[ERROR]
[ERROR] For 'properties/name', nil is not a string.
[ERROR] For 'properties/name', nil is not a string. (422)
[ERROR] -> [Help 1]

After all i am surprised what the plugin does here. Creating a commit manually and pushing that didn't take longer than 1minute, while the site plugin... well you see it above.

gowthamraj07 commented 7 years ago

I am also getting the same error, but only with 23 blobs, any possible ways to make it work?

[INFO] Creating 23 blobs
[INFO] Creating tree with 23 blob entries
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] PROJECTNAME ............................................. FAILURE [01:21 min]

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:22 min
[INFO] Finished at: 2017-03-08T10:35:45+05:30
[INFO] Final Memory: 22M/209M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.12:site (default) on project <PROJECTNAME>: Error creating commit: Invalid request.
[ERROR] 
[ERROR] For 'properties/name', nil is not a string.
[ERROR] For 'properties/name', nil is not a string. (422)
awoods commented 7 years ago

The resolution/pull-request to the original topic of this issue has been backported for Java5 compatibility.