I think the BM's work load is hard now. The build job is really a time killer.
Tuesday, I do a test about multi-shadow with a variant. I do many collateral work for shorten test time.
I tested two variant,
the first variant have a normal shadow, and I manully created another shadow for the variant. then do build and lint check at the same time.(over one hour)
I created two shadows workarea for the second variant. then do build and lint check at the same time.(one ahd half hour).
I skiped over the hard ware test because I haven't the hard ware.
Do contsync for the four variant ( parallel )use 2 hours, build use 3 hours. So the test use time about 6 hours. That day , I was over time until 10:38 pm. when I left, another test building still running.
Tuesday, I do a test about multi-shadow with a variant. I do many collateral work for shorten test time.
I tested two variant,
the first variant have a normal shadow, and I manully created another shadow for the variant. then do build and lint check at the same time.(over one hour)
I created two shadows workarea for the second variant. then do build and lint check at the same time.(one ahd half hour).
I skiped over the hard ware test because I haven't the hard ware.
Do contsync for the four variant ( parallel )use 2 hours, build use 3 hours. So the test use time about 6 hours. That day , I was over time until 10:38 pm. when I left, another test building still running.
If BM only check two variant everyday, use two shadow worarea to shorten build time, he totally need 4 hours.
If we build failed, then we should chek the log, let developers change code. build again. it will use more than 4 hours.perhaps 8 or ?
one day if we only check two variants , may be the build manager can promote a baseline. but if he had to check more variants, and he only have one computer, it is really hard. time is limited.
if we have 6 variant to test.........and if they build failed at first............