Hello: The build cicle we are thinking in requieres developers to do unit test in their machines, update from SVN and test again, they should commit only after that, this way we expect some builds to fail because of integration issues more than other thing. Ravi some of our team are new to Extreme programming and need time to get used to SVN, JUnit and CI so we are trying to make it as simple as we can for them, but is a critical project so we´ll insist to our team to execute test always before commit to reduce the integration cost.
Best Regards, Raúl -----Mensaje original----- De: Siegmann Daniel, NY [mailto:[EMAIL PROTECTED] Enviado el: martes, 15 de mayo de 2007 23:33 Para: Maven Users List Asunto: RE: A beginner´s question If I am understanding your point correctly, it is ok if the build is broken because you will not be able to deploy artifacts until it is fixed? What about the other developers, who may pull code from the repository and then be inconvenienced because the code does not compile or pass tests? ALWAYS run the tests before committing to the repository. Breaking the build is something to be avoided as much as possible. Furthermore, it is good practice to pull updates from the repository *before* doing the commit, so you can be sure your changes will play nicely with other developers' changes. ~Daniel -----Original Message----- From: Ravi Luthra [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 15, 2007 4:08 PM To: Maven Users List Subject: Re: A beginner´s question It isn't always a bad thing to just check in changes no matter what. I mean you still benefit from Maven's versioning so if you find yourself barking up the wrong tree with a bunch of bad commits, your users will still be happy using the stable or earlier versions of your code. The nice thing about Maven is that to get something deployed, even snapshots, it must compile and pass tests too. If anything Maven makes using source code repositories even easier because it decouples the requirement of making sure the build ALWAYS works from the source repository and other projects using the outputting artifact. Essentially Maven fills in the missing "artifact repository" that developers have always needed. Ravi On 5/15/07, Siegmann Daniel, NY <[EMAIL PROTECTED]> wrote: > > <<Thanks for the answer. So you think the best way is to let > developers commit manually and use the integration Server to make the > builds once the SCM repository has change and inform in case of > error?>> > > I expect that your developers will sometimes wish to run the unit > tests without committing the changes. Therefore having the commit be > automatic is undesirable. Heck, I have occasionally deployed a > snapshot from my machine before committing changes. > > If you want to commit after running tests, just execute "mvn test > scm:checkin". > > However, I am strongly of the believe that developers should test > changes on their own machine before committing to the repository. > Having CI does not make it OK to break the build! CI simply allows > mistakes to be caught sooner rather than later (probably the most > common IME is forgetting to add files to the repository before committing). > > -- > Daniel Siegmann > FJA-US, Inc. > 512 Seventh Ave., New York, NY 10018 > (212) 840-2618 ext. 139 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente. Pueden estar protegidos por secreto profesional Si usted recibe este correo electronico por error, gracias de informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus ------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
