I believe human builders are not the solution for this. However RMs should take the responsibility of building with integration tests until proper CI server with smooth build process is available. I think most product teams have dedicated machine for building, so how about scheduling a build at night locally.
To have a better build process all should comply to follow the engineering best practices. Most of the time build remain on broken state until hard code freeze being done so it will never come up to product integration level. I think we are already having some discussions on build stabilization. Thanks, On Mon, Oct 7, 2013 at 9:44 PM, Shelan Perera <[email protected]> wrote: > Hi, > > Are we running integration tests against new builds ? I am not up to date > with new Carbon Context changes how it went. Do we have a process in place > to keep the things monitored. I am bit worried since we realized the pain > of rectifying things after went wrong :) > > Thanks > > -- > *Shelan Perera* > > Senior Software Engineer > ** > Integration Technology Group > *WSO2, Inc. : wso2.com* > lean.enterprise.middleware. > > *Blog* : blog.shelan.org > *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 > *Twitter* : https://twitter.com/#!/shelan > > *Mobile* : +94 772 604 402 > > -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
