Had a thought regarding the lack of testability for non-released components in AS. The chicken-egg dilemna is: * We can't validate a release until it passes AS and TCK TestSuites * We can't integrate into AS until a component is released So we work around this by releasing, crossing our fingers, and re-releasing if a problem pops up. Some hack idea is: * Create "component-matrix-continuous" with parent of "component-matrix" * c-m-c may define versioned SNAPSHOTs in the depMgt section, overriding those defined by c-m. * Make a property to set the artifactId of the parent of thirdparty POM to the continuous build: > ./build.sh -Dcontinuous=true ...then we can set up Hudson runs to test versioned SNAPSHOTs to catch errors that may be coming down the line without affecting the normal build. WWJD?

Jason T. Greene wrote: > Hmm. The thing I wonder though is how useful this will be if you start > pulling in everyone's snapshots. You will probably end up with > incompatible combinations. We'd have to curtail this by saying "you can put SNAPSHOTs here, but on a limited basis and then take 'em out".

For instance, right now we'd have VFS and some other related stuff in Branch_5_0 only. When those SNAPSHOTs being tested are released, the snapshot override is removed.

> It's probably more useful if every team has their own manual or > automated integration run. This could either be snapshot based via > some kind of maven override, or could be a temporary branch created > off the main AS branch that includes the changes. I'd rather roll the dice on incompatible combinations than set us up for even more custom runs and branches.

Already we have a geometric problem: Number of TestSuites (AS, TCK, EJB3, etc) * AS Branches

On 02/19/2009 01:04 PM, Jason T. Greene wrote: > Andrew Lee Rubinger wrote: >> Jason T. Greene wrote: >>> Hmm. The thing I wonder though is how useful this will be if you >>> start pulling in everyone's snapshots. You will probably end up with >>> incompatible combinations. >> >> We'd have to curtail this by saying "you can put SNAPSHOTs here, but >> on a limited basis and then take 'em out". > > If you pull out the updates then you don't get the "continuous" > testing I thought you were looking for. Then its really more like a > dry-run branch, except that it's everyone's dry run at the same time. >> For instance, right now we'd have VFS and some other related stuff in >> Branch_5_0 only. When those SNAPSHOTs being tested are released, the >> snapshot override is removed. > > Exactly, and that was a bad idea that has killed any productive use of > that branch other than testing the VFS. Yeah, putting unversioned snapshots in *just doesn't work*, *period*. It's not a lot of effort to put out a versioned snapshot. It's this simple: unversioned snapshots = non-reproducable builds You're talking about buying some small convenience for one developer at the cost of all the others.

- DML _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development