-
Notifications
You must be signed in to change notification settings - Fork 20
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
Error run report allure #131
Comments
We had the same trouble. As turned out the large report size caused the problem. The solution is to expand size in nginx bamboo settings. |
We have the exact same issue in Bamboo 7.0.4. The plugin needs to be properly migrated to Bamboo 7.x, the API method signatures changed. @beteshnik I don't know how nginx settings could solve this, the only way to not run into this issue is that the Allure task is not even executed. What was the exact error message that you got? |
We have the exact same issue in Bamboo 7.1.2 |
Same here, will you fix it? |
We are getting this error with the following: Allure plugin version: 1.14.0 I saw the same error was present for Issue 196. In that issue it was suggested to set "Allure binary base url" to https://github.com/allure-framework/allure2/releases/download/ for versions >= 2.13.1, which we have done. I was thinking that this would have been resolved between versions 2.13 & 2.14 of the plugin. We are finding that the report does get created, but the job is failing with the exception:
|
Still very much happening. Any updates or resolution ETA? |
Allure plugin version: 1.10
Bamboo version: 7.0.2 build 70015
Allure agent version: 2.7.0
Error message:
The text was updated successfully, but these errors were encountered: