Hi Sathiyan, > 2) Developer n, Developer o, Developer p has pushed their solution as > changeset x, changeset y and changeset z respectively. chageset x, > changeset y and changeset z are all faulty one, Since those were pushed to > PI after some minutes to changeset w as changeset w is faulty. However > changeset x, changeset y and changeset z those are not necessarily faulty > one, if we consider their push alone. Poll will pick up chageset one by > one, it suggest all changesets are faulty after changeset w. Am I valid? This is right. It is tested as a whole, so it will keep trying and testing till it finds a changeset that passes all the tests.
> 3) All changeset are faulty after any faulty one, may be act as faulty, > since we have single header concept in Mercurial before push. So our > decision of pushing right changeset to main will be struggled. We push the changesets indidually. But we won't push a changeset without including thre previous ones. So if w is faulty and the later x, y, z are good changesets, they won't be pushed till a new aaa changeset comes that solves the problem of x and passes all the tests. When that happens w,x,y,z and aaa will be pushed to main. > 4) Assume now we have fixed issue which has created by changeset w. > Solution been pushed which has been created as "changeset aaa". Now we > have to start push from PI to Main. Where to start from? we should not > miss to push changeset x, y and z (whatever has come after chageset w). Right, as described in the last paragraph. > 1) All developers should do testing (what our continuous build does - > should be exactly same) before push to repository. I completely agree. > 2) If we got any notification for faulty one from build system, we should > not push till the re-fix happened. > waiting queue will be lengthy one, if we get settled fix of faulty changeset. Yes, we'll wait no matter how long the list is. Thank your for the comments. Juan Pablo ------------------------------------------------------------------------------ _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
