On 01/06/2011 09:33 AM, Yanko, Curtis wrote:
A not working build doesn't sound simpler to me.
We only use aggregation builds for local builds but our CI just builds
the changed module and then triggers dependent modules up the
architectural chain.
________________________________
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time, 600 times a day
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: [email protected]
For additional commands, e-mail: [email protected]
Who says it's non-working? I want to preserve something that's working
for me, while still advancing along the chain to better practices.
We don't use CI. I am trying to advance one step at a time from manual
processes, to repositories, then maybe to CI at some point?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
