> > BTW. We deploy our snapshot builds to a live system and do real > functional testing of a snapshot install. But this is still not a > release build and thus wouldn't go to a final customer. I think the line > here between CI and CD is blurred. >
To clarify on this last point here. All these tests are automated and occur right after a commit. So we have a couple layers of triggers here, similar to what you are suggesting Stephen: 1. Commit triggers a build. This creates a snapshot artifact of installer. Many in memory Junit tests run here. Nothing live. 2. Once build from 1 is done, take installer artifact, upload to a production server and install. 3. Run further live automated tests. The only difference in our case is that it is all done using snapshots. Any problems are fixed on the trunk of everything. Don't need to worry about released versions when doing these live tests. That just slows things down. Once you need to deliver something that could potentially go to a customer, trigger CD build, run same live automated tests and go through a bit more human verification testing. We have found that this can significantly reduce build complexity and improves speed at which the team can deliver a releasable product. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
