Task #11372 (closed)
CI nodes should alert us to ERROR-level server log entries
Reported by: | mtbcarroll | Owned by: | spli |
---|---|---|---|
Priority: | minor | Milestone: | 5.x |
Component: | General | Version: | n.a. |
Keywords: | hudson, jenkins | Cc: | omero-team@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
When one of our CI deployments (howe, gretzky, etc.) has OMERO logging actual errors, some mechanism should bring this to our attention.
(Quite possibly, the integration test suite should somehow also detect ERROR log entries, but perhaps some tests are expected to cause them?)
Change History (4)
comment:1 Changed 11 years ago by jamoore
- Owner changed from jamoore to spli
comment:2 Changed 9 years ago by spli
- Resolution set to invalid
- Status changed from new to closed
Moved to Trello
comment:3 Changed 9 years ago by mtbcarroll
A link to the card would be welcome.
comment:4 Changed 9 years ago by mtbcarroll
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Simon has setup a bot which does this quite well, posting ERROR (and WARN if desired) messages to a chat room. I'd argue this is as good as anything else, unless we want a hudson job which periodically does the same thing and actually goes red which we'll have to handle during the standup.
Comments?