Suggestion on auto ticket filing
jeremy at lavergne.gotdns.org
Tue Dec 1 14:38:52 PST 2009
> Can you tell me more about the gsoc project wrt MacPorts? Where do I find the log? I can force a portfile to fail, or look at some others that have, where do I find those logs?
It's in the trunk version: when there's an error it'll report where it put the log.
>> The gsoc logging project assists us in that the log is already available---no more need to rerun with debug mode.
>> It also provides the path to the log file (copy/paste into Finder).
>> As for the port field and ticket owner, we can likely have a script auto-assign (and CC) the ticket based on the port field, and we could require the port to be set for ports-based tickets (the default, type I believe).
>> These requirements should cause people to read the instructions since the tickets won't submit without making sure they've added the port, but it will also remove the need for them to mark the owner.
>> While we're at it, we might consider logic to test that the reporter/owner isn't a CC.
> From what I can gather, your comments below are speaking towards 100% automated ticket submissions on port install error? Or are you saying, that after a failed install, and some general guidance to a wiki/troubleshooting page, that the steps the user take would auto submit a new trac ticket, which in turn, a script could fish out some details and make the ticket more relevant?
The ticketing process is currently not automated, but my ideas were geared toward the creation of such a system. I feel most of the information can be gleaned from the server's database and port can fire up a terminal window with a specific URL to trigger an auto-population of the form (e.g., `open http://trac.macports.org/...port=...mpversion=1.8.99...`).
Ultimately, I would like to aim for port to POST the log to trac, with a ticket ID returned. Then port will open a URL to trac which will display the ticket pre-populated as much as we can and referencing that log.
> Sorry, had the flu, and am catching up, and also a little cloudy still, reading over your post, I am not sure I entirely follow what you mean, but would love to work on making this a reality. If you could help bring me up to speed on what you envision, maybe there is a chance my skill set falls in range with the work needed to be done.
Basically we need to plan both the server-side URLs and the ability to open such URLs directly from MacPorts. It isn't something that can be done on one side only.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4024 bytes
Desc: not available
More information about the macports-dev