Collecting change set takes too long when doing a build

When a new build is setup for the first time (the BazaarSCM discovers that there is no .bzr file), there is no point in collecting the entire set of changes (which in some projects this will be thousands of revisions). I think changes on a build server is only useful between builds. Therefore for the first build we mostlikely don't need to show all the previous changes.

Also checking out a large project (like the bzr-trunk) for the first time can really take a long time.
-------------------------------------------------------------------------------------
Proposal:

If .bzr directory is missing (First time around)

It then does a "bzr branch --stacked". The does a "bzr bind". This will effectively only branch the minimum revisions (top revision atleast) and doing a bind will convert it to checkout for future use.
For the change log we leave it empty (or the following can be executed: "bzr xmllog -r-1") But leaving it blank is probably ok.

If .bzr directory exists (normal operation):
The updates carry on as normal.
If the changeLogLimit is set, then I propose that instead of limiting it to the first N revisions, the limit should apply to the last N revisions. i.e "bzr xmllog -r-N" and not "bzr xmllog -l N"

Please let me know if my proposal is fine, I'm keen to implement it.

Hi Craig,

Sounds good!

What do you think of leaving this as the default behaviour and adding an option to import the full history on the first build (the current behaviour).

Regards,

Hi Guillermo

>>adding an option to import the full history on the first build (the current behaviour).
Sounds good, hoping to work on it soon

undo status change if not suitably fixed