Closed aantonczak closed 1 year ago
This seems to be a serious issue. I ran into the same problem with Java 17. The cause seems to be that there's some illegal reflection access happening here, which has been blocked off since Java 17. As far as I can tell, this issue in the plugin extensively corrupts information about builds that used Allure. All affected builds lost most information, including having their state set to false and their date to 0 (1970-01-01).
Wow, Java 17 finally meets Jenkins. I'll take a look
fyi, I was using the Jenkins docker image jenkins/jenkins:2.361.2-lts-jdk17
Jenkins and plugins versions report
Environment
Jenkins: 2.361.2 Allure: 2.30.2 Allure Commandline: 2.19.0 Java: jdk-18.0.2What Operating System are you using (both controller, and any agents involved in the problem)?
Windows 10
Reproduction steps
Step1: I installed the Allure plugin via Plugin Manager in Jenkins. Step2: I set up the allure-commandline in Global Tool Configuration Step3: I added post-build action (Allure Report) in my Job Configuration Step4: I executed my test Step5: I checked the generated Allure report in Jenkins Step6: I restarted the Jenkins Step7: I try to open the same Allure report as in step 5
Expected Results
I should be able to open the Allure reports after Jenkins restart.
Actual Results
After Jenkins restart, all build history with Allure's reports disappears. When I try to open the report, I get a 404 Not Found error.
Anything else?
After build execute, I get the following error in the Jenkins Log: