Hi Chris, What about a cron job that rsync content from repo in dev regularly? Surely by the time your code gets to production, it would have had at least half an hour to sync the repository ;-)
Also, I think putting repo artifacts in SCM will makes things very slow and painful - esp if you are dependent on lots of libraries. Regards, rOnn c. "Chris Helck" <[EMAIL PROTECTED]> 05/17/2007 05:04 AM Please respond to "Maven Users List" <[email protected]> To "Maven Users List" <[email protected]> cc Subject Production build question Hello, I need advice. Our production builds are handled by a separate group. They do the builds in a locked room with limited access to the company infrastructure, and no access to the outside world. They have access to our SCM. In the room they have a web server that has ssh access to a development web server. To do a maven based build they first rsync their web server's repo with the development one. Then the build machine accesses their web server. This is a pain for both developers and the build group. So, I'm thinking I should just put an image of the repo in SCM. This gives them a good audit trail and control. To do a build they first update the repo to the head of the SCM, then fetch the source code by a label, and finally kick off maven. I know SCM people don't like to put artifacts into SCM, but this seems like a reasonable use. Are there any maven specific issues/problems that this may cause? Thanks, Christopher Helck ********************************************************************** This communication and all information (including, but not limited to, market prices/levels and data) contained therein (the "Information") is for informational purposes only, is confidential, may be legally privileged and is the intellectual property of ICAP plc and its affiliates ("ICAP") or third parties. No confidentiality or privilege is waived or lost by any mistransmission. The Information is not, and should not be construed as, an offer, bid or solicitation in relation to any financial instrument or as an official confirmation of any transaction. The Information is not warranted, including, but not limited, as to completeness, timeliness or accuracy and is subject to change without notice. ICAP assumes no liability for use or misuse of the Information. All representations and warranties are expressly disclaimed. The Information does not necessarily reflect the views of ICAP. Access to the Information by anyone else other than the recipient is unauthorized and any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. ********************************************************************** ###################################################################### DISCLAIMER: This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorized to copy or disclose all or any part of it without the prior written consent of Toyota. Opinions expressed in this email and any attachments are those of the sender and not necessarily the opinions of Toyota. Please scan this email and any attachment(s) for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. ######################################################################
