433926 - Set up buildbot for weave

Status: RESOLVED WONTFIX

(Firefox :: Sync, defect, P2)

Description

[Dan Mills [:thunder]]

Builds for windows, mac, and linux.

Comment 1

[Chris Beard]

moving this to 0.3

Comment 2

[Armen [:armenzg]]

(reply regarding email received Sep.15th)
There is more than these 2 steps but would
1) what are the shell commands to generate what you want?
2) what is the .mozconfig used?

I think that bhearsum could point you to which master.cfg file to start hacking

Comment 3

[Dan Mills [:thunder]]

(In reply to comment #2)
> (reply regarding email received Sep.15th)
> There is more than these 2 steps but would
> 1) what are the shell commands to generate what you want?

https://wiki.mozilla.org/Labs/Weave/Building

Basically, on an appropriately-configured machine (with build-deps installed):

hg clone http://hg.mozilla.org/labs/weave weave
cd weave
make sdkdir=/path/to/gecko-sdk xpi

> 2) what is the .mozconfig used?

Weave does not build mozilla.  No mozconfig is used.

Comment 4

[Dan Mills [:thunder]]

These bugs need to be triaged, removing 0.3 milestone setting.

Comment 5

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #3)
> (In reply to comment #2)
...
> Basically, on an appropriately-configured machine (with build-deps installed):
...
Dan, do you have a wiki page somewhere of exactly what build-dependencies (aka "tool chain"?) do you need installed on the machine?

Comment 6

[Dan Mills [:thunder]]

We have this:

https://wiki.mozilla.org/Labs/Weave/Building

Though it's a bit out of date.

Basically you need the gecko sdk and a xulrunner app (e.g. firefox).  On mac, you need a merged ppc+intel sdk, there is a script to merge them in the weave sources.

Comment 7

[Mike Connor [:mconnor]]

https://wiki.mozilla.org/User:Mconnor/WeaveSourceReorg/BuildDocs covers the new build system.  I don't think we need to rebuild the crypto module on buildbot, at this point, so it's the unit test pieces that matter.

Comment 8

[Michael Kohler [:mkohler]]

This is a mass change. Every comment has "assigned-to-new" in it.

I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.

Comment 9

[Mike Connor [:mconnor]]

We intend to deprecate the add-on, so this is no longer needed.

Also, we now have a services branch for integrating changes to Fx4, see http://tbpl.mozilla.org/?tree=Services-Central