Hi bigtop:

I have hacked a bigtop test cycle together which builds and tests from my 
source.  

It is a bit of a hack because:

1) It consists of 2 build phases first is online, to pull deps and install 
snapshots and second one offline, to overwrite snapshots with local source.

2) it modifies the <modules> tags in test-artifacts and smokes so that the 
build only builds a couple of submodules and only tests a couple of submodules.

Id like the script to be cleaner, maybe by sending modules in at the 
commandline and having a simpler way to deal with snapshots.

Any hints on this?


Any hints on ways to customize the pom/build without editing and maintains 
changes to the core pom xml files? Of maybe example scripts used for running 
bigtop smokes in production?

Sent from my iPhone

Reply via email to