-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: continuous integration
Hey sebastian.menski lipphardt,
I want to discuss something.
With the help of the database purging we can ensure that each test runs with a clean database.
We still have random failing test cases. Maybe it will be useful that we can track all failing jobs in the history. So perhaps we can detect a pattern to fix this issues.
I would suggest to throw the successful jobs from the history (perhaps collect only the last successful one) and save the last 5 or 10 failing jobs.
Is this even possible and make this sense for you guys?
Greets,
Chris
