I went looking for the vcsMappings config file, and noticed that it's in application.php, which says "Application-specific settings separate from installation concerns." This is wrong, since these should be configured per-installation. (The values in there are only really valid for Mozilla, and even then they don't account for SeaMonkey.) Can we get these values moved elsewhere, so we can add entries on the production copy without having to update the code there? Specifically, we'll need to add an entry for the 1.9.1 repo once we're done, something like: 'hg' => array( 'hg.mozilla.org/mozilla-central' => 'http://hg.mozilla.org/mozilla-central/annotate/%(revision)s/%(file)s#l%(line)s' 'hg.mozilla.org/releases/mozilla-1.9.1' => 'http://hg.mozilla.org/releases/mozilla-1.9.1/annotate/%(revision)s/%(file)s#l%(line)s' )
Summary: vcsMappings config needs to live in install-specific config file → vcsMappings config needs to live in install-specific config file (no source links to 1.9.1 on crash-stats)
Hey guys -- Not being able to see source links in 1.9.1 is making it pretty hard to tell if crashes in similar code are identical or not, and slows down analysis of them. Would be great to get this fixed soon, let me know if I can help.
Severity: normal → major
(To be clear, while I like the sound of the architectural fix here, I'll take any gross and smelly hack that makes the 1.9.1 source links work in the interim.)
Checked in a fix r1176. Filed IT ticket to stage change.
Status: NEW → ASSIGNED
Code is on stage.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
That doesn't seem to have fixed my original request in this bug, since I still have to file a Socorro bug and not an IT bug to get this updated, which is why bug 510918 is languishing and we don't have source links for 1.9.2 now.
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.