On Thu, Apr 16, 2009 at 11:52 AM, ant elder <[email protected]> wrote: > I'm wondering if its got to the stage where we need to do something about > our builds as they take too long and are always broken. >
This is very simmilar to what I have proposed in [1] [1] http://www.mail-archive.com/[email protected]/msg02236.html > The continuum builds almost never work, nor does a local build for me > usually, its got to the stage i think people often don't even bother trying > one before committing which is just exasperating the problem. Even on the > rare occasions when it is building cleanly it takes so long to run i'm > guessing most of us often don't run a build before committing anyway, and > one of the reasons there's seldom a completed 1.x continuum build is that it > takes so long it often gets killed before it finishes. > It' s really a shame to hear that people just dump code to trunk without building, I think we should rethink this. > Right now the 1.x build takes over 70 minutes for me (and continuum), i'd > like to have a go to get that down to under 30 minutes or better. Disabling > the schema validation makes a difference but not enough so i'd like to start > taking things out of the build. I know that sounds a bit drastic but we've > quite a lot of stuff that has never been included in a release, or hasn't > been touched in ages, some doesn't even have any tests so we're just burning > time compiling with no idea if its doing anything useful. > > I don't have a list, it would be easier to spend time on and off moving > things out as they're discovered, so would anyone object if this happened > CTR and anything can get put back if theres an issue? > For some suggestions, see http://www.mail-archive.com/[email protected]/msg02236.html Last time I tried this CTR approach, I was asked to revert couple changes, so I don't think a simple CTR will work. See http://markmail.org/message/fypdpbffir4ghwoz > Longer term i think we should think about separating some parts out into > separate builds and releases. Does any want to help or have any other ideas > about how to speed things up and get a more stable build? > We should think carefully about this, consider what we have in 2.x today, where we are having to release various plugins everytime we need to do a release. Also, if it's the other way around, where we never need to touch the code, it might get forgotten. I gues I would like to see a concrete plan of what goes where, before I could make my mind. -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
