MXR needs to handle better

Assigned to


9 years ago
6 years ago


(Reporter: Matthew Gertner, Assigned: timeless)


Firefox Tracking Flags

(Not tracked)




9 years ago
See The MXR repository for the project is here: It doesn't look like it's been updated since November or so.


9 years ago
Assignee: server-ops → reed
Our svn repo is too large... the way we're currently handling this isn't working. Need to work with timeless to come up with a better solution.

Comment 2

9 years ago
tentatively, this is probably a combination of:

find . -name trunk -type d |xargs -n1 svn up

and some magic at the top level to "discover" new roots

i'm told there's an svn bot which has some intelligence for that...
Assignee: reed → nobody
Component: Server Operations → MXR
Product: → Webtools
QA Contact: mrz → mxr
Summary: MXR still isn't being updated for webrunner project → MXR needs to handle better

Comment 3

9 years ago
I'm using MXR as documentation for the Prism API right now. It's therefore even more important that the repository be up to date. Is there any chance we can get the automatic update working?
timeless and I discussed this. Need to recursively look through directory for .svn and similar directories. Update those and not recurse it, etc...
Assignee: nobody → timeless

Comment 5

8 years ago
Did we ever come to a conclusion on this? Would it be possible at least to run the update again manually? It doesn't look like it's been updated for a year or so, so MXR is very out-of-date with respect to the sources in SVN.
You need to log in before you can comment on or make changes to this bug.