I have a plan for the 'send to Red Hat' Report plugin, which I've
(finally) named 'RHUpload', please let me know if you see any
problems. Originally this plugin was going to talk directly to
Issue-Tracker, but for several reasons it's better if this is
generalized to working with any ticketing system. In general the
plugin will work by asking the user for the ticket number to upload
this report to; taring, compressing, optionally encripting, and FTPing
the report to RH; then showing the user a block of text about the
report to paste into their ticket. Doing it this way will make it
work for any current and future ticketing systems, and doesn't
preclude haveing the plugin talk directly to a particular ticketing
system in the future.
RHUpload will be a sub-class of CReporter. When invoked it ask the user
to enter a ticket number, customer name, and whether or not they want the
upload to be encrypted. The "customer name" field will be populated with
a customer name configured into the RHUpload.conf file. When the user
responds, it will create CDebugDump entries for ticket number and customer
name that the user gave. It will then put all the CDebugDump entries into
individual files in a tarball, compress and optionally encrypt the tarball,
and then show the user a block of text about the report to paste into their
ticket. This block of text will contain, the filename of the tarball sent
to Red Hat, the md5sum, and the encryption key.
Again, if you see any problems, or can suggest improvements, I'd like to
hear about them.
I've started thinking about the 'send report to Red Hat' plugin (which
is the IssueTracker plugin reworked to take into account all of RH
support's ticketing systems).
This plugin needs to know what ticket and ticketing system the user
want's to attach the crash report to. Ideally ABRT would ask the user
this info at 'report' time (at the point that the user pushes 'report'
in the Gui). Currently the Gui asks for a 'Comment', but in this case
we need to have the Gui ask for different information depending on the
needs of the Reporter plugin.
In order to ask for this kind of information, the Gui needs to know what
Reporter plugins is going to run, and more importantly what information
that Reporter wants from the user. Any thoughts on the best way to get
this info to the Gui?