--And I think this is the nub of the problem - you don't have a sufficiently frequent release cycle to experience the problems I am describing.
I too came to this same conclusion. I get that now, even every two weeks isn't enough but I still don't see my process being a pain even if we released a few times daily, I really don't. Also understand that I am committed to understanding how I'm going to get my projects to CD some day but my assumption was that I'd be building on my existing work and figure it must be my ignorance that makes me feel like the rug is being pulled out. I confess I haven't read your book yet but it is on my short list so only a matter of time I'm sure. ________________________________ Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -----Original Message----- From: jhumble [mailto:j...@jezhumble.net] Sent: Monday, November 08, 2010 6:54 PM To: users@maven.apache.org Subject: Re: Continuous Delivery and Maven > > My mantra is this, if you are feeling pain in your process, do it more > often which should force you to either solve the problem or realize > it's upstream. That is one of my 8 principles of CD ("If It Hurts, Do It More Frequently, and Bring the Pain Forward" - p26). And I think it applies to integrating modules too. > You're trying to solve a two-sided jello view of a system at build > time, perhaps what you need is to refactor you architecture (and why > SaaS, Cloud and federated systems lend themselves to CD). Maven is > your pain point but I say you're just not doing it right. > We can both play that game, but it's not very productive. I respect the fact that you have a bunch of experience and that you've created a process that works great for you, and I am not suggesting you change it. Hard as it may be to believe, I have had many experiences that point me in exactly the opposite direction, also working for organizations that make "our little A->B->C game" seem trivial. So, after we *find something valuable* we can release it trivially. > And I think this is the nub of the problem - you don't have a sufficiently frequent release cycle to experience the problems I am describing. -- Jez Humble Co-author, *Continuous Delivery <http://continuousdelivery.com/>* http://continuousdelivery.com/ http://jezhumble.net/ -- View this message in context: http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370 p3256015.html Sent from the Maven - Users mailing list archive at Nabble.com. This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
