Importd basic OOPS reporting

Registered by David Allouche

The Buildbot-based importd will provide basic oops reporting.

As discussed with SteveA, OOPS reporting will be done in two places:
 1. loading of jobs from the database, on the botmaster side
 2. job completion on the botmaster side, just record failure of an import without trying to record details of the cause of the failure.

In particular, the exception causing a failure or the job log will not be recorded in the oops if they are difficult to retrieve on the botmaster side at job completion time.

Blueprint information

Status:
Complete
Approver:
Steve Alexander
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
David Allouche
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
David Allouche
Completed by
David Allouche

Related branches

Sprints

Whiteboard

Last week, I have fixed the importd test environment so I can successfully run it locally, so I will be able to manually test the oops reporting. -- David Allouche 2007-04-04

Implemented the oops reporting code. Now pending review. -- David Allouche 2007-04-11

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.