Actually, iTest is left out of the scope of the bigtop-tests for a reason. The reason being that iTest isn't specific for any version of the Hadoop (or other software) stack: it is a generic enough framework for integration testing.
We don't even need to rebuild iTest module every time we release a stack with certain version of the Hadoop and other components in it. The release artifacts of iTest should only be published if changes are done to it - like in your case. What we really need - is a good documentation and/or development guide. Hope it helps, Cos On Thu, Jul 11, 2013 at 12:52PM, Jay Vyas wrote: > Ahhhh, Okay here was my issue: > > I was actually building the "test-artifacts" pom.xml. However, the > "bigtop-test-framework/pom.xml", which is responsible for building the > TestUtils jar file, was not being rebuilt. Thus, all of the source changes > I was making wasn't reflected. > > Anyways, thanks Konstantin - after turning online mode to false in my maven > settings.xml, it became clear that my jar's were indeed getting written and > used by bigtop. > > So... moving forward... a new question which stems from this confusion that > i had -- > Maybe *bigtop-test-framework* and *bigtop-tests* should be SUBMODULES under > the same pom.xml? That way when building the bigtop smoke tests, you can > invoke a single command that builds the two cohesive artifacts? > > > > On Wed, Jul 10, 2013 at 8:48 PM, Konstantin Boudnik <[email protected]> wrote: > > > It seems like either an issue with your ~/.m2/settings.xml or your custom > > pom.xml file (something along the line of not using correct artifact > > versions, > > etc.) than a bigtop issue. The scenario you're describing is working > > everytime I've tried. > > > > Cos > > > > On Wed, Jul 10, 2013 at 07:10PM, Jay Vyas wrote: > > > Hi ! > > > > > > I just realized that I am running remotely downloaded bigtop tests, > > rather > > > than my custom groovy iTests. I was thinking that: > > > > > > mvn clean install -DskipTests -DskipITs -DperformRelease -f > > > bigtop-tests/test-artifacts/pom.xml > > > > > > would install local source code built bigtop jars, which would then be > > used > > > for tests when i run: > > > > > > mvn -fae clean verify -Dorg.apache.bigtop.itest.log4j.level=INFO -f > > > /root/SystemTestsBT/bigtop/bigtop-tests/test-execution/smokes/pom.xml > > > > > > However, at closer analysis, these commands are merely downloading > > > snapshots from remote and installing them over my local bigtop build :( > > .... > > > > > > I guess I might be interpretting the README wrong... but.... how do I > > > install my local bigtop source code into my local maven repo, so that I > > can > > > run customized bigtop groovy (iTest) tests? > > > > > > Probably this is more of a pom.xml question than a bigtop one. > > > > > > Thanks! > > > -- > > > Jay Vyas > > > http://jayunit100.blogspot.com > > > > > > -- > Jay Vyas > http://jayunit100.blogspot.com
