You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Release Notes

Issues discovered in testing

Issues discovered in testing:

Discovered byIssuebbdbnw
Andy

The only issue I’ve found so far is that the looping task producers emit an error to STDERR on every run. I have set up cron jobs to run the loopers daily and send us an email if there are errors, so now we’re receiving this error for every looper every day.

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.springframework.cglib.core.ReflectUtils$1 (file:/var/lib/duracloud/auditlog-generator.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of org.springframework.cglib.core.ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

This is a known issue with Spring and Java 9+. https://github.com/spring-projects/spring-framework/issues/20414




Testing of Completed Issues

Itembbdbnw

Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Regression Testing

Taskbbdbnw
Perform Regression Tests


Use ZAProxy to perform a security analysis
  • Use a test DuraCloud account with very little content
  • Start an Automated Scan
  • Remove any sites not relevant to DuraCloud from the "Sites" list
  • Generate an HTML and XML report and attach to this page



Build Tests

Testbbdbnw
mvn clean install (full build + integration tests) - DuraCloud DB




mvn clean install (full build + integration tests) - DuraCloud


mvn clean install (full build + integration tests) - Management Console


mvn clean install (full build + integration tests) - Mill


mvn clean install (full build + integration tests) - Snapshot



Release Actions - for each baseline (in this order): DB, DuraCloud, MC, Mill, Snapshot


  • No labels