+1 to setup continuum on ws.zones . I was about to propose it and David beat me :).. IMHO we should configure Continuum to run Axis2 build followed by new security build after every commit to either of the projects. It should send a mail to Axis2-dev with reference to the relevant commit's whenever the build is broken. AFAICS forgetting the success messages will not do any harm :) .. In this way we can make sure (at least to some extent) not to commit on top of a broken build..
Thanks, Thilina On 1/2/07, David Illsley <[EMAIL PROTECTED]> wrote:
I'm dead against moving security out of the axis2 build and leaving a substantial amount of security tests in the axis2 builds. The converse to an earlier argument is also true, namely that axis2 becomes dependant on rampart to build and that people working on rampart won't see the axis2 build failures. How about we (I'm willing to do this) set up a continuum instance on the ws zone to build axis2, rampart and sandesha at least once a day and have the success/fail messages sent to the dev lists. That should mean that we all see any failing security tests but it doesn't block work on axis2 (and speeds up the axis2 build :-) Incidentally, anything that could persuade more people to run *any* of the integration tests regularly would be a positive step forward and I think moving the security ones could do just that. David On 01/01/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > Glen Daniels wrote: > > > > The security tests are among the slowest integration tests that we've > > got. If there's a way, as Ruchith and Deepal mention, to actually test > > the same Axis2 functionality without the full security machinery, that > > would serve two purposes - speeding up the build and also more cleanly > > reducing the coupling between core Axis2 and other modules. I'd love to > > see that happen. > > Me too. This is the exact same thing that I also wanted and mentioned in > my earlier email. > > > The Rampart build will of course still test the full > > Axis2/security integration, we'd just be focusing the Axis2 tests more > > appropriately. > > This is the problem. Eventhough rampart tests are failing in rampart > project, no-one in Axis2 project will see that, until Ruchith holler. > But by that time several commits must have gone in Axis2. > > Anyway, I just wanted to add some comments and seems rampart is good to > go out of Axis2. I hope the same thing will happen to savan, etc., > > -- Chinthaka > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
