Juan Pablo Aroztegi wrote: > I rise a discussion from the IRC channel to this list: > > In the process of building a continuous integration system in > erp/devel/pi, there are some decisions to be taken. In this case, what > do we do if a changeset breaks the build or does not pass the tests? I > suggest backing out that changeset. The "hg backout" command applies the > reverse patch of that changeset. > > There might be some corner cases where a later changeset may depend on > that faulty changeset. I think that those situations should be handled > manually. > > What do you think? Do you see any problems to this?
Main problem i see is that we cannot determine functional dependency between changesets. Example is when a later changeset needs the changeset we want to backout for correct function but not for compilation. It is in general impossible to detect this situation and backing out the old changeset could go unnoticed and create bigger problem then not backing out a changeset at all. Stefan ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
