Report of the first successful build after a failed one

- All comments are incorectly makerd as new ones in the table since the current report is compared with an empty one.
- If the previous build contains no data, the diffing will be skipped and only the current report displayed.
- Diff status is set to unchanged by default instead of null.
Report summary of the first failed build

- The summary marks all comments as solved in failed builds which is incorrect.
- Code updated to not store any data for the failed builds.
Report summary before the first build

- If a job is created and no build exists yet, clicking on the link in the menu will redirect the user to an empty page.
- Fixed to redirect the user to the previously displayed job page in such case.
- A new page with an info message would be better, but this is much simpler and good enough for such corner case.
Report summary fixed

- Incorrect numbers are displayed in statistics for concrete patterns, global numbers were used.
- Log messages updated in publisher.
First successful build after a failed one

- Trend graph is not displayed.
- Summary diff is not computed.
- Report diff is not computed.
- getPreviousAction() and getPreviousReport() updated to search a valid action/report in all previous builds instead of checking only the last one.
Diff of statistics resulting in zero pattern's comments

- If number of pattern's occurrences goes to zero, the pattern won't be listed in the summary and the trend graph will be incorrectly transparent in that part instead of color.
- Computing of summary updated to considers all patterns in both current and previous statistics.
- Displaying of trend graph now considers all patterns defined in all builds for each data set.