522681 - Please start indexing releases/comm-1.9.1 on mxr

Status: VERIFIED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Mark Banner (:standard8)]

Bug 522460 is setting up http://hg.mozilla.org/releases/comm-1.9.1

Please can this be indexed on mxr as well.

I believe mxr runs client.py, if so, it shouldn't need any extra arguments (I don't know if it has any on comm-central at the moment).

Comment 1

[Mark Banner (:standard8)]

I just remembered, we'll be swapping the comm-central builds to pull mozilla/ from mozilla-central not mozilla-1.9.1, so do we need a further change to change the "Hg Log" and "Hg Blame" links?

Comment 2

[Mark Banner (:standard8)]

Oh and if you hadn't seen we're expecting to formally branch on Thursday 22nd.

Comment 3

[Dave Miller [:justdave]]

Can you point me at instructions for how to make an initial checkout of this? (and the proper way to update it as well?)

Comment 4

[Mark Banner (:standard8)]

https://developer.mozilla.org/en/Comm-central_source_code_%28Mercurial%29
https://developer.mozilla.org/En/Simple_Thunderbird_build

In essence, an initial checkout is:

  hg clone http://hg.mozilla.org/comm-central/ src
  cd src
  python client.py checkout

To update the checkout:

  cd src
  python client.py checkout


For 1.9.1 replace http://hg.mozilla.org/comm-central/ with http://hg.mozilla.org/releases/comm-1.9.1/

Note that until we formally branch tomorrow, pulling comm-central and then doing python client.py checkout will currently get mozilla-1.9.1. You can override that with --mozilla-repo=http://hg.mozilla.org/mozilla-central/. Alternately just wait for us to branch comm-central in which case client.py will archive the old mozilla/ directory and replace with a new clone of mozilla-central.

Comment 5

[Dave Miller [:justdave]]

OK, so for best performance on MXR I need to wait until you actually branch before I set this up.

Comment 6

[Mark Banner (:standard8)]

(In reply to comment #5)
> OK, so for best performance on MXR I need to wait until you actually branch
> before I set this up.

We've now done the branch - comm-central will pull mozilla-central, comm-1.9.1 will pull mozilla-1.9.1.

Comment 7

[Mark Banner (:standard8)]

Just to note: http://mxr.mozilla.org/comm-central has switched itself to mozilla-central, and is now reporting .mozilla-1.9.1/ which is the archived directory, this will obviously need cleaning up.

Comment 8

[Dave Miller [:justdave]]

So if I push this out tomorrow, the instructions in comment 4 are still valid?

Comment 9

[Mark Banner (:standard8)]

(In reply to comment #8)
> So if I push this out tomorrow, the instructions in comment 4 are still valid?

Yes.

Comment 10

[Serge Gautherie (:sgautherie)]

(In reply to comment #7)
> Just to note: http://mxr.mozilla.org/comm-central has switched itself to
> mozilla-central, and is now reporting .mozilla-1.9.1/ which is the archived
> directory, this will obviously need cleaning up.

Bug 522460 comment 11.

Comment 11

[Dave Miller [:justdave]]

Deployed.  http://mxr.mozilla.org/comm-1.9.1/

Will probably be a couple hours before you have a searchable index though.  Currently set to update daily.

Comment 12

[Mark Banner (:standard8)]

This isn't quite right:

http://mxr.mozilla.org/comm-1.9.1/source/mozilla/config/milestone.txt

shows 1.9.3a1pre which indicates it is pulling in mozilla-central.

(In reply to comment #4)
> Note that until we formally branch tomorrow, pulling comm-central and then
> doing python client.py checkout will currently get mozilla-1.9.1. You can
> override that with --mozilla-repo=http://hg.mozilla.org/mozilla-central/.
> Alternately just wait for us to branch comm-central in which case client.py
> will archive the old mozilla/ directory and replace with a new clone of
> mozilla-central.

Hmm, I wonder if this confused you, the --mozilla-repo override was only needed in the comm-central version before we did the branch. Apologies if it did confuse you.

Also, I don't yet see comm-1.9.1 on http://mxr.mozilla.org/ - does that get automatically added at some stage?

Comment 13

[Dave Miller [:justdave]]

I didn't use that option because I was under the impression that you already branched, so I didn't need it anymore.

However, reviewing my command line history, it looks like I forgot to swap the repo name, and indeed did check out comm-central :|

(In reply to comment #12)
> Also, I don't yet see comm-1.9.1 on http://mxr.mozilla.org/ - does that get
> automatically added at some stage?

No, that has to be done manually, too.  I forgot that one.  I just added it.

The repo is checking out again now, I'll close the bug again when it completes.

Comment 14

[Dave Miller [:justdave]]

OK, source has been re-checked out.  It's indexing now.  As before, it may be an hour or so before search works.  milestone.txt reads 1.9.1.5pre now.

Comment 15

[Reed Loden [:reed]]

(In reply to comment #13)
> (In reply to comment #12)
> > Also, I don't yet see comm-1.9.1 on http://mxr.mozilla.org/ - does that get
> > automatically added at some stage?
> 
> No, that has to be done manually, too.  I forgot that one.  I just added it.

If you're editing mxr's source code, please either file a MXR bug with a patch or commit the change to the mxr repo (http://hg.mozilla.org/webtools/mxr/) yourself. Having local patches is not fun and just leads to problems in the future.

Comment 16

[Serge Gautherie (:sgautherie)]

(In reply to comment #10)
> (In reply to comment #7)
> > Just to note: http://mxr.mozilla.org/comm-central has switched itself to
> > mozilla-central, and is now reporting .mozilla-1.9.1/ which is the archived
> > directory, this will obviously need cleaning up.
> 
> Bug 522460 comment 11.

Please, do delete '/.mozilla-1.9.1' backup dir from comm-central working copy.

Comment 17

[Dave Miller [:justdave]]

(In reply to comment #16)
> Please, do delete '/.mozilla-1.9.1' backup dir from comm-central working copy.

There is no such directory on the filesystem.  Where you do see it?

Comment 18

[Serge Gautherie (:sgautherie)]

(In reply to comment #17)
> Where you do see it?

Example:
[
http://mxr.mozilla.org/comm-central/find?text=&kind=text&string=%2F%5C.cvsignore%24

...
/directory/c-sdk/.cvsignore
/.mozilla-1.9.1/dbm/tests/.cvsignore
...
]

Comment 19

[Dave Miller [:justdave]]

Ahhh...  comm-central, not comm-1.9.1.  You confused me by reopening this bug about it.  This bug is about comm-1.9.1, not comm-central.

It's gone.  The search entries should disappear on the next indexing pass.

Comment 20

[Serge Gautherie (:sgautherie)]

V.Fixed