Suggestion on auto ticket filing
talklists at newgeo.com
Tue Dec 1 14:29:12 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?
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?
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.
Scott * If you contact me off list replace talklists@ with scott@ *
On Nov 26, 2009, at 9:46 PM, Jeremy Lavergne wrote:
> 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.
> On Nov 27, 2009, at 12:37 AM, Scott Haneda wrote:
>> In a past message on MP-users, subject of: Re: "Electric" failed to
>> compile, Ryan suggested the use of:
>> sudo port -d install electric 2>&1 | tee ~/Desktop/electric.txt
>> Then asked:
>>> Then file a new ticket in the issue tracker and attach
>>> electric.txt from your desktop.
>> I have been wondering this for a while, and this is a good intro
>> for me to ask...
>> As a result of any error in MacPorts, a message is written to the
>> terminal of what the error was. What if the last line was:
>> You may want to try the troubleshooting steps located at: http://trac.macports.org/wiki/FAQ#buildfails
>> Though I would like to point to a new wiki page, where it was much
>> more orderly, a set of steps to try. I see a lot of requests that
>> are answered with "did you clean and try again", "yeah, I did, that
>> worked, thanks".
>> Maybe that entire dialog could go away, with the pointing of a url
>> at the very end of the error message. Then, within the new wiki
>> page, I would add the "If all else fails...".
>> sudo port -d install portname 2>&1 | tee | mp-reporter
>> * Not sure I have that correct.
>> The idea is, that the output is passed to a small shell script, mp-
>> reporter, which would automatically create the report in the
>> ticketing system. We would need one account for which this
>> happened under.
>> I would like to make the mp-reporter script interactive, so if
>> desired, they could login to trac right there, and the ticket would
>> be made under their account. Or they can decline, and it will be
>> made under the general mp-reporter account.
>> I believe this is something within my abilities to create. I think
>> it can be done with curl and some pretty simple bash scripting.
>> Filing the ticket with the output as an attachment, over putting it
>> into the ticket itself is up for discussion, and would be the only
>> aspect of curl I am not familiar with off the bat.
>> Scott * If you contact me off list replace talklists@ with scott@ *
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
More information about the macports-dev