A
andrew.may
Guest
Bronco, I agree with you on keeping test code in the same project as production code & config. But I also agree with Mike that (where it makes sense,) separating logical chunks of your architecture into separate projects makes for an easier life. Using Ivy + Artifactory to manage our dependencies makes it easy to break down our offering into interdependent projects & still keep our setups in sync, e.g. If Project A defines databaseA's schema & various programs that run against it, then a change to the schema of databaseA in project A will be built into the build artifacts when built by Hudson & will be pushed up into Artifactory. Hudson will then trigger downstream jobs to rebuild themselves. If these downstream jobs have Ivy configs that say "I depend on the latest version of project A", then they will retrieve the new version of Project A's artifacts from Artifactory (including databaseA) & will then build themselves using these retrieved artifacts (e.g. compile source against the new schema). Devs just have to remember to run the ivy-retrieve ant task in their local projects to pull in the correct versions of dependencies.
Continue reading...
Continue reading...