Last Comment Bug 675115 - Add mozilla-release and comm-release to MXR
: Add mozilla-release and comm-release to MXR
Status: RESOLVED FIXED
:
Product: mozilla.org Graveyard
Classification: Graveyard
Component: Server Operations (show other bugs)
: other
: All All
: -- normal (vote)
: ---
Assigned To: Jake Maul [:jakem]
: Corey Shields [:cshields]
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-28 17:55 PDT by Philipp von Weitershausen [:philikon]
Modified: 2015-03-12 08:17 PDT (History)
1 user (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Philipp von Weitershausen [:philikon] 2011-07-28 17:55:44 PDT
Would be handy for identifying back traces thrown by release builds. You know, the software that people actually use ;)
Comment 1 Justin Wood (:Callek) 2012-01-21 06:15:14 PST
Though there is software changes involved in adding this, it is a server ops bug, as it was server-issues that have been preventing any new repos from going into mxr lately.

We'll also need ESR and the hotfix addon-repo to land into MXR soonish, and we STILL have comm-aurora/beta repos to get in.
Comment 2 Jake Maul [:jakem] 2012-01-23 11:43:03 PST
How often do the trees comm-aurora, comm-beta, and comm-release need to be updated in MXR? Is daily good enough?
Comment 3 Jake Maul [:jakem] 2012-01-23 11:59:54 PST
Also worth noting: I'm assuming the proper update procedure for this is the same as MXR uses for comm-central, comm-1.9.1, and comm-1.9.2 (and comm-2.0 now, which I'm doing simultaneously):

    print LOG `cd $src_dir; $TIME python2.4 ./client.py checkout $STDERRTOSTDOUT`;

If that's not correct for some reason, please let me know what it should be. Of course I had to do a simple 'hg clone' initially just to get that file, but I'm assuming this does more than just that. If nothing else, it seems to do an hg clone of a different repo inside itself.
Comment 4 Justin Wood (:Callek) 2012-01-23 12:41:57 PST
(In reply to Jake Maul [:jakem] from comment #2)
> How often do the trees comm-aurora, comm-beta, and comm-release need to be
> updated in MXR? Is daily good enough?

Daily should be good enough for comm-release, I would prefer same timing as mozilla-aurora/beta for comm-aurora/beta though, but worse comes to worse, 1 day is ok.

I had filed Bug 653424 with a patch for the comm aurora/beta stuff which seemed to have problems getting it deployed, so if you do it all in this bug, we can probably consider that one a dupe (or vice-versa)

(In reply to Jake Maul [:jakem] from comment #3)
> Also worth noting: I'm assuming the proper update procedure for this is the
> same as MXR uses for comm-central, comm-1.9.1, and comm-1.9.2 (and comm-2.0
> now, which I'm doing simultaneously):
> 
>     print LOG `cd $src_dir; $TIME python2.4 ./client.py checkout
> $STDERRTOSTDOUT`;
> 

Yes that is fine, though there is thoughts/ways we could improve this for comm, to be more tolerant against breakages in client.py itself, this will have us working just fine.
Comment 5 Jake Maul [:jakem] 2012-01-23 13:15:38 PST
mozilla-aurora and mozilla-beta are both daily. I don't actually see mozilla-release in MXR...

Aurora and Beta are completed (just now) in bug 653424. Comm-release has now completed as well. All 3 are scheduled for daily processing.
Comment 6 Jake Maul [:jakem] 2012-01-23 13:41:21 PST
Missed mozilla-release... which it looks like maybe we need l10n-mozilla-release also, at least for consistency with aurora and beta.
Comment 7 Jake Maul [:jakem] 2012-01-23 14:05:45 PST
This is completed, but still processing... should be done in an hour or less. Scheduled for daily updating.

Note You need to log in before you can comment on or make changes to this bug.