Closed Bug 855567 Opened 11 years ago Closed 10 years ago

provide way to filter job logs by repository

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Unassigned)

References

Details

(Whiteboard: [re-vcs-sync])

Attachments

(1 file)

Attached file new python script
python script to pull detailed logs regarding a particular repository.

use case: researching issue which impacted one repository at an unknown time. I.e. where the history of actions on one repository are required, and the job supports many repositories.

For example, the detailed log file for l10n repos is in excess of 20M lines, of which only about 

Note that detailed output includes stdout & stderr - so relevant lines may not contain a reference to the repository, hence grep not a solution.

Note that deploying on current production boxes will require adding the argparse library, as only python 2.6 is on production.
Attachment #730469 - Flags: review?(aki)
Attachment #730469 - Flags: review?(aki) → review+
deployed on all production machines

Some environment changes needed, those are documented in http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/dd099cf49d0c
 - added argparse to the python virtual env
 - put symlink to virtual env's python in ~/bin

Work done for legacy system. Not resolving to serve as marker for functionality in production system.
Product: mozilla.org → Release Engineering
Looks like this is done for legacy?
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
correct - was left open to ensure in new system.
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: