-
Notifications
You must be signed in to change notification settings - Fork 69
An error occurred while running semantic-release: { Error: spawn ENAMETOOLONG #91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you provide the logs with the full stacktrace? And a link to your repo? And your semantic-release configuration? |
For information the problem is that at least one of the file the plugin is trying to commit is too long to be handled by Node. There is no much we can do here. |
Here is the stacktrace for the semantic-release. 2018-11-01T08:30:32.4551740Z ##[section]Starting: Yarn semantic-release Dear Angular and Ember CLI users, please check our known issues Here is the config for the semantic release. |
Somehow it seems a lot of files, or files with very long names are globbed. and when passed to Can you run semantic-release with the --debug option and provide the logs? That should show what files are actually resolved via glob. |
2018-11-01T16:39:08.4967176Z ##[section]Starting: Yarn semantic-release --debug Dear Angular and Ember CLI users, please check our known issues |
So it seems that around 800 files are resolved from the glob. See the line Are you sure your configuration for Is it intentional? Do you really want to commit all those files in the |
I don't get why the dist would be configured. It's not included in the assets of the config. |
I tested again and I don't see how the files in |
I just released |
Greetings! Sorry for answering but I've been away. The config file seemed to have some issues & and now it seems to be working properly. Thank you for all the answers! |
This is still a problem. It will happen, when The error message is mis-leading, it it not about the length of the filename, but about the maximum length of passed arguments as well. All occurrences in the code, where basically unrestricted amount of data is passed to For |
I ran into this issue when trying to add semantic-release to an existing project. It generated a changelog file of over 2k lines which fails on ubuntu. Is there any way to reduce this or truncate the commit message in the event it does end up too long? |
While they don't merge the pull request that fixes it, a workaround is removing |
Greetings! What could be the problem?
Current behavior
On the prepare step, the git plugin commits with fails
Expected behavior
The git plugin should pass during the build.
Environment
semantic-release version: v15.10.6
semantic-release/git: v7.0.5
The text was updated successfully, but these errors were encountered: