Task #3694 (new)
Opened 9 years ago
Last modified 3 years ago
Log parser for all hudson jobs
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Deployment | Version: | n.a. |
| Keywords: | n.a. | Cc: | jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
There should be a single description of what log statements should look like which hudson should always parse. For example:
ome-log-start.file-xyx:File opened ... ome-log-end.file-xyz:File closed
should balance. If the log parser detects that a close never happened, then the build should fail.
Similarly, for:
ome-log-perf.block-import.filetypeA:<any message here> ... ome-log-perf.block-import.filetypeB:<any message here>
could be used to show graphs of imports of "filetypeA" over time, as well as comparisons between filetypes.
Change History (5)
comment:1 Changed 9 years ago by jmoore
- Cc jburel added
- Component changed from General to Deployment
- Milestone changed from Unscheduled to OMERO-Beta4.3
- Priority changed from minor to major
comment:2 Changed 8 years ago by jmoore
- Milestone changed from OMERO-Beta4.3 to Unscheduled
Moving to Unscheduled since we are approaching the 4.3 freeze.
comment:3 Changed 7 years ago by jmoore
Referencing ticket #1736 has changed sprint.
comment:4 Changed 3 years ago by sbesson
Referencing ticket #11622 has changed sprint.
comment:5 Changed 3 years ago by sbesson
Referencing ticket #11622 has changed sprint.
An initial version of this can be started quite soon. May be useful for performance testing big images. The results could then get displayed as graphs on hudson.